Closed Handrail9 closed 6 months ago
Two more here in case its helpful in any meaningful capacity
I have not seen this before on my instance, but what I suggest is
http://ROKU_IP:8888/logs/app_logs.txt
) and inspect them and/or share them with me and I can take a look for anything that can explain what happened
From the looks of it, it is just Invidious returning a 404. This is where that happens. If nothing else works, might be worth looking at Invidious logs and see if it is a video unavailable issue or something else (I wouldn't also be surprised that YouTube is A/B testing a new change, so only you are seeing this error).
Alrighty, thanks for the quick response. I'll try to keep this in mind for the next time it happens and keep you posted :)
@Wave6677 following up with this issue - does it still happen? Also I'm guessing this is Google trying to randomly block some connections (I've had another report from a user - similar to this, but not a 404, and the error can appear 10 to 30 minutes into the video)
If you had to guess, would you say the errors started happening roughly after version [0.20.0] - 2024-02-21, or before that?
I feel like it was right around that version, possibly maybe a bit before but my memory is a bit shoddy so I can't recall exactly when it started. It does still happen but as I've been looking into it it does seem like it's an Invidious issue more than a Playlet issue, so if it's helpful to close this issue feel free to, or I can close it, whichever.
Let's keep it open a just a bit further to narrow it down - once we try a couple of things, or we know this is an Invidious fix , then we should close it
In conclusion:
region
on calls to /api/v1/videos
endpoint (which would lead to fresh video fetch every time) probably did not help muchWe will keep an eye on it, but so far, this is all we can do.
Hello, I'm not sure what's happened but recently Ive gotten very frequent HTTP 404 errors while watching videos. It'll be halfway through a video and stop playing it, at which point I have to wait 30 to 90 seconds before it will allow me to play it again. I'm using my own instance so I know the issue is not server downtime. I will post an image of the error the next time I get it (I know it won't be too long before it happens again :P)