-
Notifications
You must be signed in to change notification settings - Fork 48
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
Invalid status code for access token tv response: 400 #69
Comments
It looks like the url you are requesting in the log, |
Is this in my ability to fix? I'm not doing any sort of URL manipulation on my side. |
Having the same sort of problem for a discord bot |
this could potentially fixed by #70 |
@austin3410 @SKitou can you see if this lavalink build fixes the issue? lavalink-devs/Lavalink@9a6c9d4 |
@topi314 Can confirm |
I'd also like to see if this build fixes my issue but I'm not familiar enough with GitHub to know how to download that specific build. I'm using the .jar file from the master release. Do I have to compile my own .jar in this case? |
Click on the commit |
Thank you! |
My problems are still occurring with the snapshot build. Same errors as previous. |
Having the same issues, status code 400 on ytsearch |
Having the same, Invalid status code for video page response: 400 |
pulled docker tag |
I am now using the build someone mentioned in the comments of lavalink-devs/lavaplayer#69 instead of the latest snapshot, this should hopefully solve the issue.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I have this problem and I'm using this version
|
It was fixed with |
I can confirm using branch fix-yt-400 fixes the issues. Perhaps the 2.0.1 lavaplayer is outdated due to Youtube making some changes to their backends. |
branch fix-yt-400 has problems with lavasrc 4.0.1 |
Make sure you use lavasrc-plugin-4.0.1.jar |
as i mentioned, i am using specifically that version of plugin for fix-yt-400, it works fine with lavalink v4 |
this should now be fixed in https://github.com/lavalink-devs/lavaplayer/releases/tag/2.1.1 and https://github.com/lavalink-devs/lavaplayer/releases/tag/1.5.3 I'm locking this issue, please open a new issue when you encounter new errors |
I'm running into this error on my Lavalink server. I started by submitting a form post on the Lavalink Discord but was directed here as a possible bug report.
Background:
Developing a Discord bot using the Wavelink library to communicate with my Lavalink server. The bot and Lavalink server are being hosted within the same Ubuntu environment.
Sometimes when autoplay is set to enabled. Lavalink can't find related tracks to the one that was playing.
I'm not sure but I believe it has to do with the initial track, or the search term that was used to play the initial track. I also see in the logs that it fails to update my YouTube access token but there are times when autoplay still works with this error. I don't have MFA enabled on this YouTube account.
Lavalink version: 4.0.3
Wavelink version: 3.2.0
I'm happy to provide any other information.
Lavalink log file:
spring.log
application.yml file:
The text was updated successfully, but these errors were encountered: