Some Warner Bros/Discovery TVE channels not working

Channels DVR Server TV Everywhere
#1

I had a recording fail on TNT but didn't have time to look into it last night when it happened. Just now, however, I had another recording fail on Food Network. I tried rescanning the channel but received the following error:

adobe auth reg code: json: cannot unmarshal JSON string into Go network.CookiePartitionKey within "/cookies/10/partitionKey"

Getting the same or similar message when I try to rescan some of the WBD TV Everywhere stations. The error for TNT is:

json: cannot unmarshal JSON string into Go network.CookiePartitionKey within "/cookies/10/partitionKey"

So far the stations I'm experiencing this issue with are:

TNT/TNTP
TRU/TRUP
TCM/TCMP
DISCOVERY
FOOD

I'm not seeing this issue with:

CNN
HLN
CNNI
TBS/TBSP

There may be other channels affected but those were the ones I was able to test at the moment. I'm using TV Everywhere through Xfinity.

1 Like
#2

Working fine for me.
Have you updated your server to the latest pre-release version?

#3

I noticed this issue earlier this week, seems to affect more than just WBD channels when I did a full rescan (Comcast user on the latest beta). I submitted logs to the support email to see if they have any ideas, but if anyone here has advice, I'd appreciate it.

#4

I no longer rescan TVE channels when they fail.
I play them from the guide in the DVR web UI player.
This will re-authenticate the channel if needed.

Working for me.

If you rescan channels and they fail, they're removed from your lineup and guide, so your only recourse is to rescan them. I prefer not to do that.

#5

I am on 2026.02.21.0601 using a Synology DS218+.

1 Like
#6

So maybe it's a Comcast issue with TV Everywhere. Now that you mentioned it, I scanned a few other channels like Lifetime and Sundance and they're giving similar errors.

1 Like
#7

Comcast Xfinity TVE is working fine for me.
What little I use it for.
Synology if I recall uses a special container or something for tve use.
Or maybe u need to update Chrome.

#8

playback in any chrome based browser has been broken for me for quite some time there’s already a thread on that. If I recall anything other than OTA gives a weird error. Everything works fine in Firefox, however

#9

According to troubleshooting steps, Chrome is up to date. A few Comcast channels still work, and it appears all channels with Philo as a source are working as well.

#10

Same. When I run the Troubleshooting I'm getting all green checks and it notes that Chrome is up-to-date (Chrome version up to date: 114.0.5735.199)

#11

If you're running the DVR Server on a NAS, read the note here. I run mine in a container on my Synology.
https://getchannels.com/docs/channels-dvr-server/tv-everywhere/provider-help/#xfinity

  • 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.
1 Like
#12

Agree. I use Firefox as my daily driver.
You can also keep trying to play a channel from a client device, but I prefer doing it from the web UI so I can look at the log (opened in another browser tab) while I attempt to play a channel that's failed. That's how I know it re-authenticates if needed.

#13

Latest version of chrome is 129.0.6668.59.

In order for it to update to this version you have to add another source like directTv and use user test and pass test. Its the act of adding a new source that will update it from 114 to 129.

1 Like
#14

I think the key to getting a chrome update is to Click and Hold the Sign In button.

1 Like
#15

I tried that but when I check the version number through Troubleshooting again, it's still at 114.

EDIT: I responded before seeing @chDVRuser's post about having to hold the sign in button while doing the test/test user/pass login with DirecTV. I'm now seeing " Chrome version up to date: 129.0.6668.59"

Scanning the previously affected channels brings them back. How can I ensure in the future that Chrome is up-to-date if the Troubleshooter isn't accurate?

#16

Did you ever get a reply to the support email? I had also sent in logs and the reply I got back was that they were cancelling my subscription and giving me a ref*nd. I assume that was some kind of error as I never requested that and my subscription still shows as active but that was the only reply I've had so far.

#17

Did you Click and Hold the Sign In button?

#18

Sorry, just updated my previous reply to note I'd missed your earlier suggestion. That did update Chrome and allow me to rescan the channels.

#19

Thanks, for a second there I thought I made that post using my invisible ink font :laughing:

#20

I believe that is the newest version possible due to the kernel version that Synology uses. So unless they upgrade to a more modern version (don't hold your breath). You now have probably the latest version there ever will be. Version 129 is a fairly old version.

Thanks @chDVRuser I forgot about the long hold part of it.