-
Notifications
You must be signed in to change notification settings - Fork 87
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
SUSPICIOUS - Could not load track. #208
Comments
Same here. It fixed itself once, then happened again 24h later. Restart fixed it the next time. Could this be some YouTube token not renewing in time? Here are my logs:
|
the worse part is the bot get disconnected and all the queue get deleted, I would suggest the developers to fix it by playing the next track instead of just kicking it out of the vc. I tried to fix it. but I failed XD |
Seems like this is a recent issue with lavaplayer lavalink-devs/lavaplayer#69 and is most likely already fixed in the latest snapshot with this merge lavalink-devs/lavaplayer#70 But I guess we'll have to wait for that fix to get backported to legacy v1 lavaplayer and legacy v3 lavalink since that's what this bot uses for now |
I'm using Lavalink v3 too on my project and facing a similar issue, I made my own fork and ran the workflow so it uses the snapshot version of Lavaplayer that contains the fixes. Can't confirm yet that it actually solves the issues. /~https://github.com/SuspiciousLookingOwl/Lavalink/actions/runs/8035035875 (download artifacts) EDIT: 24 hours later, haven't faced the same 400 issue since I used my build, so seems like it does fix the issue |
A day after my comment a new lavalink branch was made implementing the fix and I haven't gotten the error since switching to it. If you're using docker you can just switch from lavalink:3 -> lavalink:fix-yt-400-v3 in the docker-compose.yml and you're set! |
I'm using your lavalink v3 fork one and it has been running thoroughly. Thanks a lot! |
For future reference #229 (comment) |
The text was updated successfully, but these errors were encountered: