We would need more information to try to help. What is your server running on? It sound like it could have to do with an outdated chrome version.
And run Support > Troubleshooting after updating to the latest pre-release version.
Thanks for the quick reply - I am running version 2026.05.26.1844 on a Synology NAS. I believe that is the latest pre-release version.
Troubleshooting ran with no issues.
Logs have been submitted as 4fceaa41-9ca7-44f6-a583-714a63ebd4aa
This is what I did and using that user works on my Synology DS1019+ in a TVE docker container
Thanks for the suggestion. I tried it exactly and it still gives me the chrome error. This was working fine until last week. My account has been in there for years and last week and then it just stopped recording and when I rescanned for channels it it would not work. I deleted YTTV from the sources to try to add it again, like I have in the past and here we are. Is Chrome part of the channels server, could it need an updated version?
Yes, chromium is part of the TVE container.
What version of chrome does troubleshooting show you have?
My Channels DVR Xfinity-TVE container shows
[TRS] TV Everywhere: OK: Chrome version up to date: 132.0.6834.83
My custom built YTTV-TVE container shows
[TRS] TV Everywhere: OK: Chrome version up to date: 148.0.7778.215
It shows, "Chrome version up to date: 114.0.5735.199"
That looks old. How can I update it?
By doing the above step the Synology Nas should update to version 129.0.6668.59 if you are running the native server for synology. It can't be upgraded to a newer version than 129 with the native Channels DVR Server. I believe Chrome version 130 and newer requires a newer linux kernel which Synology doesn't provide. If they ever did upgrade to a more modern kernel then Channels DVR could upgrade the Chrome version to a newer version.
I tried the instructions with Dish, which I do not have and holding the Sign In button, but I still receive the same browser error. When I tried it with Xfinity, which I also do not have it just said credentials failed.
I cannot even navigate to http://myipaddress:8089/providers/tve/chrome I just get a 404 error.
Did you check in Troubleshooting to see if Chrome upgraded to 129?
You don't bring up that url in a browser.
You use the curl commandline utility with it.
curl -XPOST http://myipaddress:8089/providers/tve/chrome
Using a container allows newer chrome versions.
https://getchannels.com/docs/channels-dvr-server/tv-everywhere/provider-help/#youtube-tv
Yes but not native install 
Correct. That's why they mention running in a container for Xfinity and YTTV
-
Xfinity authentication can frequently fail while running on a NAS system. Our suggestion is to run Channels DVR Server via Docker on these systems, or run your Channels DVR Server directly on a computer with Linux, macOS, or Windows.
-
YouTube TV authentication can frequently fail while running on a NAS system. Our suggestion is to run Channels DVR Server via Docker on these systems, or run your Channels DVR Server directly on a computer with Linux, macOS, or Windows.
I have one server using a container for Xfinity-TVE (Chrome v132) and another server using a container for YTTV-TVE (Chrome v148).
It did update to 129, thanks. It still does not work though. I will update it to a container. Thanks for all the assistance everyone!
Let us know how it turns out. Pretty sure using a container will work for you.
If it's any help to anyone, and I'm not saying don't use the FancyBits container, but the container I built reruns a CI monthly with the latest Chrome baked in, if that is helpful to anyone.
Even though it is built with Unraid in mind. It'll work anywhere, not just Unraid. And just don't expect official support from FancyBits because it's not an official container. That's just my disclaimer. It is not expected that they will support it, of course.
I am running it in a container now and have chrome version 132.0.6834.83, but now when i try to add YTTV I get this message: authn: POST: https://sp.auth.adobe.com/adobe-services/session: 401 Unauthorized: "Data not found"
By chance, are you using a Pi-hole or DNS ad blocker?