Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discord API updates broke it? or am I missing something? #408

Open
cfunkz opened this issue Mar 25, 2024 · 2 comments
Open

Discord API updates broke it? or am I missing something? #408

cfunkz opened this issue Mar 25, 2024 · 2 comments

Comments

@cfunkz
Copy link

cfunkz commented Mar 25, 2024

image image

2024-03-25 13:29:29 | [ERROR] | Could not authenticate, check token: /home/runner/lua420/deps/coro-http.lua:75: timeout

And my token is definately correct.

image
2024-03-25 13:40:24 | [INFO]    | Connecting to Discord...
2024-03-25 13:40:24 | [ERROR]   | Could not authenticate, check token: /home/runner/lua420/deps/coro-http.lua:75: Error verifying peer: unable to get local issuer certificate
Uncaught Error: cannot resume dead coroutine
stack traceback:
stack traceback:
    [C]: in function 'error'
    /home/runner/lua420/deps/secure-socket/init.lua:24: in function 'handshakeComplete'
    /home/runner/lua420/deps/secure-socket/biowrap.lua:56: in function </home/runner/lua420/deps/secure-socket/biowrap.lua:49>
    [C]: in function 'run'
    [string "bundle:/init.lua"]:55: in function <[string "bundle:/init.lua"]:47>
    [C]: in function 'xpcall'
    [string "bundle:/init.lua"]:47: in function 'fn'
    [string "bundle:deps/require.lua"]:310: in function <[string "bundle:deps/require.lua"]:266>```
    
@lil-evil
Copy link

lil-evil commented Apr 7, 2024

Hey. The error talk about certificates, from the http library. I might be wrong, but I'll try to give you hints

Assuming you're on a Linux OS, you can try to install the ca-certificate package (with apt, pacman ...), which would probably fix the certificate error ?

@Bilal2453
Copy link
Contributor

Bilal2453 commented Apr 7, 2024

That would probably not fix it. What needs to be done here is updating the system, pretty much any Operating System will come with working CA store, although when that gets out dated you might start getting errors such as this one. So update your operating system and that will probably do the trick, if not, make sure you are pulling from the latest repository, potentially contact your VPS if that doesn't do it as it is a system issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants