Getting context canceled message for Discovery networks

Channels DVR Server TV Everywhere
#1

I'm getting the message "context canceled" for all Discovery networks. After getting the message, I upgraded to the newest DVR beta version of 2022.01.27.0906 but I'm still getting the same message. My DVR server is an Ubuntu 18.04 machine. Here's the log file message I get when trying to rescan a Discovery network channel

2022/01/27 15:25:25.774201 [TVE] action=error_response type=Other error=net::ERR_UNKNOWN_URL_SCHEME url=
2022/01/27 15:25:25.775095 [TVE] action=version product=Chrome/89.0.4389.114 jsVersion=8.9.255.24 protocol=1.3 revision=@1ea76e193b4fadb723bfea2a19a66c93a1bc0ca6
2022/01/27 15:25:25.775486 [TVE] action=navigate url=https://auth.sciencechannel.com/login-affiliates?returnUrl=https://www.sciencechannel.com/live-now&hostUrl=us1-prod-direct.sciencechannel.com
2022/01/27 15:25:25.776170 [TVE] action=request type=Document method=GET url=https://auth.sciencechannel.com/login-affiliates
2022/01/27 15:25:25.776181 [TVE] action=auth_domain domain=auth.sciencechannel.com
2022/01/27 15:25:25.776186 [TVE] action=scienceauth reason=login

#2

Can you successfully login and watch at https://www.sciencechannel.com/channel/discovery
If so while that tab is open, open another tab to the dvr web ui and choose update password on the source with current password. Then rescan missing discovery’s individually

#3

Thanks for the suggestion. I was able to login to the link you provided and stream the discovery channel. I updated my password on the DVR UI with the current password and rescanned the discovery channel. I still get the "context canceled" message.

#4

Try sudo apt install chromium-browser

#5

I got the error "Unable to locate package chromium-browser" when I tried to install. Even after doing an apt update command. I then upgraded to Ubuntu 20.04 and still got the same error. However, I was able to install chromium through the snap command. The rescans are now working for the discovery networks. Thank you.

#6

I have the exact same old version and revision of Chrome.
Any way to update this headless chrome that Channels DVR installs?

registry.ping url=https://registry-1.docker.io/v2/
registry.manifest.get url=https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/89.0.4389.114 repository=chromedp/headless-shell reference=89.0.4389.114
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:1633fec4c8941cfbdde74459550ed95d255878d91ee08fb5894627cdf046fca0 repository=chromedp/headless-shell digest=sha256:1633fec4c8941cfbdde74459550ed95d255878d91ee08fb5894627cdf046fca0
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:f04fd593031a9b736187fbfac2f8e72fbe68bc9d65ca2eaeedf9f618e255d658 repository=chromedp/headless-shell digest=sha256:f04fd593031a9b736187fbfac2f8e72fbe68bc9d65ca2eaeedf9f618e255d658
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:71120124a9d579b544ff09506c59a81f5548dd2f19b278622307af04ef29e189 repository=chromedp/headless-shell digest=sha256:71120124a9d579b544ff09506c59a81f5548dd2f19b278622307af04ef29e189
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:5af79d440e20791028323fc0d80605674d6442a23dc49909a362e9f94b22cae4 repository=chromedp/headless-shell digest=sha256:5af79d440e20791028323fc0d80605674d6442a23dc49909a362e9f94b22cae4
[TVE] action=version product=Chrome/89.0.4389.114 jsVersion=8.9.255.24 protocol=1.3 revision=@1ea76e193b4fadb723bfea2a19a66c93a1bc0ca6
1 Like
#7

I suppose you could tell the system in the container to update the chromium package it has installed. Maybe something like:

docker exec -it channels sh -c "apk upgrade chromium"

(Of course, run at your own discretion, as I haven't found the need to update the Chromium version in the provided container; beware the copypasta.)

#8

It's installed via the Synology package, so not in a container.

docker container version: Chrome/89.0.4389.72  jsVersion=8.9.255.20 protocol=1.3 revision=@3f345f156bfd157bd1bea06310e55f3fb2490359
synology package version: Chrome/89.0.4389.114 jsVersion=8.9.255.24 protocol=1.3 revision=@1ea76e193b4fadb723bfea2a19a66c93a1bc0ca6
#9

I'm assuming that either means it wasn't the actual fix for Stacey_Simmans or was but it's only needed for Ubuntu. :man_shrugging:

#10

On my Ubuntu 20.04 I have Chromium 97.0.4692.99 snap. So it appears her chromium was old.

#11

Thanks. Problem with a Synology NAS is that packages are installed/updated/removed using their Synology Package Manager and there's no headless chrome package I could find.

#12

In the past the NAS packages' Chromium installs were updated via the Support > Troubleshooting page in the web UI; an out-of-date Chromium would include a "Fix" button that would update the internal browser.

#13

Correct.
Guess my question is if Stacey needed to update the exact same old version of Chrome that I have to fix the problem, why don't I or anyone else using it have to update?

1 Like
#14

I had Ubuntu 18.04 installed. I had done what racameron has stated to upgrade Chrome with the Fix button a couple months ago. Yesterday I started having issues with Discovery channels and only those channels. All other channels would validate just fine. I'm not sure why the newer Chromimum version of 97.0 allows the Discovery network channels to work and the older 89.0 version stopped working with Discovery network channels.

#15

Thanks for the reply.
Guess I'll wait until my Discovery channels fail to record or authorize and post.
Just figured if your Chrome was too old and I had the same version, well...

#16

Bundled chrome doesn't work on newer Ubuntu. You have to use the system package. Other platforms are not affected.

1 Like
#17

I am having the same problem on my Synology NAS "context canceled". I do not see a way to update chromium-browser. Is there a fix for Synlogy install?

#18

Try these TVE troubleshooting tips

  • If you can't watch the network at their Live streaming website, nothing Channels can do. Like nbc.com/live or check availability buttons at Channels Support - TV Everywhere Availability for your Provider
  • Make sure your package or container (if running in one) is up to date.
  • Update to the latest DVR prerelease version see this article for how
  • Run troubleshooting from the DVR web UI Support>Troubleshooting and make sure all green checkmarks. (If it says Chrome corrupted or not up to date it should offer a green fix button to press.)
  • Make sure your chrome or headless chrome is up to date. (Current included version is 89.0.4389)
  • Use Update Password under the gear dropdown next to your source in the DVR web UI and just key in your existing Provider password to clear the chromedata folder.
  • Reboot your server or restart your package or container if running in one.
  • Individually rescan channels with issues using Rescan Channels under the gear dropdown next to your source in the DVR web UI.
  • Remove and re-add your source.
  • If all the above fails, submit DVR diagnostics from the DVR web UI Support>Troubleshooting.
#19

No luck with these steps. I do not know how to update Chrome. However from the troubleshooting logs, it is reporting Chrome/89.0.4389.114.
When I try re-scanning, it just reports "Context Cancelled"

Logs show:
2022/01/29 13:22:05.861314 [TVE] action=error_response type=Other error=net::ERR_UNKNOWN_URL_SCHEME url=
2022/01/29 13:22:05.863804 [TVE] action=version product=Chrome/89.0.4389.114 jsVersion=8.9.255.24 protocol=1.3 revision=@1ea76e193b4fadb723bfea2a19a66c93a1bc0ca6
2022/01/29 13:22:05.864774 [TVE] action=navigate url=https://auth.sciencechannel.com/login-affiliates?returnUrl=https://www.sciencechannel.com/live-now&hostUrl=us1-prod-direct.sciencechannel.com
2022/01/29 13:22:05.867329 [TVE] action=request type=Document method=GET url=https://auth.sciencechannel.com/login-affiliates
2022/01/29 13:22:05.867376 [TVE] action=auth_domain domain=auth.sciencechannel.com
2022/01/29 13:22:05.867385 [TVE] action=scienceauth reason=login

Not sure what to do at this point, but starting using the Spectrum App instead of Channels.

#20

That chrome version is what's supplied and used by Channels DVR for headless servers.
If all the steps failed to fix it, the last step is to submit diagnostics from the DVR web UI.