Closed 0x17de closed 6 years ago
Yeah, in this case the initialization procedure as bitlbee-discord sees it would never finish. I see it as a low-priority issue though as there is no way to add new servers in bitlbee-discord at the moment.
I'm getting this error even though my Discord account has joined servers. It happens even after I've been able to connect and chat.
[edit: Oops, forgot to mention, I'm using the plugin as of commit 88de238b8317f9f19da6d12d786a66004a3f81e5.]
Can you get debug logs (see https://wiki.bitlbee.org/Debugging) when this happens? Make sure to at least remove password/token info before posting the results.
I took a look in my IRC logs and actually it seems that it was only a temporary thing - I only got that message between 12:08:21 and 12:19:16 GMT today. It's probably just Discord as I didn't get that message for several months prior. (I do get "Remote host is closing websocket connection" very commonly, but that's obviously a different issue.)
Sorry for the false alarm! If it does happen again I'll see if I can get debug logs but I don't think it's the plugin's fault in this case.
I had a new discord account and never joined any server before. The resulting issue was the following over and over again:
After joining the first server on the discord webapp the issue was resolved.