-
Notifications
You must be signed in to change notification settings - Fork 11
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
[BUG] “This helps protect our community. Learn more” #400
Comments
Thanks for reporting, please see iv-org/invidious#4734 |
Sorry didn’t know it was already reported, also I found a server that still works, can I post that? |
No worries, it's good to have an issue on this repo as well for visibility. We suspect that this is an incremental rollout where eventually all instances will be affected, even though some are still currently working.
Sure! For anyone facing the same issue (who's not using their own instance) is to try different ones until one works. Use the "Test instance" button in Playlet to test quickly, or test them in the browser. |
Update iv-org/invidious#4734 (comment)
|
iv-org/invidious#4734 (comment)
|
Doesn't look good for now. I'm still confused whether this is an IP blacklisting issue or just a general google patch against invidious. I run my own invidious docker instance on my residential IP and no videos play. I tried using a few different VPN IPs and same deal. |
The hot fix seems to work pretty well, would it be possible to add an option to use the hot fix for all playback so that playlet can be used without having to use the web remote? Just to get by until invidious comes out with a fix. |
This is not simple, since https://github.com/LuanRT/YouTube.js was used to implement this temporary fix. Roku does not have a way to run Javascript, so the request is prepared and parsed in the web app, but sent through the Roku device. |
Right now, the Playlet backend works ok, so I'll close this issue |
Playlet seems to be broken and displays that message
The text was updated successfully, but these errors were encountered: