Skip to content
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

Voice connection timeout #4

Closed
itsjakeb opened this issue Sep 23, 2017 · 34 comments
Closed

Voice connection timeout #4

itsjakeb opened this issue Sep 23, 2017 · 34 comments

Comments

@itsjakeb
Copy link

Error: Voice connection timeout
     at Timeout.pendingGuilds.(anonymous function).timeout.setTimeout [as _onTimeout] (/home/jake/discord/Adonis/node_modules/eris-lavalink/src/PlayerManager.js:323:25)
     at ontimeout (timers.js:469:11)
     at tryOnTimeout (timers.js:304:5)
     at Timer.listOnTimeout (timers.js:264:5)
@briantanner
Copy link
Owner

Could you provide any more info on it?

@briantanner briantanner changed the title Any estimate of this being fixed? :) Voice connection timeout Sep 27, 2017
@itsjakeb
Copy link
Author

Not much info to be provided. Happens quite often and I know other large bots that have this problem such as Pancake. Really not sure what causes it.

@minemidnight
Copy link

I get this error a bunch too. Used to happen with Eris, might want to ask abal on how he fixed it.

@minemidnight
Copy link

Any updates on this? It’s pretty bad for my users.

@briantanner
Copy link
Owner

Have any logs or debug that might help pinpoint the cause?

@minemidnight
Copy link

Nope. All I know is Eris used to have the same issue.

@itslukej
Copy link
Collaborator

itslukej commented Oct 8, 2017

Getting this too, however I've noticed that it happens more after the shard has lost connection with one of the voice nodes. https://sentry.davinci.sh/share/issue/332e333535/
image

@itsjakeb
Copy link
Author

It's happening a lot more now than it ever has to me. Got to the point where it won't play.

@briantanner
Copy link
Owner

Any help would be appreciated. I haven't found anything in the client that could be causing it.

It is fixable by restarting the affected Lavalink node, it seems to get in a connect loop which is what I find causes it often times.

@itsjakeb
Copy link
Author

Alright, its just constant.
image

@briantanner
Copy link
Owner

Yeah, that doesn't help much.. The best that I've been able to figure out so far is that there's either something not implemented correctly in the client, or have been told it could be a JDA-Audio issue. However, I've looked through the client up and down for weeks looking for the cause and can't see anything glaring.

Repository owner deleted a comment from itsjakeb Nov 12, 2017
Repository owner deleted a comment from briantanner Nov 12, 2017
Repository owner deleted a comment from itsjakeb Nov 12, 2017
@itslukej
Copy link
Collaborator

I too have looked through eris-lavalink and I've seen nothing that could lead to this issue, given that JDA-Audio is experimental, It's probably coming from the lavalink server itself. I could ask someone using the JDA lavalink client to see if they have also experienced it

@p4rkrs
Copy link

p4rkrs commented Nov 17, 2017

I have a lot of that too. The people need to kick the bot, and wait like 5 minutes & thats will work

@itslukej
Copy link
Collaborator

itslukej commented Dec 5, 2017

We are now having cases where the bot will give a Voice connection timeout when it shows as not in the voice channel (compared to the previous times where the bot would show as in the voice channel), the only solution we have found so far to this is restarting the whole eris client (which is 5 shards, ~4.5k guilds for us, quite annoying 😕)

Repository owner deleted a comment from Vappe Dec 5, 2017
Repository owner deleted a comment from Vappe Dec 5, 2017
@itslukej
Copy link
Collaborator

Very sure this issue is on the lavalink server side. A 'fix' we have found for our users is to have them connect to a different lavalink server than the one that they are getting vc timeouts on
image

@freyacodes
Copy link

Grepping the affected guild's id in the affected LL server's debug.log might give some clues

@itsjakeb
Copy link
Author

I no longer get this issue but people still say they get it with other bots so I'll keep this issue open.

@p4rkrs
Copy link

p4rkrs commented Dec 18, 2017

@DoctorDarkMagic How?

@itslukej
Copy link
Collaborator

@itskiru #11

@briantanner
Copy link
Owner

Closing due to age, deprecation, and new bug fixes in the v1 branch

@Bacon1661
Copy link

Still getting this issue.

@itslukej
Copy link
Collaborator

@Bacon1153 Have you updated eris-lavalink and lavalink server to v2?

@Bacon1661
Copy link

Bacon1661 commented Feb 15, 2018

@itslukej Yes, I've gotten this both on v1 and v2.

@briantanner
Copy link
Owner

This happens afaik, have always had this issue when dealing with music, if you can get more info on what's causing it and/or identify a bug in eris-lavalink, feel free to open a new issue.

Some possible causes:
Permissions - View Channel, Connect, Use Voice Activity
Voice Server/Region - Not sure how common, but happens on occasion that the voice server is to blame, changing region gets you on a new server.

@Bacon1661
Copy link

It's strange, because some people don't have this issue at all and some people (like me) always get the error. I'll look into it.

@Bacon1661
Copy link

I've been talking to some people and someone said that voiceServerUpdate is never getting called, causing the timeout to never be resolved. Very interesting.

@briantanner
Copy link
Owner

That would be because your bot never joins the channel, therefore never gets a voice server update, and times out... I would check the things I mentioned above, namely that the permissions are correct when it happens.

@PassTheMayo
Copy link

I've been getting the same issue, but it's seemed to go away after I messed with the code. It hasn't been happening today.

@briantanner
Copy link
Owner

@PassTheMayo "after I messed with the code" would be nice to know what this means if it's a bug in eris-lavalink

@PassTheMayo
Copy link

@briantanner I'm not sure what I did, because I changed a lot. I can't explain what I did, but it just doesn't do that now.

@p4rkrs
Copy link

p4rkrs commented Mar 1, 2018

Just use 0.1.2 with V1 of lavalink and everything is okay.

@Bacon1661
Copy link

Bacon1661 commented Mar 1, 2018

Why would you use v1?

@briantanner
Copy link
Owner

I would recommend people update to Lavalink v2 and eris-lavalink ^1.0.x

@briantanner
Copy link
Owner

I'm locking this issue, if anyone can identify a bug in eris-lavalink with a way to reproduce, please submit a new issue. Otherwise, refer to my previous comments, and make an effort to correct the issue on your end first. If that doesn't work, please provide some debugging information or even submit a pull request if you think you can contribute anything.

Repository owner locked as resolved and limited conversation to collaborators Mar 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants