-
-
Notifications
You must be signed in to change notification settings - Fork 712
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
"Initial player response not valid" #2487
Comments
yup, having this happen to me too, kinda scared me at first that every video was the same |
Can confirm this, all instances are affected. However, I have noticed that only some videos are effected by this e.g. charlie bit my finger works but typical unixporn user doesn't. |
the first video mightve worked because you have it in cache, for me no video at all works |
Some regions still appear to work - CA and FR. |
You won't even get a channel feed. |
How does NewPipe do it? Can we use their method? |
can confirm |
This comment was marked as spam.
This comment was marked as spam.
sussy sonic |
Require double check! some videos seem to be still functioning while others are not:
and appears to be independent of channel:
Please verify and use emojis to signal if you can replicate. |
This comment was marked as spam.
This comment was marked as spam.
@CZython A bit different for me: the last video you mentioned works, others don't |
Seems that Invidious experienced something similar today: iv-org/invidious.io#71 |
This comment was marked as spam.
This comment was marked as spam.
it's the opposite for me. the ones you say don't work, are working, and vice versa. |
This comment was marked as spam.
This comment was marked as spam.
in hope of not DDOSing, i need a check these of instances:
because they seem to work... @Cade66 @DanielProg39 @cyberhardt |
@CZython the instances you listed work fine |
This comment was marked as spam.
This comment was marked as spam.
I'm staring think that the "update/dropped support" is only partial, because on some instances no videos work, while on others some videos work. and as if by magic, these specific instances work fine. I'll close this issue and put these instances to the top as workaround, because is obviously no longer satisfies: Or is there any reason to keep this issue open? |
It makes sense to keep the issue open as long as the official instance (piped.video) is affected. |
Which is still the case. |
ok, i'll leave it open |
This comment was marked as spam.
This comment was marked as spam.
First one is a 404 for me. the other ones work - I've tested the same video on those instances (except the first one) and on the ones I use: piped.video, piped.qdi.fi and il.ax. The ones I use aren't working, but those you provided seem to work normally. |
Yup, it seems like not all instances were hit by that error. piped.video, piped.qdi.fi and il.ax are definitely having issues. shall we make a list? |
You could also configure it with |
Hi, I have same issues on my instance. I tried to use |
I have the same issue on my Piped instance, none of the aforementioned workarounds worked. Any idea how to fix this? |
@unstablemaple I figured it out with privoxy and |
I'm having this issue as of today, first time user of piped. |
I'm not sure if it's related, but as of the past ~48h I'm no longer receiving updates on my account's subscription feed either. I haven't configured the proxy for my instance (yet), but I've kicked a bit the can down the road by using my instance for authentication and other instances for streaming. No problem so far, as the API subscription side still worked even without the dynamic IP workaround. But that no longer seems to be the case. Relevant log traces:
Has anybody being experiencing the same issue lately as well (i.e. subscriptions not updating because of errors from |
Yes, your instance's IP blocked by YouTube, you'll need to change it, use a VPN, configure a proxy, or alternatively, if you have an ipv6 prefix, use this. |
@FireMasterK thanks for the input! I've managed to fix the ytproxy:
image: 1337kavin/ytproxy:latest
restart: unless-stopped
volumes:
- ytproxy:/app/socket
container_name: ytproxy
+ depends_on:
+ - tor
+ environment:
+ REQWEST_PROXY: socks5://piped-tor:9050
+
+ tor:
+ image: lncm/tor
+ container_name: piped-tor
+ volumes:
+ - ./data/tor/data:/etc/tor
+ - ./data/tor/data:/var/lib/tor
+ - ./data/tor/run:/var/run/tor
+ restart: on-failure
+
piped:
image: 1337kavin/piped:latest
restart: unless-stopped
@@ -21,7 +53,15 @@ services:
- ./config/config.properties:/app/config.properties:ro
depends_on:
- postgres
+ - tor
+ environment:
+ REQWEST_PROXY: socks5://piped-tor:9050
container_name: piped-backend
+ I'm still getting errors when streaming though, but at least the biggest offender is now out of the way - as long as I can get my feed updates, I can still use alternative instances for streaming. Btw I've just noticed that this commit actually completely removed the support for the |
Ironically my instance: piped.syncpundit.io is now facing the same problem while others seem to have fixed it. @FireMasterK please link me to the fix, I'm dreading reading through ALL the back and forth since it's from half a year back. |
@Deon-Trevor if you also started experiencing issues lately, and with error logs similar to mine (e.g. the A Tor container with SOCK5 thrown in the docker-compose should be enough to circumvent it if it's the case. |
Just switched IP Address and it's working fine. If you don't mind please share your docker compose config so I can implement one as well |
The docker-compose diff is in my previous post - you just need to add a basic |
Thanks a bunch mate |
@blacklight you need to use the new Rust based proxy, you're still using the old Golang one. It was changed over a year ago in TeamPiped/Piped-Docker@a77f887 You can |
I have implemented IPv6 support in docker and made sure that the containers have V6 connectivity, however Piped seems to always use V4, as it always has the 'Initial player response is not valid' Error, because it's using the banned V4 address and not IPv6. Is there a way to force piped to use V6 for its connections to YouTube? my Piped docker setup: Edit, you have to use |
I'm interested as well. I'm having the error and |
Official instances do not have this problem. It happened again last time on the lunar.icu server. Blocking problem not solved? |
Hi. I'm getting this error on every instance I try through the LibreTube app. Testing a couple of servers directly, it appears to be a problem through the web interface too (or at least they're not loading videos) so I'm reporting it here. |
Doesn't Piped still use the ipv6 rotator provided by Invidious? |
backend : https://apitredingplay5.ddns.net/ After completing the IPv6 setup, I noticed that my backend is defaulting to the Nginx web page instead of the intended backend page. I have reviewed the configuration steps but have not been able to identify the cause of this issue. If i set server ipv4 it will work. I would greatly appreciate your assistance in resolving this matter. |
Testing requested (edit by kavin)
Hi everyone, I request everyone to please use https://pipedtesting.kavin.rocks/ temporarily as it would help with debugging and fixing this issue. Thanks!
In LibreTube, you can set the custom API URL to https://pipedtestingapi.kavin.rocks
Workaround Found
use one of these instances (because they somehow work):
Official Instance
Describe the bug
Youtube dropped support for API version that Piped uses to load videos.
update: some videos seem to still work
To Reproduce
anyofficial piped instanceExpected behavior
Loads name and Video
Logs/Errors
instead of video there is a message:
This content isn't available.
instead of video name there is this text:
Video Not Available
Browser, and OS with Version.
No response
Additional context
UPDATE:
depending on your location different videos seem to be unavailable
source: verification | different result
The text was updated successfully, but these errors were encountered: