-
Notifications
You must be signed in to change notification settings - Fork 27
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
Unable to connect to discord: Connection timeout #201
Comments
Discussed this over IRC and provided a log. Discord is timing me out because data isn't processed fast enough. Updating to bitlbee 3.6 doesn't improve anything. Left most server I was on, without improvements. I usually get high CPU usage when connecting, but no more. The change in behavior didn't occur after I made changes to my configuration or the amount of server I was on, which lead me to believe that something changed on discord's end. Smell test suggest to me that processing the data might need to be done at a later stage. |
I am seeing the same issue. I can connect but very soon after connect drops and won't reconnect. |
Looks like an API change after all. bitlbee-discord is no longer getting GUILD_SYNC replies. Websocket opcode 12 (request sync) is also no longer in discord docs, although I vaguely remember it not being there before. |
The opcode and format are still valid though because it doesn't disconnect right away (it should on invalid opcode or badly formatted request). |
For whatever reason discord stopped responding to REQUEST_SYNC opcode(12) so we timeout on login. Temporary ignore the issue and assume we have completed connections even though we are missing guild info. I am no longer sure of the full list of effects this will have, we will surely lose guild presence info. This is a workaround for #201 and should be reverted once that is properly fixed. Signed-off-by: Artem Savkov <artem.savkov@gmail.com>
Pushed in a workaround. I am not sure of all effects it will have, but at least it lets you login. |
Thanks for the quick fix ! :) |
@remlap make sure you logout from bitlbee and restart it after installing updated plugin |
I quickly deleted my comment after I realised what I did wrong, I had stupidly run make then forgot to actually install! I even restarted bitlbee. I am an idiot! It seems to be all working well. |
I experienced this timeout issue as of February 4 and will try your fix. Thanks. |
Login works for me. Issue introduced: the user lists are now empty. |
Hi there, |
1b9870a adds support for per-channel sync, so user lists should be there once again. |
Seeing the same behavior again, can't seem to log in to discord using the plugin. |
and again..
|
I am currently able to log in normally. But if the issue persists for you please follow the 'Debugging' section from readme and open a new issue with debug information included. |
thx.. see: #218 |
As of today, bitlbee discord seems unable to reach discord at all:
Not quite sure what it means, maybe a change in API? I am obviously connected to the internet and able to reach discordapp.com,
host
returns a bunch of ip and all.The text was updated successfully, but these errors were encountered: