-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Bot can't enter the ready state in voice channels #10356
Comments
|
@balkrishan99 Thanks! Actually, I tried most of them, but in the end the problem was in other things:
Since my bot joins channels automatically and Discord doesn't provide an exact error on failure, I didn't know where the problem is. Could you only explain the number 3 in your list? Like I need to keep a several bot servers in different locations? |
Regarding point 3 in the list: "Optimize Geographical Routing," the suggestion refers to strategically placing your bot servers closer to the Discord voice servers most relevant to your user base. Here's an explanation: Why Geographical Routing Matters
How to Implement Geographical RoutingTo address these challenges:
|
Which package is this bug report for?
discord.js
Issue description
We have noticed that our bot gets the timeout error ~30-40 times a day (against 60-70 successful connections):
It happens when the bot joins to the channel and tries to enter to the READY state.
Today we succeeded to reproduce it in our working laptop with DEBUG mode:
For failed entering we see the next log:
For successful entering we see the next log:
After a few hours endpoint changed from tel-aviv to seattle and everything was working w/o timeouts already.
Code sample
Versions
Issue priority
Medium (should be fixed soon)
Which partials do you have configured?
Not applicable
Which gateway intents are you subscribing to?
Guilds, GuildMembers, GuildVoiceStates, GuildPresences, GuildMessages, DirectMessages, MessageContent
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: