-
Notifications
You must be signed in to change notification settings - Fork 2
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
Error: Could not connect #1
Comments
Did you specify a Your ClientID in the index.js? |
Yes, but i guess i found the error: This page: https://github.com/djs/discord-rpc doesn't exist and npm trys to get the discord-rpc package from there |
If u would, u can use my ClientId if u can't create your own: 825853950833328201 |
I have my own id, but the script fails |
Okay... u are the only one that have this error |
is it compatible with linux? |
do u use Linux? |
You need to run RichPresence on the same system as Discord! |
Additional note: It only works if you use a local installation of Discord, it won't work if you use Discord in a browser. |
Error: Could not connect
at Socket.onerror (/home/pi/savediscord/Custom Discord RPC/node_modules/discord-rpc/src/transports/ipc.js:32:16)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
The text was updated successfully, but these errors were encountered: