• If you need help or want to discuss things, you now can also join us on our Discord Server!
  • Happy New Year everyone! A new version (1.0.0-beta.16) is out for Linux, fixing an issue that could lock the bot up when using it with TS3. Please visit the resources section or the main page (https://www.sinusbot.com) for the new package.

Discord timeout/fails to reconnect to channel.

Zaidain

Member
Hello all,

I'm a long-time user but first time poster and am having an issue.
My bots are working via discord (used to use TS3 for years) but they have developed an issue in the past 48h where they will timeout in a channel and won't reconnect to the same channel anymore despite them being set to do so. I can get them back into the channel manually but this is an issue when they shut down every 30-50mins.

I have them set up with no scripts, they just play one radio stream each but I have now had to turn on scripts to be able to use !join instead of having to remote into my server and manually bring them back. I had to change their default channel to another, save settings then change it back and only then would they reconnect but again would stop 30-50min later.


Does anyone have any idea what could be causing this?

I have gone through the forums here before posting and can't find anything like what is going on here. I have fully updated, rolled back, remade the bots and all sorts of things but the problem remains. My second server running Sinusbot is also now doing the same thing as is my friend’s server in Canada so I don't think this is a ME problem.
 

Attachments

  • Screenshot 2022-09-18 221028.jpg
    Screenshot 2022-09-18 221028.jpg
    255.5 KB · Views: 19

Lala Sabathil

Donor
is awesome!
Contributor
Insider
We are aware of that issue.

Due to private life stuff we can't provide a fix that fast.

Sorry for that
 

Zaidain

Member
We are aware of that issue.

Due to private life stuff we can't provide a fix that fast.

Sorry for that
Thank you for the super fast reply Lala! Glad to know you guys are aware of it and I'm sure you're working hard on a fix for it. I understand you can't fix it right away but I'm grateful you guys are sorting it out as fast as you can.

Thank you for your hard work :)
 
Yeah, i would like to thank you Lala as well, i was going to open a Bug Report about that as well, because i was almost going mad not being able to find a fix. I thought i was the only one having this problem :D
 

SubwooferNL

Member
i have the same issue

2022-09-20T21:20:07+02:00 voice handler returned with: error from voice reader: websocket: close 4014: Disconnected.
2022-09-20T21:18:28+02:00 reconnecting soon
2022-09-20T21:18:28+02:00 disconnected from discord
2022-09-20T21:18:28+02:00 error from conn reader: websocket: close 4003: Not authenticated.
2022-09-20T21:18:27+02:00 reconnecting to discord gateway by request
2022-09-20T21:16:36+02:00 [ command:41:14] could not get author with ID=375805687529209857; replacing client with workaround
2022-09-20T21:03:39+02:00 [ command:41:14] could not get author with ID=207441536819003392; replacing client with workaround
2022-09-20T20:54:26+02:00 [ command:41:14] could not get author with ID=207441536819003392; replacing client with workaround
 

Lala Sabathil

Donor
is awesome!
Contributor
Insider
i have the same issue

2022-09-20T21:20:07+02:00 voice handler returned with: error from voice reader: websocket: close 4014: Disconnected.
2022-09-20T21:18:28+02:00 reconnecting soon
2022-09-20T21:18:28+02:00 disconnected from discord
2022-09-20T21:18:28+02:00 error from conn reader: websocket: close 4003: Not authenticated.
2022-09-20T21:18:27+02:00 reconnecting to discord gateway by request
2022-09-20T21:16:36+02:00 [ command:41:14] could not get author with ID=375805687529209857; replacing client with workaround
2022-09-20T21:03:39+02:00 [ command:41:14] could not get author with ID=207441536819003392; replacing client with workaround
2022-09-20T20:54:26+02:00 [ command:41:14] could not get author with ID=207441536819003392; replacing client with workaround
We are aware of that issue.

Due to private life stuff we can't provide a fix that fast.

Sorry for that
That still counts
 
Thanks a lot for that :) Do you get this fixed version (didn't test it yet) by upgrading the Sinusbot via the official tutorial as well?
 

flyth

is reticulating splines
Staff member
Developer
Contributor
Thanks a lot for that :) Do you get this fixed version (didn't test it yet) by upgrading the Sinusbot via the official tutorial as well?
You'd need to change the filename from sinusbot.current.tar.bz2 to sinusbot-1.0.1-amd64.tar.bz2 in that case (and use the link for the download). The official links (and with that also the Docker image) will be updated if everything looks fine.
 

ebmusicman84

New Member
I am having what appears to be a similar issue to this, although the bot never connects to the Discord channel to begin with, instead of connecting and then timing out eventually.

Relavant info:
Bot Version: 1.0.0-beta.16-ba60e37
TS Client / Server: n/a using Discord
OS Version: Ubuntu Linux 5.4.0-126
Hardware: Unraid VM 2 cores / 1 gb memory

I have attached four files with further info, please let me know what next steps to take or if any further information is needed, or if I should start a different thread instead of extending this one.

Thanks
 

Attachments

  • sinusbot_diag_info.zip
    6.4 KB · Views: 0

ebmusicman84

New Member
Apologies, please disregard the previous. I did not properly understand the installation instructions. It appears to be working fine now.
 
I've been having the same problem that ebmusicman84 is having where Sinusbot won't even connect to my Discord channel. But I'm working with the Windows version. Based on the file extensions I think the fix that was offered in this thread is for the Linux version? Is there a fix for the Windows version?
 

Lala Sabathil

Donor
is awesome!
Contributor
Insider
I've been having the same problem that ebmusicman84 is having where Sinusbot won't even connect to my Discord channel. But I'm working with the Windows version. Based on the file extensions I think the fix that was offered in this thread is for the Linux version? Is there a fix for the Windows version?
We currently have no updates for windows. No ETA either.
We suggest using a linux server.
 
Top