-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Audio] Lavalink.jar Status #4505
Labels
Category: Cogs - Audio
This is related to the Audio cog.
Type: Informational
Aims to provide information or facilitate discussion.
Comments
aikaterna
added
the
Type: Informational
Aims to provide information or facilitate discussion.
label
Oct 17, 2020
github-actions
bot
added
the
Status: Needs Triage
This has not been labeled or discussed for handling yet.
label
Oct 17, 2020
aikaterna
removed
the
Status: Needs Triage
This has not been labeled or discussed for handling yet.
label
Oct 17, 2020
Edit by aika: Superceded, comment here is regarding the 1115 build.
EDIT: Should be resolved now on build 1128 |
Errors on
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Category: Cogs - Audio
This is related to the Audio cog.
Type: Informational
Aims to provide information or facilitate discussion.
If you are experiencing any problems listed in this issue, they are known and will be addressed as soon as fixes can be identified, written, and published/pushed to a new version of Red. This issue will be edited with new information as it's available to us.
(Last updated Jan 12 2025. Please visit our support server at https://discord.gg/red if you need assistance.)
This information is for our latest Lavalink.jar, released in Aug 2024: version 3.7.12+red.1 and the Lavalink yt plugin version 1.11.2.
"Sign in if you're not a bot" or "This video requires login" or "This video is unavailable" is an IP ban that is usually resolvable by using Oauth.
"This content isn't available" means your Oauth account has been flagged and you need a new one.
With any of these choices, you will need to manage Lavalink.
You will need to pay attention to Red updates where we may update Red's Lavalink.jar or the application.yml, and integrate the changes into your own, modified copy of the application.yml.
See https://docs.discord.red/en/stable/cog_guides/audio.html#setting-up-an-unmanaged-lavalink-node-on-a-remote-vps-or-server. This is not a 1:1 guide for this situation.
"Solutions" which may or may not work for you:
You will be trusting a service with your bot's IP address and your users' playback queries
You must use a Lavalink v3 node, not v4
You must re-arrange the sources used on your application.yml so that TVHTML5EMBEDDED is first and TV is second
Follow the additional instructions at https://github.com/lavalink-devs/youtube-source?tab=readme-ov-file#using-oauth-tokens
Follow the instructions at https://github.com/lavalink-devs/youtube-source?tab=readme-ov-file#using-a-potoken
You must have a /64 or greater assigned to you
A basic guide can be found at https://lavalink.dev/configuration/ipv6/
With any of these methods:
You must provide your own application.yml to:
detail which sources the plugin will use
provide your Oauth information
provide the proper potoken information
outline which rotation strategy you choose to use and your IP block(s)
See the plugin readme for more information.
Release from Apr 2024, version 3.7.11+red.3
"Something broke when playing the track" with a 403 Forbidden error in Lavalink logs
A fix for this issue was added in 3.5.14. Please update your bot to that version and try again. If you continue to experience this issue, after updating please let us know.
Some users may get messages saying "Sign in to confirm you're not a bot".
This seems to be related to where the bot is being hosted - see the above message for 3.7.12
Release from Apr 2024, version 3.7.11+red.2
Some tracks are getting stuck at 0:00.
Trying to play some private videos will result in a more generic traceback that includes the JSON response from the site instead of a proper FriendlyException string.
The text was updated successfully, but these errors were encountered: