-
Notifications
You must be signed in to change notification settings - Fork 262
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
Trouble with videos not playing #75
Comments
I should add that I have whitelisted s.youtube.com |
I'd like to know how to stop the schedule for this script as well |
For the schedule part, go back to crontab -e and put a # sign in front of step 5 code. Only part im confused with is why add each individual google video in the block list if its available when adding them to the adlist, the other part..... the list isn't matching up to direct them to 127.0.0.1 to be blocked. |
Thanks @91ajames but I'm not really understanding your instructions. Sorry but I'm a newbie at this and I'm not clear on what step 5 is of the code. Any chance you can spell it out for me? |
Not a problem @dvpetta crontab -e
to
any code with the pound edit... |
same problem, this list is overblocking, if I put for example "r3---sn-i5h7lner.googlevideo.com" to whitelist, I can watch a video. |
I believe youtube has switched to serving ads and content from the same servers. I've been watching my Firefox and Chrome network inspectors and if I sort by Domains and compare what's downloading during an ad playing vs what's downloading during. With this blocklist enabled sometimes youtube will play and the ads will be blocked, sometimes the video won't load at all and you need to reload the page to try again (getting a different server in the process), and sometimes both ads and content will play. |
Hello
I'm having trouble viewing videos now on my Android TV after installing your code on my rasberry pi with pi hole. It seemed like I had ads blocked for the first video but since then I only get ads and no videos. Is there a way to inspect what has happened in pi hole to fix this?
The text was updated successfully, but these errors were encountered: