I’m just curious about how often headless chrome gets updated. I’ve been checking the troubleshooting tab on an almost daily basis, and every time I check it shows up as out of date. I tell it to update and it does but then a day later it shows as out of date again. Is headless chrome really being updated for raspberry pi that often? I’ve got channels on a raspberry pi running raspberry pi os. I update my raspberry pi weekly so it’s not like I’m letting the OS get out of date. It just seems like it happens a lot, so I’m wondering if something else could be going on.
Some details may help narrow this down. Which version of the OS are you running? Which version of Chromium is installed and marked as out of date? After updating, which version of Chromium is installed? And when you reboot/recheck the Chromium version, which version is being indicated as installed and out of date?
Also, have you restarted the device at all between the checks?
2 Likes
I have noticed this issue also. I have submitted logs and have a support ticket open. I have three Channels instances running. Two of them are in separate VM's running Ubuntu Server 16.04. On these two if I update chromium-browser manually it shows up-to-date. @tmm1 told me to update the Ubuntu version or ignore the error. I'm unwilling to update those for specific reasons. On those two instances the out-of-date version shows 90.0.4430.72.
This also happens on my main Channels Server that runs on Unraid 6.11.5 (also did it on 6.9.2) in a Docker container (fancybits/channels-dvr:tve) but it also shows out-of-date version 89.0.4389.72. I have asked about that one in the same support thread but have not gotten a response.
On all three of these after I click on the "click here to update chrome" it shows that it updated and will pass with a green check mark if I try it again. But just like @andi330 says, I'll go back a day or two later and run it and it reverts back to being out-of-date with the same version it showed prior to updating. I leave mine running and don't update unless I have a reason to or a forced update is applied. I don't see a pattern if I reboot either. I started noticing it when the latest stable version v2022.11.15.1908 was released and have tried several pre-releases since including the up-to-date pre-release v2022.12.12.0138.
I'm not too concerned about it because it doesn't seem to be causing an issue as of yet. More of an annoyance than anything.
1 Like
I’ll try to get some of the details asked for above tomorrow. I haven’t had the energy to look at it today. But I can say that I keep my raspberry pi and all of its software up-to-date on a weekly basis. I do the sudo apt get update and sudo apt full-upgrade commands on a weekly basis. So everything should be pretty up-to-date. I always reboot after doing the weekly updates. I can see occasionally an update dropping after I’ve updated for the week, but this seems to be constant. I’ve noticed it recently because I use Xfinity for TVE and I’ve noticed some scheduled items not recording. I also use a VPN, so that may not be the only issue, but I often find that if I go in and check troubleshooting and tell it to update headless chrome, the problem goes away (the exception to this seems to be ABC which does seem to sometimes catch on to the VPN in a way that most of my other channels don’t). I haven’t made note of the version of headless chrome, but I’ll try to the next few times I’ve checked. I posted here at first because I had a feeling that the numbers looked the same as last time, but I haven’t actually tracked the version numbers to be sure.
1 Like
To see what version of Chrome is being used by Channels DVR, search the DVR log for action=version product=
or
jsVersion=
[TVE] action=version product=Chrome/97.0.4692.56 jsVersion=9.7.106.18 protocol=1.3 revision=@04da6c66398ca50e603cc236a07dc7dfd3bbc750
I know of two ways to get Channels DVR to update the Chrome it uses.
- When Troubleshooting says it's out of date or corrupted and you click the Fix button
- When you add a TVE source and click and HOLD the Sign In button
There's a hack using #2 where you add a TVE source using a Provider you don't use just to update Chrome.
Just use test or something for username and password, then click and HOLD the Sign In button.
In either case you can check the DVR log to see the version it installed.
registry.ping url=https://registry-1.docker.io/v2/
registry.manifest.get url=https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/97.0.4692.56 repository=chromedp/headless-shell reference=97.0.4692.56
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:ffbb094f4f9e7c61d97c2b409f3e8154e2621a5074a0087d35f1849e665d0d34 repository=chromedp/headless-shell digest=sha256:ffbb094f4f9e7c61d97c2b409f3e8154e2621a5074a0087d35f1849e665d0d34
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:9b14f784f92a19552c6301741f4299a599c5ddd79c4d2343f449baabc840079b repository=chromedp/headless-shell digest=sha256:9b14f784f92a19552c6301741f4299a599c5ddd79c4d2343f449baabc840079b
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:a315ff4312e7298a86768350b0385281a5532eb1f8497f4680de8e3189a07894 repository=chromedp/headless-shell digest=sha256:a315ff4312e7298a86768350b0385281a5532eb1f8497f4680de8e3189a07894
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:8a83912a086faffe21f33bc6cb5a881bcb61ff7a23d0b8bfa9198fe9ddb54dd9 repository=chromedp/headless-shell digest=sha256:8a83912a086faffe21f33bc6cb5a881bcb61ff7a23d0b8bfa9198fe9ddb54dd9
[TVE] action=version product=Chrome/97.0.4692.56 jsVersion=9.7.106.18 protocol=1.3 revision=@04da6c66398ca50e603cc236a07dc7dfd3bbc750
This example is from my Channels DVR Synology package install (not a Docker container)
version product=HeadlessChrome/108.0.5359.94 jsVersion=10.8.168.21 protocol=1.3
1 Like
Thanks, updated my post to search for
action=version product=
or guess you could search for
jsVersion=
This one is from a Docker container installation
TV Everywhere
Chrome version is out of date: HeadlessChrome/89.0.4389.72
Click here to upgrade Chrome
After clicking the upgrade Chrome button
registry.ping url=https://registry-1.docker.io/v2/
registry.manifest.get url=https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/97.0.4692.56 repository=chromedp/headless-shell reference=97.0.4692.56
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:ffbb094f4f9e7c61d97c2b409f3e8154e2621a5074a0087d35f1849e665d0d34 repository=chromedp/headless-shell digest=sha256:ffbb094f4f9e7c61d97c2b409f3e8154e2621a5074a0087d35f1849e665d0d34
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:9b14f784f92a19552c6301741f4299a599c5ddd79c4d2343f449baabc840079b repository=chromedp/headless-shell digest=sha256:9b14f784f92a19552c6301741f4299a599c5ddd79c4d2343f449baabc840079b
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:a315ff4312e7298a86768350b0385281a5532eb1f8497f4680de8e3189a07894 repository=chromedp/headless-shell digest=sha256:a315ff4312e7298a86768350b0385281a5532eb1f8497f4680de8e3189a07894
registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:8a83912a086faffe21f33bc6cb5a881bcb61ff7a23d0b8bfa9198fe9ddb54dd9 repository=chromedp/headless-shell digest=sha256:8a83912a086faffe21f33bc6cb5a881bcb61ff7a23d0b8bfa9198fe9ddb54dd9
[TVE] action=version product=HeadlessChrome/89.0.4389.72 jsVersion=8.9.255.20 protocol=1.3 revision=@3f345f156bfd157bd1bea06310e55f3fb2490359
Hmmm, that doesn't look like it updated Chrome to me.
Troubleshooting still shows it out of date.
TV Everywhere
Chrome version is out of date: HeadlessChrome/89.0.4389.72
Click here to upgrade Chrome
Same after restarting the Docker container.
Yeah, it shows it updated but it doesn't "keep" the update after it is installed. As you can see it appears to update it to 97.0.4692.56 on 12/16 at 14:04 but almost 6 hours later the version it shows it is using is back to 89.0.4389.72.
2022/12/16 14:04:27.222546 registry.ping url=https://registry-1.docker.io/v2/
2022/12/16 14:04:28.225317 registry.manifest.get url=https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/97.0.4692.56 repository=chromedp/headless-shell reference=97.0.4692.56
2022/12/16 14:04:29.392748 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:ffbb094f4f9e7c61d97c2b409f3e8154e2621a5074a0087d35f1849e665d0d34 repository=chromedp/headless-shell digest=sha256:ffbb094f4f9e7c61d97c2b409f3e8154e2621a5074a0087d35f1849e665d0d34
2022/12/16 14:04:32.309972 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:9b14f784f92a19552c6301741f4299a599c5ddd79c4d2343f449baabc840079b repository=chromedp/headless-shell digest=sha256:9b14f784f92a19552c6301741f4299a599c5ddd79c4d2343f449baabc840079b
2022/12/16 14:04:33.069012 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:a315ff4312e7298a86768350b0385281a5532eb1f8497f4680de8e3189a07894 repository=chromedp/headless-shell digest=sha256:a315ff4312e7298a86768350b0385281a5532eb1f8497f4680de8e3189a07894
2022/12/16 14:04:35.050427 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:8a83912a086faffe21f33bc6cb5a881bcb61ff7a23d0b8bfa9198fe9ddb54dd9 repository=chromedp/headless-shell digest=sha256:8a83912a086faffe21f33bc6cb5a881bcb61ff7a23d0b8bfa9198fe9ddb54dd9
2022/12/16 19:54:34.263450 [TVE] action=version product=HeadlessChrome/89.0.4389.72 jsVersion=8.9.255.20 protocol=1.3 revision=@3f345f156bfd157bd1bea06310e55f3fb2490359
1 Like
Agree. Either the updated install failed or it downloaded but isn't running it.
I really don't care at this point as I don't use Docker for TVE and my two servers with TVE sources are running from a Synology package install where the Chrome update actually works.
I think you guys might find this interesting and maybe the developers will too. I have clicked on update to the latest chrome version.
It runs this deal and then tells me it is up to date. I can restart the docker image and still shows it is updated.
registry.manifest.get url=https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/97.0.4692.56 repository=chromedp/headless-shell reference=97.0.4692.56
As soon as I uncheck the Local Networks via TV Everywhere and re-check it.
The Click here to upgrade Chrome comes back. So could it be that it upgrades and then downgrades the chrome version?
My guess
I would believe it didn't install. But I can go days checking the support troubleshooting and it tells me it is up to date. I can restart the virtual server it still tells me its up to date. Uncheck that TV Everywhere and re-check it. Then now its out of date on the Troubleshooting page.
I honestly think something rolls it back.
P.S. only reason I noticed it was that my fox channel stopped working again.
~$ cat /volume1/docker/channels-dvr/data/chromedp-version
HeadlessChrome/89.0.4389.72
Maybe the executable is up to date (how to tell?)
But the chromedp-version file wasn't updated
Looks like the files were downloaded, so being used
~$ ls -l /volume1/docker/channels-dvr/data/chr*
-rw-r--r-- 1 root root 27 Dec 17 11:06 /volume1/docker/channels-dvr/data/chromedp-version
/volume1/docker/channels-dvr/data/chromedp-chroot:
total 80
drwxr-xr-x 2 root root 4096 Dec 17 11:03 bin
drwxr-xr-x 2 root root 4096 Dec 17 11:03 boot
drwxr-xr-x 2 root root 4096 Dec 17 11:03 dev
drwxr-xr-x 29 root root 4096 Dec 17 11:03 etc
drwxr-xr-x 3 root root 4096 Dec 17 11:03 headless-shell
drwxr-xr-x 2 root root 4096 Dec 17 11:03 home
drwxr-xr-x 7 root root 4096 Dec 17 11:03 lib
drwxr-xr-x 2 root root 4096 Dec 17 11:03 lib64
drwxr-xr-x 2 root root 4096 Dec 17 11:03 media
drwxr-xr-x 2 root root 4096 Dec 17 11:03 mnt
drwxr-xr-x 2 root root 4096 Dec 17 11:03 opt
drwxr-xr-x 2 root root 4096 Dec 17 11:03 proc
drwx------ 2 root root 4096 Dec 17 11:03 root
drwxr-xr-x 3 root root 4096 Dec 17 11:03 run
drwxr-xr-x 2 root root 4096 Dec 17 11:03 sbin
drwxr-xr-x 2 root root 4096 Dec 17 11:03 srv
drwxr-xr-x 2 root root 4096 Dec 17 11:03 sys
drwxr-xr-t 2 root root 4096 Dec 17 11:03 tmp
drwxr-xr-x 10 root root 4096 Dec 17 11:03 usr
drwxr-xr-x 11 root root 4096 Dec 17 11:03 var
~$ ls -l /volume1/docker/channels-dvr/data/chromedp-chroot/headless-shell
total 184608
-rwxr-xr-x 1 root root 189031736 Dec 17 11:03 headless-shell
drwxr-xr-x 2 root root 4096 Dec 17 11:03 swiftshader
I think this is similar to the issue I had. I had to actually insinstall chromium and then click fix and apparently channels installed it on its own. It refused to use the install I did per the instructions.
1 Like
The part I am reporting is a different issue. I never installed chrome on my debian os because I am running it inside a docker. I do think that original install with version 89. Troubleshoot page probably does update to 97. But then when you uncheck the local channel and then re-check it. It then calls on it to install the chrome 89 version again instead of checking if a newer version is already installed, or at least that is my hypothesis.
Guessing it's downloading this. Using headless chrome is over my head though.
https://hub.docker.com/r/chromedp/headless-shell/tags
Yup. They have much newer versions than what channels is using. But I guess you gotta go with what you know works.
Ok. I’ve been sick, and then out of town, but now I’m back so I can answer some of this.
OS Version: Raspbian GNU/Linux 10 (buster)
Chromium Version: 92.0.4515.98~buster-rpt2
I tried entering the command to install Chromium again to see if that would force a newer version to install and it says that this is the most recent version of Chromium for Raspberry Pi OS. I ran an update on my whole raspberry pi system using sudo apt update and sudo apt full-upgrade last night. I rebooted as soon as I did that. Last night it had a green check next to TV Everywhere, this morning it was back to saying it was out of date. I’m on the most recent pre-release 2022.12.22.0210
I do see that there are more recent versions of chromium in general for Linux, but not specifically for the Raspberry Pi OS. I wonder that is part of the issue. I have noticed that there some channels, like Freeform, that won’t work when the Headless Chrome is out of date. However, I also use a VPN because I am outside of the USA so it is possible that could be a VPN issue and not a Headless Chrome issue.
I posit this is the root of your issue. Most media companies blacklist known VPN endpoints.
1 Like