support gave me a trial for the live tv bundle since I was already a hulu subscriber
1 Like
Run the troubleshooting on the server. It’s under support. Does it show anything in red? Chrome version??
TV Everywhere
Chrome version is out of date: 89.0.4389.114
Remote Access
Could not connect to a5db24797623.u.channelsdvr.net. Check if the port is mapped.
updated chrome and reran and got yellow warning but no red other than the remote access again
DNS
Using public DNS resolver from "Cloudflare, Inc." can cause problems with TV Everywhere
still not able to add Hulu though
No way you should be getting that if you're using the latest :tve docker image.
2024/03/27 14:43:08.692819 [TVE] action=version product=Chrome/120.0.6099.129 jsVersion=12.0.267.10 protocol=1.3 revision=@204016af461e03117aa3858b51ba4534c7cfda81
2024/03/27 14:43:08.695450 [TVE] action=page_ready chromeVersion=120
TV Everywhere
Chrome version up to date: 120.0.6099.129
i don't know what I did wrong...I updated it and its not giving an error any more...
Does troubleshooting show you have v120 now?
Can you add Hulu?
I would suggest getting chrome up to date to 120 and using isp dns at least until adding is successful.
yes no more red for Chrome in the troubleshooter but I still cant add Hulu
its up to date now...I havent changed the dns so far
Try restarting the docker container and run Troubleshooting again to make sure Chrome is still at v120
Might also want to check the DVR log.
Last time I added Xfinity-TVE, it started auth at HGTV before scanning channels.
See where the log says it's authing at and try to login that network live website with Hulu. It might be having an issue.
2024/01/26 17:26:24.783061 [TVE] Auth starting for Comcast_SSO as <username>
2024/01/26 17:26:29.043249 [TVE] action=auth mvpd=Comcast_SSO requestor=HGTV
2024/01/26 17:26:29.155907 [TVE] action=xvfb display=:607
2024/01/26 17:26:32.169997 [TVE] action=version product=Chrome/120.0.6099.129 jsVersion=12.0.267.10 protocol=1.3 revision=@204016af461e03117aa3858b51ba4534c7cfda81
2024/01/26 17:26:32.234878 [TVE] action=page_ready chromeVersion=120
...
2024/01/26 17:27:09.667223 [TVE] action=authed
2024/01/26 17:27:09.671713 [TVE] action=cookies num_domains=2 num_cookies=33
2024/01/26 17:27:10.659208 [TVE] Channel scan starting for 173 channels on Comcast_SSO
2024/01/26 17:27:10.767296 [TVE] action=auth mvpd=Comcast_SSO requestor=C-SPAN
Took me awhile to search for this one.
You should be running the newest docker image for tve (Jan 5, 2024).
https://hub.docker.com/r/fancybits/channels-dvr/tags?page=1&ordering=last_updated
https://hub.docker.com/layers/fancybits/channels-dvr/tve/images/sha256-e59b99dcadcc75540a814d8199d0d7deba1f77f71cc2d225a3b5a3efe044781b?context=explore
That INDEX DIGEST
sha256:3188e18fd56eff49f86e00bfbd57c76293bbb7b51bb61cb34558a39946d7a7e3
Matches my image RepoDigests fancybits/channels-dvr@
sha256:3188e18fd56eff49f86e00bfbd57c76293bbb7b51bb61cb34558a39946d7a7e3
# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
fancybits/channels-dvr tve 968a63d0cda4 2 months ago 635MB
# docker inspect 968a63d0cda4
[
{
"Id": "sha256:968a63d0cda4c224266b5205e240de93fd9c96854b7196ae8688da10962ec0c3",
"RepoTags": ["fancybits/channels-dvr:tve"],
"RepoDigests": ["fancybits/channels-dvr@sha256:3188e18fd56eff49f86e00bfbd57c76293bbb7b51bb61cb34558a39946d7a7e3"],
"Parent": "",
"Comment": "buildkit.dockerfile.v0",
"Created": "2024-01-05T23:32:39.533250652Z",
FINALLY!!!!
After restarting Docker and the Channels session the login for Hulu FINALLY asked me for an authorization code. I got it from my email and now it is scanning for channels.
THANK YOU all for your help!!!
Hopefully it stays logged in...BUT if it doesn't how do you know when a source has lost authorization?
The entire Hulu source won’t loose its authentication all at once. Typically for me it’s mainly just the discovery family. When it is failing my email will get a bunch of emails as it’s repeatedly trying and failing to do a recording. It doesn’t happen a lot but a couple times a year.
There seems to be something specific with Hulu authentication in a headless browser that doesn't appear to apply to other services. I've been dealing with this in a totally unrelated automation. When the browser is visible, login works 100% of the time. However, when it is headless, it works like 5% of the time. I cannot for the life me figure out why... yet!
When that happens, do you just rescan those individual channels one at a time to get them back?
My issue is always that Hulu says my password is incorrect when it is correct. It’s a Hulu issue not channels. Just trying to login to Hulu’s site fails with a web browser. Going through the password reset on their site will fail. So I’ll pretty much not do anything with the dvr until Hulu decides to let me in. Then I’ll just tune to the channel and it will authorize usually. If not I update the password in channels with same password twice and rescan the individual channels. I never remove Hulu as a source because I’ll lose all my channels. I do all this on the server machine chrome web browser. Whatever the issue is Hulu phone support can fix it on their end but they won’t explain why it happens. Typically I’ll just wait it out for a couple hours and it will work.
Even with this it’s still better than spectrum. I would lose discovery family channels for days waiting for them to tell discovery that they are part of my subscription each month.
2 Likes
do your channels lose access to the tuners a lot? it has happened a few times on me...
No. If that is happening to you it’s not a Hulu thing, once a channel is authorized it uses the same tve source as all the rest. Above you have fubo as a source. Hulu and fubo get the stream from the same place along with all the other tve providers.
My guess is losing tuners is a symptom of you using non isp provided dns servers. The devs have more than once stated tve can have issues using non isp DNS servers.
ok I will check it out...thanks