Error getting segments for video. Code: 404 - Githubissues

dmunozv04 / iSponsorBlockTV

SponsorBlock client for all YouTube TV clients.

GNU General Public License v3.0

2.42k stars 98 forks source link

Error getting segments for video. Code: 404 #158

Open BACONGUDEN opened 4 months ago

BACONGUDEN commented 4 months ago

Getting a 404-error in logs when playing a yt vid on tvOS.

Running in Docker, on CasaOS through Debian. I have nginx proxy manager running as well on the same server, which I assume is causing this error?

Any help is appreciated!

Logs:

isponsorblocktv  | Error getting segments for video Qh9KBwqGxTI, hashed as a8d0. Code: 404 - []
isponsorblocktv  | [2;36m[05/13/24 08:58:05][0m[2;36m [0m[34mINFO    [0m [33mYouTube on TV[0m[33m [0mPlaying video Qh9KBwqGxTI with [1;36m0[0m     
isponsorblocktv  | [2;36m                    [0m         [33m              [0msegments                             
isponsorblocktv  | [2;36m[05/13/24 08:58:07][0m[2;36m [0m[34mINFO    [0m [33mYouTube on TV[0m[33m [0mPlaying video Qh9KBwqGxTI with [1;36m0[0m     
isponsorblocktv  | [2;36m                    [0m         [33m              [0msegments                             
isponsorblocktv  | [2;36m[05/13/24 08:58:08][0m[2;36m [0m[34mINFO    [0m [33mYouTube on TV[0m[33m [0mPlaying video Qh9KBwqGxTI with [1;36m0[0m     
isponsorblocktv  | [2;36m                    [0m         [33m              [0msegments

BACONGUDEN commented 4 months ago

Any help?

dmunozv04 commented 3 months ago

Please, update to the latest version and run the container in debug mode, adding --debug to the docker command and post the logs. That way I'll be able to see what's happening and maybe identify the issue

BACONGUDEN commented 3 months ago

Please, update to the latest version and run the container in debug mode, adding --debug to the docker command and post the logs. That way I'll be able to see what's happening and maybe identify the issue

Did a much needed fresh install on my debian server this weekend and once I installed the latest image again it somehow magically "Just Works™" on my LG TV (webOS).

Snooped around in an old backup of the container and all I can see that could be causing the issue I had was that in my config I misspelled "sponsor" as "sponsorr" (servarr brainrot lol), no clue if that could cause this 404 to happen? I had no other categories specified under the "skip_categories" part of the config.

Having an issue with the auto-play setting not working though, kicks me back to the main screen after video finishes even though auto-play is set ON. Same as #82.