Authorizing Client refuses to work, no matter what client is even used
I tried using Overlayed as I noticed it has Linux support. I tried it once, doesn't work. Then I tried it on Windows to check, and it works there. For some reason, it refuses to connect to ANY client, beit the official from Arch repos (yes, I use Arch), flatpak, Vesktop, Equicord... Nothing works! Neither the vanilla client, nor using other mods like Replugged or anything. It's like it's not even detecting the window and asking for authorization. I tried it all, shutting down arrpc througg systemctl disable --now arrpc, uninstalled and reinstalled... I'm at a loss. Please help :(
6 Replies
Yep I have the same issue :/
i think the connection issue is realted to their api https://github.com/discord/discord-api-docs/issues/7200
GitHub
[RPC] Events are delayed when connecting more than 2 times · Issue ...
Description I seem to have uncovered either a neat bug or feature that I'm trying to understand why it exists. tl;dr my app connecting to the RPC websocket after more than two attempts will res...
but
i have this test page https://overlayed.dev/test
Overlayed Connection Test
Test connecting to Discord's RPC Server using WebSockets
but what i suspect is that the socket is getting ratlimited
I tried it, and for some reason, it doesn't detect the discord:// protocol either. Had to basically edit the mimetype and then the protocol worked. But... Not the invite links, nor the overlays are working
Testing the page above basically does nothing
Doesn't even show a signal that it connects
Weirdly it works when I shutdown Ublock Origin, but I doubt that's the thing that makes the app not work