Looks like the Pi image chrome was pretty old too (product=HeadlessChrome/79.0.3945.130). I've updated it to v89 in case that helps. To update, follow these instructions:
What? On the pi?
Why can you not just use the update button for either the server or the other button that updates the os?
How do u know if that works?
I tried it and it just sits at verifying for a while , then no login form found.
EDIT: nvm, i see things in the log about it...derp.
EDIT2: Ok. did that update. rescan the one chan that i used for Xfinity that went auth failed...IT WORKED! Xfinity now working instantly after doing this funky way of updating chrome.
1 Like
Iām still having issues with food network and like channels for weeks now. Iāve updated the server, changed passwords, etc, for xfinity, but they either have a 401 error or no auth token, but Iām able to log in via their websites without issue.
Any ideas on what to try next?
Delete ~/Library/Application Support/ChannelsDVR/data/chromedata/ and try rescan again
Working now. Thanks!
Where is that file? I'm running on synology 218+.
/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedata
Please share the path for qnap running in a container.
/share/CACHEDEV1_DATA/.qpkg/ChannelsDVR/channels-dvr/data/chromedata
That fixed Food, Animal Planet, HGTV. But CNN, HLN still not working.
This thing is simply not working today on my MacBookās server. I wish this would get some more attention on a fundamental basis. It simply wonāt login to my Xfinity account after needing to change my password. I tried the update password feature and rescanned, but authentication failed. I tried removing the source and adding it again, but authentication failed. I updated to the latest prerelease, but authentication failed. I updated Chrome, but authentication failed. I deleted the chromedata folder, but authentication failed. I restarted the server numerous times, authentication failed. Signing into Xfinity directly with Chrome? Works just fine.
Everytime this happens to everyone, we basically canāt watch TV, and thereās no warning if we discover our shows just never recorded.
My password works, just not with your DVR. Why is this such an issue?
Yes, itās Xfinityās fault when it detects a security risk and needs me to change my password, but I donāt see why itās such a problem to login with the DVR once I set a new password.
Also, I donāt like the idea of having to install a prerelease every time I have this problems, that just invites more bugs that Iāve never had before. I used to use a Raspberry Pi as my server and it became basically junk after numerous prereleases, too many errors to count and no response from support.
I feel your pain, athough probably not as much as you do.
Remember that it's still Beta.
Appears the devs have to play catchup with all the TVE issues and providing a newer version of Chrome for those who don't use their own version (which probably auto-updates).
I use TVE, but don't solely rely on it since I have an HDHR Prime and a couple TiVo's.
The only TVE channel I very rarely have issues with is my local PBS station (other than when they don't stream a program or have tech difficulties with their stream).
hey guys, my parents are about to switch from FIOS to Xfinity. Anything special I need to do to get TV Everywhere working? Make a separate account, or turn anything on or off?
Best practice seems to be to set up a login only that only Channels uses. Turn off dual factor authentication -- Channels can't deal with that. I've been using it for over a year and it is pretty stable, but I would expect to have occasional authentication issues like the ones described in this thread. For me the issues have not been bothersome enough to cause me to switch providers or explore the whole cable card rabbit hole. Good luck!
The article below should cover it. Although I recommend updating to the latest pre-release of Channels DVR server first.
Ugh . . . I'm ready to give up on this. I had to reset everything again over the weekend, and then today two shows didn't record because the channels wouldn't authorize. I'm to the point where there is no benefit to scheduling any shows to record without first trying to log into the channel right before . . . which obviously defeats the purpose.
I recognize this is an Xfinity issue and not a Channels issue, but if the only thing I can record is from my antenna, I can use my Plex pass for that.
This was a new experience . . . in the middle of WATCHING a movie in FX, the screen went blank, then showed a "connection lost" message and then the "no authorization" when I tried to reconnect. So randomly during watching a show this is happening. Time to move on.
On Pre-release 2021.05.14.0010. I'm unable to get Xfinity logins to work. This is the error log below
2021/05/13 20:42:23.093864 [TVE] action=request type=Document method=POST url=https://login.xfinity.com/login
2021/05/13 20:42:23.300501 [TVE] action=error_response type=XHR error=net::ERR_ABORTED
2021/05/13 20:42:23.416025 [TVE] action=error_response type=Image error=net::ERR_CONNECTION_REFUSED
2021/05/13 20:42:23.418792 [TVE] action=error_response type=Image error=net::ERR_CONNECTION_REFUSED
2021/05/13 20:42:23.780213 [TVE] action=error_response type=Document error=net::ERR_CONNECTION_REFUSED
2021/05/13 20:42:23.786819 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED
2021/05/13 20:42:28.863724 [TVE] action=page_ready
2021/05/13 20:42:35.085152 [TVE] action=auth_timed_out
2021/05/13 20:42:35.085231 [TVE] action=screenshot
2021/05/13 20:42:35.359824 [TVE] action=screenshot size=291342
2021/05/13 20:42:35.360179 [TVE] action=capture_html
2021/05/13 20:42:35.369329 [TVE] action=capture_html size=18660
2021/05/13 20:42:35.464672 [TVE] Auth failed for Comcast_SSO: Cable provider authentication failed
And here is the diagnostic ID.
43db1f60-b89b-499c-b23e-9a1d4a6403d2
I have tried signing in by clicking & holding the sign up button with no dice. I can log into Xfinity's website no problem. Maybe I need to wait 48 hours or so, but I figured I'd see if there was something else here.
Edit: it did successfully sign in on version 2021.05.13.0008 from a different server that I have. Here are the diagnostics for comparison. d84becc8-b581-4acb-9945-4f51d26dac0f
Edit 2: Tried deleting chromedata folder. Same error is occurring.
Edit 3: It sat overnight & now logging in is working. š¤·
Try deleting and re-adding the Xfinity source.
I did do that. That's how I got to the click & hold sign in part. I should have mentioned it though.