-
-
Notifications
You must be signed in to change notification settings - Fork 250
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
Sign in to confirm you're not a bot #1049
Comments
This is a wider issue affecting many other bots using Youtube's API.
It seems like the cobalt client implemented OAuth tokens to circumvent this: Our issue is that A couple ways of tackling this:
|
I'm also experiencing this issue! |
I also have this problem. |
I also have this problem! Same configuration |
Hi! I'm currently trying to figure it out, based on the comment @Stealthii made. Apparently, there is no issue with @distube/ytsr, (from what I have just tested, the search part is just OK). I think the problem revolves around ytdl instead, when it tries to get the audio stream. That ytdl call to fetch for the info has no apiKey whatsoever, so maybe there is an alternative? I dunno, I'll keep trying to solve this issue |
I'm also experiencing this, even when trying to play songs from Spotify weirdly enough. In case it's relevant, just before having this error, the bot was acting weird when trying to play a song.
|
Currently experiencing this issue when hosting the Jmusicbot app on PebbleHost From the Console The command I ran: ?p https://youtu.be/a_aIaO88rzY?feature=shared |
Still unable to play anything, though now it does log This is using the latest version with Docker Compose so I'm unable to run this before the container starts, will try tomorrow to install it manually. |
Getting the exact same issue as well |
To add more info here (gathered mostly from the links above), this appears to be an IP block from youtube. Apparently it can even happen because a neighboring IP spammed the youtube API too much. I can confirm that, while my VPS has been unable to play anything for more than a month, I was able to play songs from both youtube and spotify when running the bot on my own PC. Some users on other projects were able to access the API with rotating IPv6, cookies from an account that is currently logged in, using a proxy, or with OAuth 2. I haven't found any workaround that we could use so far, besides running the bot on a entirely different IP. |
Just updated to the latest build and getting this as well. |
I got around this by making Muse dependent on Warp.
|
How do I make this work within my Docker application? |
Just append the above to your docker-compose.yml for Muse and then run docker-compose up -d In the end it should look similar to this:
|
Thanks for the fix! Should we merge this into Muse? The IP-banning from Youtube looks like it will stay, so we need a long term solution. |
I can vouch that this works for me! Though I assume they will find a way to implement it into the project overall? |
Is this issue still present in muse v2.9.3 or v2.9.4? The recent update to @distube/ytdl-core in v2.9.3 has addressed various problems. |
Yeah, this is not a @distube/ytdl-core issue. Youtube is blocking IPs, there is nothing that can be done on yt-dlp's end, you just have to get an unbanned IP or route your requests through something else (like Warp). |
I've tried to set up muse to run with this but the moment I start it with Warp I just get timed out when trying to queue anything. Without warp the bot doesnt time out but I also have the problem of youtube not allowing my connection. |
Same for me, Warp worked perfectly for a week, and now I have timeout issues. |
Would moving to using the youtube api without warp work as a solution? I'm running ghcr muse latest as a docker container on digital ocean and it's either "Sign in to confirm you're not a bot" without warp or timeouts with warp. |
So far having same issues of "Sign in to confirm you're not a bot" or timeouts with warp. My instance is hosted on Oracle Cloud. yt-dlp has an option to pass cookies.txt, so you can create some dummy account and pass its cookies to be "signed in". For us this means the bot needs to be configured to accept and pass the cookies to yt-dlp if configured. |
Are there any updates to this? |
Bug still on in v2.10.0! |
It's not really a bug anymore, if you are experiencing this issue, you either need to change the External IP address or use the warp thing mentioned above and add it to the docker compose file. It's because Google hit you with IP limit on API |
Warp didn't work for me, the application just hung instead. Would appreciate official guidance on this! |
@tyteen4a03 |
Which provider are you on? I'm on Hetzner. |
Oracle Cloud, I moved my Muse instance to a different node, got the same error, added the Warp dependency and it started working. If the data center IP has been blacklisted by youtube then there is not that much one can do to unblock. |
I also run my bot on Oracle Cloud. Unfortunately, Warp does not solve this problem for me permanently. Everything works great for a few hours, but then I get the error message “Sign in to confirm you're not a bot” despite Warp. |
For anyone seeing this in the future, looking to implement the WARP solution, breaking changes to the way the container works were introduced by a containerd update in late November, (see this) requiring some light changes. Updated config is this: services:
muse:
image: ghcr.io/museofficial/muse:latest
restart: always
volumes:
- ./muse:/data
environment:
- DISCORD_TOKEN=YOURS HERE
- YOUTUBE_API_KEY=YOURS HERE
# Below are all optional
# - SPOTIFY_CLIENT_ID=
# - SPOTIFY_CLIENT_SECRET=
# - CACHE_LIMIT=10GB
# - ENABLE_SPONSORBLOCK=true
# - SPONSORBLOCK_TIMEOUT=2
# - BOT_STATUS=online
# - BOT_ACTIVITY_TYPE=LISTENING
# - BOT_ACTIVITY_URL= # Not used for non-streaming activity types
# - BOT_ACTIVITY=your shite music
network_mode: "service:warp"
depends_on:
- warp
warp:
image: caomingjun/warp
container_name: warp
restart: always
devices:
- /dev/net/tun:/dev/net/tun
ports:
- '1080:1080'
environment:
- WARP_SLEEP=2
- WARP_LICENSE_KEY=UBW6t134-3A6b24Km-nJ286iN9
cap_add:
- NET_ADMIN
sysctls:
- net.ipv6.conf.all.disable_ipv6=0
- net.ipv4.conf.all.src_valid_mark=1
volumes:
- ./data:/var/lib/cloudflare-warp Tip Using a WARP+ key is HIGHLY recommended since you get extra fast bandwidth and better servers. If you need a WARP+ key with a bunch of bandwidth, use one from here. Warning If you previously restricted your YouTube Data API key by IP address, this will no longer work. Either remove the restriction or add Cloudflare's IP ranges which are available here. |
What's happening?
With the newest version, I get the message "Sign in to confirm you're not a bot" whenever I try to play a song.
Example command:
/play query: https://www.youtube.com/watch?v=lgh68Swuak0
Logs
Screenshots
Runtime
I'm running Muse:
Versions
The text was updated successfully, but these errors were encountered: