I have a Roku TV with a brand name of Sharp. It works fine and I can watch streaming apps, but when you run a network test it says that it is connected to the network (in my case a wired ethernet connection) but that the TV is not connected to the internet.
Could this be a Pi-hole issue? Has anyone else seen this.
I tried disabling Pi-hole for five minutes, which didn’t change things, but I wonder if something needs to be reset on the Roku TV.
Could this be a Pi-hole issue?
Absolutely.
I tried disabling Pi-hole for five minutes, which didn’t change things
If the client still had a cached record with a valid TTL, it’ll use it. To test this stringently, you would need to take the client down also to guarantee it gets a new record.
If you are blocking a domain the TV uses as it’s connectivity check address then yes, it will return an offline error. Check your logs and determine what is getting blocked.
I run a dual pi-hole setup through the router (full network pi-hole) and have multiple roku devices – tv’s and sticks. No issues like that here.
So today it seems that when I run Check connection it works with wired ethernet, but not when I try to switch to wifi, then it still fails. Strange, but everything is good for now.
By the way, I was always able to use streaming apps but the internet test would fail.
FYI, I am running Pi-hole in a docker container on an unRAID server.
I’m no pro, but if your pihole is disabled and it’s not working it almost can’t be the pihole. You could try setting your DNS to cloud flare for a few minutes so it completely bypasses the pihole. And see if that does anything.
Could be one of your block lists is blocking something your smartTV uses which causes the Roku to indicate no internet connection. Generally no issues, for several years now, with a Roku Ultra and the green check marked default Firebog.net (https://firebog.net/) block lists on dual Pi-Holes.
Edit to add: Have noticed recently that my Roku Ultra tends to flood the Pi-Hole(s) with scribe.logs.roku.com DNS requests/lookups, typically once or twice a day for a minute or two. This has, one time, caused the Pi-Hole to throw a RATE_LIMIT diagnostic message about too many requests in a 60 second period. I typically don’t notice any issues so I’ve been ignoring the messages in Pi-Hole.
You need to look at the pihole logs and filter by the roku client and the TV client. See what they are trying to look up and what is getting blocked. You can whitelist some or all of that if you wish.
there some domain that you need to white because there are included in your ad list block it can cause some apps to not work on roku. you need pinpoint which one was it to whitelist those.
Example this one “edgekey.net” it will cause playback problem if you dont whitelist it. the app will exit and bring you back to roku menu.
Pi-hole updates lists at a pseudorandom time in the small hours of each Sunday morning by default.
I imagine there would very likely be a strong correlation between “what is X domain?”, “why did X stop working”, “is it possible Pi-hole broke X?” related posts here and on the Pi-hole Discourse, with Sundays and Mondays.
Probably also directly proportional to the amount and quality of user added lists.
So what you’re saying is, they can’t connect to the ad servers, so the whole device just refuses to work?
If this is the case though, it would’ve worked if he disabled the pihole for a bit right?