Yes that’s correct. Update chrome function does not work when I choose it. Here’s what’s tricky, it doesn’t alway say that. Right now it doesn’t but other times it does. I THINK it happens after I try to add source but that’s only an educated guess
As far as time zone goes, all my devices including the qnap are accurate. The guide for the hdhr is also accurate. I’m not sure why it says that on the screen shot. I doubt that it’s related but if it is advice on fixing it is appreciated
I run Channels DVR in a couple docker containers and just add the timezone setting to the run command for the container. In my case it's
--env TZ=America/Los_Angeles
Something else I noticed about your screenshot and just occured to me what it is.
Looks like you're running an older Channels DVR TVE container image.
Yours says
Linux Alpine 3.10.3
Mine says
Linux Alpine 3.14.0_alpha20210212
I'm having the same issue with Xfinity. I am not using docker and am on the latest pre-release version. Let me know if there is anything I can provide to help!
This was just a fresh install on Friday. I deleted the previous installation as I was getting no response to my submitted tickets. (They just emailed me a question in the last few minutes.). I know no other way then to pull it as previously done.
As far as time goes, although I appreciate the help, that’s beyond my abilities. I think that’s ssh and I know nothing about it nor am I willing to learn just to use channels. This server was bought solely for channels usage although I use Plex for movies on very rare occasions.
I don't have a qnap, but sounds like you need to delete the old Channels DVR container image and pull the new one before creating and running the container.
Sorry, can't walk you through how to do it on your qnap.
I also seem to be having a similar TVE issue with Xfinity. My setup was working fine for months, but sometime in the last week we lost access to almost all of our channels. I've done the usual steps of removing Xfinity as a source and readding and updating to the pre-release software. Still no luck. Most channels are now showing as not part of our package even though they most definitely are. We went from over 200 TVE channels to less than 75 showing up. One example is AMC. Here are the logs when trying to rescan for AMC:
2021/11/30 09:58:48.146405 [TVE] action=auth mvpd=Comcast_SSO requestor=AMC 2021/11/30 09:58:48.858398 [TVE] action=error_response type=Other error=net::ERR_UNKNOWN_URL_SCHEME url= 2021/11/30 09:58:48.864521 [TVE] action=version product=HeadlessChrome/89.0.4389.114 jsVersion=8.9.255.24 protocol=1.3 revision=@1ea76e193b4fadb723bfea2a19a66c93a1bc0ca6 2021/11/30 09:58:48.866582 [TVE] action=set_cookies domains=1 cookies=23 2021/11/30 09:58:48.877495 [TVE] action=mock 2021/11/30 09:58:48.901851 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=Comcast_SSO&requestor_id=AMC&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication 2021/11/30 09:58:48.905093 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml 2021/11/30 09:58:49.239924 [TVE] action=request type=Document method=GET url=https://oauth.xfinity.com/oauth/authorize 2021/11/30 09:58:49.432969 [TVE] action=request type=Document method=GET url=https://login.xfinity.com/login 2021/11/30 09:58:49.433105 [TVE] action=auth_domain domain=login.xfinity.com 2021/11/30 09:58:49.858527 [TVE] action=request type=Document method=GET url=https://my.xfinity.com/upgrade 2021/11/30 09:58:49.865235 [TVE] action=request type=Document method=GET url=https://login.comcast.net/h/tve_unauthorized_nochannel.html 2021/11/30 09:58:49.865322 [TVE] action=authed 2021/11/30 09:58:49.871654 [TVE] action=request type=Document method=GET url=https://login.xfinity.com/h/tve_unauthorized_nochannel.html 2021/11/30 09:58:49.914176 [TVE] action=wait_for_page 2021/11/30 09:58:49.914282 [TVE] action=wait_for_page done=true reason=auth_finished 2021/11/30 09:58:49.927895 [TVE] action=error_response type=Document error=net::ERR_ABORTED url=https://login.xfinity.com/h/tve_unauthorized_nochannel.html
How can I help?
That looks like an auto authentication issue.
Has anyone with the same recent issues resolved this yet? 8 days, 3 diagnostics submitted and the only response I received was an email asking did I push the “button” to update chrome. I had already stated that it wasn’t working in the earlier email but perhaps I should have communicated that better
Usually the dev team is quick to respond or at least acknowledge the issue but just crickets this time. Is this being worked on, ignored or other? I’d appreciate some kind of response.
Huh? Fix was put up 8 months ago, have you tried it?
https://hub.docker.com/r/fancybits/channels-dvr/tags?page=1&ordering=last_updated
docker pull fancybits/channels-dvr:tve
Turns out that xfinity messed up and didn’t have streaming enabled on my account after calling in. They had to do an account refresh and that cleared it all up.
As per my previous responses to you, I already did and did a fresh install on Friday (post 531)
Ahh, OK. So now your web UI Status shows OS as
Linux Alpine
3.14.0_alpha20210212 (kernel: 4.14.24-qnap)
Apologies, I thought you were saying you didn't know how to pull the latest container image.
I would update to the latest pre-release and when you add the Xfinity-TVE source click and HOLD the Login button.
I have this same issue and am not running the dvr in a docker but I am running docker for Pluto. I have tried latest pre-release and holding login button. Still have the same issue. Any other ideas?
Other than deleting the chromedata folder, no other ideas.
I'm sure I'll have some when it happens to me (again).
What does your error screenshot look like?
http://x.x.x.x:8089/providers/tve/error_screenshot.png
This was my last issue, Ask me later
I have this same issue for many (most? maybe all that require login?) channels via TVE lately. I'm running the current version of Chromium available on Ubuntu, and tried with the latest Channels Stable and Pre-release. Channels presents the "no login form found" error, but the HTML and screenshot that Channels logs for the error do show a field for "Enter your Xfinity ID".
While I don't know if Auto Authentication ever worked for Chromium on Ubuntu, it doesn't right now. However, Auto Authentication works fine from my Windows Vivaldi browser. If anyone knows a channel that doesn't support Auto Authentication but does require a login, I'd be happy to check whether or not that channel works in Channels right now. I did try re-scanning a channel, and it presented the "no login form found" error as well, so a re-scan doesn't seem likely to help.
It seems like the only common link here is xfinity not docker, not chrome, not a particular server. I even tried on my windows laptop and it wouldn’t work here. I really think the issue is with the xfinity login screen but that’s just an educated guess. The latest update still hasn’t fixed it.
Can the devs please acknowledge that they are seeing this? I see them active on other conversations but not this one.
I'm wondering if it's Xfinity auth servers.
I logged into my Xfinity account (for other things, not streaming) earlier today and got a 500 error multiple times and had to try again later.
The login works everywhere but channels. Individual apps both atv and iOS, online sites, the xfinity stream app, etc.
To test I just added Xfinity-TVE, no problem.
DVR version 2021.11.23.2219
I already have 2 servers with it working, so added it to my docker container that had only a Pluto source.
Then enabled local networks and got them also.
Not sure what's different for those unable to add it.
I'm on my home Xfinity network using my own account and used a secondary VIEWER only user/pass.
