Lately I have noticed that when I select a TVE channel the wheel spins a really long time before the connection is made. Usually it only took a couple of seconds, now it can take upwards of 30 seconds.
Some channels are worse than others.
I am on the latest beta for my DVR and my Apple TV. Internet connection is Google Fiber, so not a speed issue.
Any ideas?
Usually happens if you have multiple TVE sources and the first one listed is not working for some reason.
I do. I have Directv and YTTV. YTTV is first in the list. Should i swap them or just turn off the channels that are duplicated between the two?
Check your logs, see if the YTTV channels are failing. You may need to remove/readd YTTV. You can also adjust source priority and move DTV first.
i did a search for "error" and got a lot of these
2021/10/18 12:07:46.169917 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED url=https://s.go-mpulse.net/boomerang/VXRZ2-6J5FA-2D937-2WYLU-6J9RG
2021/10/18 12:07:46.245246 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED url=https://apv-launcher.minute.ly/api/launcher/MIN-50100.js
2021/10/18 12:07:46.245461 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED url=https://cdn.optimizely.com/js/17902805246.js
2021/10/18 12:07:46.246639 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED url=https://websdk.appsflyer.com/
2021/10/18 12:07:46.248097 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED url=https://s.go-mpulse.net/boomerang/VXRZ2-6J5FA-2D937-2WYLU-6J9RG
2021/10/18 12:07:46.678325 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED url=https://cdn.segment.com/analytics.js/v1/nZKOCs4zQ7sYYrXWnMX12o0ZzMijA5Yj/analytics.min.js
2021/10/18 12:07:46.685412 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED url=https://tags.tiqcdn.com/utag/foxcorp/fscom-main/prod/utag.js
2021/10/18 12:07:46.709563 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED url=https://bam.nr-data.net/1/cf1b711708
That's just your adblocker.
Does http://10.20.1.2:8089/providers/tve/error_screenshot.png show any YTTV page or errors
Hard to say with limited info. Did moving DTV first help? Maybe you need to do it on the client too.
You can submit diagnostics and contact support
I have rescanned all channels on both sources. Will watch it over the next day and see if there is a change.
Does running my network wide adblocker cause issues for Channels?
If it uses domain-based blocking and blocks one of the many domains that may be used for TVE access, yes. Might be worth temporarily disabling it to see if the issues clear up.
I use nextdns for add blocking at the dns level. I found about 10 tve stations were not working. I just changed the dns for my channels server to 8.8.8.8 and everything worked great. I really didn't need an add blocker for channels anyway...
Well it’s all working perfect today but I did two things and not sure which was the fix. I rescanned my TVE sources, and I removed DNS filtering from my server. Channels tune in super fast now.
What kind of DNS filtering were you using? If you're able to test turning it back on and see if it makes things slow again, that would be helpful.
We're trying to teach the DVR to detect these kind of DNS setup issues as part of troubleshooting.
sure, I can send that server through nextdns and see what happens.
I can send you the nextdns logs too if that helps.
Yea that would be great. Once you notice issues, submit diagnostics from the dvr and email us the dns logs. Thanks!
I use nextdns as well and I just created a seperate profile that is unfiltered. I have the nextdns freebsd package installed on my pfsense router. I put the Mac address of the channels server in there to use the non filtered dns profile. Works perfect and now I have no issues with TVE.
I juts felt like DNS filtering on the channels server was unnecessary.
I was using NextDNS network wide on my entire system, running a CLI in my ASUS router. But I noticed some slowdowns with TVE authentication that may have been attributed to all my filters. Or maybe not, since at that time is when YTTV authentication was wonky too. I also noticed that because I am a Google Fiber customer that using NextDNS was not always routing my streaming devices to local content delivery servers on the GF network.
Since then I run NextDNS directly only on my computers that need it and no longer filter all of my devices.
So for this test I have installed the NextDNS app on the Mac that is my Channels DVR server and it is getting fully filtered. See what happens.
