TV Everywhere & Hulu - Possible NBC Universal Issue?

Issue is related to TV Everywhere and Hulu.

Yesterday, I lost about half of my channels. It looks like Viacom and NBCUniversal owned channels seem to be errored out. I updated to pre-release, and now I can't sign in to Hulu at all, and the error given is what I was seeing with the channels in question yesterday:

could not dial "ws://127.0.0.1:38293/devtools/browser/579a5a4d-390c-4327-aac7-b3c953b142c8": EOF

Looking at the logs:
2021/02/09 10:01:31.456773 [TVE] Channel scan finished after 25s: 65/213 channels available
2021/02/09 10:06:27.536520 [TVE] Auth starting for Hulu as (email address redacted)
2021/02/09 10:06:27.536615 [TVE] action=auth mvpd=Hulu requestor=nbcentertainment
2021/02/09 10:06:27.833889 [TVE] Auth failed for Hulu: could not dial "ws://127.0.0.1:42377/devtools/browser/b6216eb2-038d-4183-873a-5145efc7f275": EOF
2021/02/09 10:06:57.017027 [TVE] Auth starting for Hulu as (email address redacted)
2021/02/09 10:06:57.017135 [TVE] action=auth mvpd=Hulu requestor=nbcentertainment
2021/02/09 10:06:57.301774 [TVE] Auth failed for Hulu: context canceled
2021/02/09 10:11:13.441563 [TVE] Auth starting for Hulu as (email address redacted)
2021/02/09 10:11:13.441614 [TVE] action=auth mvpd=Hulu requestor=nbcentertainment
2021/02/09 10:11:13.730748 [TVE] Auth failed for Hulu: could not dial "ws://127.0.0.1:38293/devtools/browser/579a5a4d-390c-4327-aac7-b3c953b142c8": EOF

Looks like there is an issue with NBCUniversal channels, can anyone else confirm? I know there is a similar thread here: MSNBC not working on TVE T-Mobile Source

I can post a full channels log if needed

Your chrome installation is broken. Which Linux distro are you using?

Debian with DietPi on VM

Try this:

apt-get install chromium-browser
chromium --version

Currently at Chromium 88.0.4324.146

I've done a remove/purge of Chromium, and did a reinstall.

Still at Chromium 88.0.4324.146 built on Debian 10.7, running on Debian 10.8

Should I consider downgrading?

Yea if it was working before then maybe switch back to an older build?

On Ubuntu there are some known issues with their snap but that should affect Debian..

Never had snap installed on my VM. Tried that out:

snap install chromium
error: cannot perform the following tasks:

  • Mount snap "chromium" (1479) (snap "chromium" assumes unsupported features: snapd2.43 (try to update snapd and refresh the core snap))

Seems like I can't pull the version required, snapd needs to be at a later version, but I don't think Debian has a later version available to meet the reqs.

Tried apt-get install chromium=87.0.4280.141-0.1~deb10u1

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
chromium : Depends: chromium-common (= 87.0.4280.141-0.1~deb10u1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Don't know if that's a limitation of DietPi or not. Tried some clearing of the cache, and verified no held apps.

Issue occurred on 2/8 around 8pm for the first time. Chromium was updated after the fact to try and resolve the issue, so this occurred before the update happened.

Are you still getting the "could not dial" error in the logs?

Is there any kind of firewall running inside the VM maybe?

What if you apt-get remove chromium-browser what is the error message then?

When I try without Chromium installed (in this case it is just apt-get remove chromium), I get: "Cable provider authentication failed" and a screenshot of the Hulu login page. Log below:

2021/02/10 13:57:27.636844 [TVE] Auth starting for Hulu as (email redacted)
2021/02/10 13:57:27.636886 [TVE] action=auth mvpd=Hulu requestor=nbcentertainment
2021/02/10 13:57:27.637631 registry.ping url=https://registry-1.docker.io/v2/
2021/02/10 13:57:28.167263 registry.manifest.get url=https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/76.0.3805.2 repository=chromedp/headless-shell reference=76.0.3805.2
2021/02/10 13:57:28.596564 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:dff99e741a048ce33cac108df4b135733346a2a9cc027f316e834a9a4a932c7c repository=chromedp/headless-shell digest=sha256:dff99e741a048ce33cac108df4b135733346a2a9cc027f316e834a9a4a932c7c
2021/02/10 13:57:30.088155 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:4b83ef502c3194487b328f71a8e95789c2574bdd783840bfba1997a9bd3acbb4 repository=chromedp/headless-shell digest=sha256:4b83ef502c3194487b328f71a8e95789c2574bdd783840bfba1997a9bd3acbb4
2021/02/10 13:57:30.745712 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:54154f627d69b6cdc27e9ca2475980b0d5266c1d4bbf450fa3cc2a7541d1506a repository=chromedp/headless-shell digest=sha256:54154f627d69b6cdc27e9ca2475980b0d5266c1d4bbf450fa3cc2a7541d1506a
2021/02/10 13:57:33.659058 [TVE] action=xvfb
2021/02/10 13:57:33.756686 [TVE] action=error_response type=Other error=net::ERR_UNKNOWN_URL_SCHEME
2021/02/10 13:57:33.761057 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=Hulu&requestor_id=nbcentertainment&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2021/02/10 13:57:33.762364 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2021/02/10 13:57:33.922027 [TVE] action=request type=Document method=GET url=https://auth.hulu.com/oauth2/login
2021/02/10 13:57:33.922050 [TVE] action=auth_domain domain=.hulu.com
2021/02/10 13:57:34.169469 [TVE] action=wait_for_page
2021/02/10 13:57:40.730131 [TVE] action=page_ready
2021/02/10 13:57:40.730173 [TVE] action=wait_for_page done=true reason=page_ready
2021/02/10 13:57:40.730188 [TVE] action=fill_form u=(email redacted)
2021/02/10 13:57:40.738584 [TVE] action=tvecaptcha step=start
2021/02/10 13:57:40.738970 [TVE] action=wait_for_auth
2021/02/10 13:57:40.738990 [TVE] action=click_captcha x=170 y=472.8999938964844
2021/02/10 13:57:42.793228 [TVE] action=captcha_screenshot pos=0,0 size=800,600 bytes=21358
2021/02/10 13:57:42.793365 [TVE] action=captcha_check
2021/02/10 13:57:42.795068 [TVE] action=tvejs msg="recaptcha found=true width=300 y=-9999"
2021/02/10 13:57:42.795192 [TVE] action=tvecaptcha step=continue ratio=1
2021/02/10 13:58:42.795388 [TVE] action=auth_timed_out
2021/02/10 13:58:42.795430 [TVE] action=screenshot
2021/02/10 13:58:42.858234 [TVE] action=screenshot size=21358
2021/02/10 13:58:42.858363 [TVE] action=capture_html
2021/02/10 13:58:42.864096 [TVE] action=capture_html size=47096
2021/02/10 13:58:42.902591 [TVE] Auth failed for Hulu: Cable provider authentication failed

Still have the same failure when logging in after reinstalling Chromium: could not dial "ws://127.0.0.1:32835/devtools/browser/d8f017e8-fc78-4ab1-86e2-783b97ea04a7": EOF

2021/02/10 14:03:48.327680 [TVE] Auth starting for Hulu as (email redacted)
2021/02/10 14:03:48.327724 [TVE] action=auth mvpd=Hulu requestor=nbcentertainment
2021/02/10 14:03:48.328265 [TVE] action=xvfb
2021/02/10 14:03:49.600621 [TVE] Auth failed for Hulu: could not dial 
"ws://127.0.0.1:32835/devtools/browser/d8f017e8-fc78-4ab1-86e2-783b97ea04a7": EOF

Sounds like the built-in chrome is working, so just uninstall the package. You will need to watch the screen and complete the captcha for Hulu login to finish.

Uninstalled Chromium.

I don't seem to have that option to click when I authenticate. I gave the service a restart before starting. I let it spin, and then it fails with the screen shot. Can't click on anything inside the image, which I expected. I am accessing the machine from another internal IP, the VM is headless. Is this supposed to be done on the host machine with display? I can't click on anything.

Hmm, what browser are you using to access the web UI? Before it says "Cable provider auth failed", it should say "Please complete Captcha below". Maybe try another browser.

That was it. Very weird

Problem browser was Brave browser. Used Safari without issue.. other than tens of CAPTCHAS to rifle through haha (not the app's fault!). Normally I have not had issues re-scanning Channels in the past using Brave, but I assume that is because Chromium was on the local server acting as the medium. Guess that can't walk through CAPTCHA on its own?

Thanks for your patience in walking through all of this with me. First time I have come across a major issue with the app.