I need help, nothing below 6101 on my channels guide will tune in, it clocks and then give the following message: Connection Lost - Tuner Unreachable
Please go to Support -> Troubleshooting -> Submit Diagnostic Logs from the web interface of the DVR and let us know when it's been submitted so we can have a better idea of what was going on.
Done, let me know if you got them.
Please try updating to the latest pre-release and let us know if that helps the situation.
Things are working again with the pre-release, but my 6101 Discovery channel is no longer listed in the guid. Pulling in on Spectrum source.
From 6101 Discovery...to 6114 I'm getting "no login form found".
Did you try to rescan the individual channels?
1 Like
Yes, I have tried rescan each one; one at a time. No longer coming in.
You could try following these TVE Troubleshooting tips
Probably steps 9 & 10, but start from #1 
1 Like
6100–6114 (OWN to MotorTrend) are all of the WBD channels. For the past week or so there have been intermittent problems with several Discovery networks; this is likely related, and indicates it's likely an issue on their end.
I can’t tell you how many times I’ve referred to your list of TVE tips. Just in case no one has thanked you on these forums, thanks.
1 Like
Thanks @Suds
Hopefully it has helped some users. It started as a text document I made after seeing common causes for TVE issues. Most of the info in it was spread around the forum, so I decided to post it, making it easier to point to one reference.
keep hoping there will be a fix soon. I able to watch streaming from Chrome form their site, but no love from ChannelDVR (TV Everywhere). Keep checking daily.
What server device and OS is your Channels DVR installed on?
QNAP T2-253D Firmware QTS 5.0.1.2425 Memory 8GB
Do you know what version of headless chrome is being used by Channels DVR on it?
My guess is v97. It shows in the DVR log whenever Channels DVR has to authenticate with a network.
Example from a Docker Container install below using v109
2023/08/07 20:25:43.366621 [TVE] action=version product=Chrome/109.0.5414.74 jsVersion=10.9.194.9 protocol=1.3 revision=@e7c5703604daa9cc128ccf5a5d3e993513758913
If it is running v97, my guess is that's the problem. I quit running in a Synology package and migrated to a docker container to get the newer version chrome.
No, I have no idea. QPKG (Channels DVR Server 1.1.0) is install on the QNAP TS-253D and we use Fire TV to watch Channel DVR.
OS
QNAP TS-253D
Linux
(kernel: 5.10.60-qnap)
CPU
4 cores / Intel(R) Celeron(R) J4125 CPU @ 2.00GHz
load averages: 2.78 1.95 1.61
RAM
3.68 GB
49.6% free
I found the header. product=Chrome/97.0.4692.56
2023/08/14 06:51:02.568381 [HTTP] | 200 | 888.065952ms | 172.16.0.41 | GET "/tmsimg/assets/s56905_ll_h15_ad.png"
2023/08/14 06:51:02.827406 [TVE] action=version product=Chrome/97.0.4692.56 jsVersion=9.7.106.18 protocol=1.3 revision=@04da6c66398ca50e603cc236a07dc7dfd3bbc750
2023/08/14 06:51:02.828350 [TVE] action=navigate url=https://auth.sciencechannel.com/login-affiliates?returnUrl=https://www.sciencechannel.com/live-now&hostUrl=us1-prod-direct.sciencechannel.com
2023/08/14 06:51:02.830152 [TVE] action=request type=Document method=GET url=https://auth.sciencechannel.com/login-affiliates
2023/08/14 06:51:02.830175 [TVE] action=auth_domain domain=auth.sciencechannel.com
2023/08/14 06:51:02.830182 [TVE] action=scienceauth reason=login
2023/08/14 06:51:02.862138 [HTTP] | 200 | 898.719µs | 172.16.0.30 | GET "/devices/TVE-Spectrum/status/0-38/debug"
2023/08/14 06:51:02.935032 [HTTP] | 200 | 57.854µs | 172.16.0.41 | GET "/updater"
2023/08/14 06:51:03.134572 [TVE] action=wait_for_page
current version of chrome is 115.0.5790.171
Yes, but like the Synology package it's something the devs need to update
Or he can migrate the install to a Docker Container which works and is currently maxed out at headless-chrome v109