Cox login error on DS412+

When trying to add source "TV Everywhere", and upon entering my login credentials for COX, I get the following authentication error: encountered exception 'Uncaught' 5:5.

I am using the most recent update/build (2019.08.06.2312), and am entering verified correct login credentials for my Cox account, Channels DVR installed on a Synology DS412+.

Log:

2019/08/06 17:01:17 [SYS] Downloading new version v2019.08.06.2312
2019/08/06 17:01:30 [SYS] Update downloaded and verified successfully.
2019/08/06 17:01:30 [SYS] Shutting down for upgrade from v2019.08.06.0711 to v2019.08.06.2312
2019/08/06 17:01:30 [SYS] Bonjour service stopped.
2019/08/06 17:01:30 [DVR] Recording engine stopped.
2019/08/06 17:01:32 [SYS] Starting Channels DVR v2019.08.06.2312 (linux-x86_64 pid:11901) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2019/08/06 17:01:32 [HDR] Found 1 devices
2019/08/06 17:01:34 [SYS] Started HTTP Server
2019/08/06 17:01:49 [DVR] Recording engine started in /volume1/Channels DVR
2019/08/06 17:01:49 [SYS] Bonjour service running for dvr-diskstation.local. [192.168.1.12 192.168.1.12]
2019/08/06 17:01:49 [SYS] Removing old update 2019.08.03.0055
2019/08/06 17:01:49 [NAT] Successfully mapped port 8089 using natpmp
2019/08/06 17:01:49 [SYS] Created database snapshot: backup-20190806.170149
2019/08/06 17:02:09 [IDX] Pruned 2627 expired airings from USA-CA04420-X in 8.720510964s.
2019/08/06 17:02:42 [TVE] Auth starting for Cox as [email protected]
2019/08/06 17:02:42 [TVE] action=auth mvpd=Cox requestor=nbcentertainment
2019/08/06 17:02:44 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=Cox&requestor_id=nbcentertainment&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2019/08/06 17:02:44 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2019/08/06 17:02:45 [TVE] action=request type=Document method=GET url=https://idm.east.cox.net/affwebservices/public/saml2sso
2019/08/06 17:02:45 [TVE] action=auth_domain domain=idm.east.cox.net
2019/08/06 17:02:45 [TVE] action=wait_for_page
2019/08/06 17:02:50 [TVE] action=page_ready
2019/08/06 17:02:50 [TVE] action=wait_for_page done=true reason=page_ready
2019/08/06 17:02:51 [TVE] action=fill_form u= [email protected]
2019/08/06 17:02:51 [TVE] action=screenshot
2019/08/06 17:02:52 [TVE] action=script_error err=&runtime.ExceptionDetails{ExceptionID:1, Text:"Uncaught", LineNumber:5, ColumnNumber:5, ScriptID:"11", URL:"", StackTrace:(*runtime.StackTrace)(0xc000a0e600), Exception:(*runtime.RemoteObject)(0xc0003727e0), ExecutionContextID:0} exp=&runtime.RemoteObject{Type:"string", Subtype:"", ClassName:"", Value:easyjson.RawMessage{0x22, 0x6e, 0x6f, 0x20, 0x6c, 0x6f, 0x67, 0x69, 0x6e, 0x20, 0x66, 0x6f, 0x72, 0x6d, 0x20, 0x66, 0x6f, 0x75, 0x6e, 0x64, 0x22}, UnserializableValue:"", Description:"", ObjectID:"", Preview:(*runtime.ObjectPreview)(nil), CustomPreview:(*runtime.CustomPreview)(nil)} exp_value="no login form found"
2019/08/06 17:02:52 [TVE] Auth failed for Cox: encountered exception 'Uncaught' (5:5)

Any suggestion(s) on how to get this working?

-Frustrated

Do you have a PC or Mac you can install the DVR on for testing, to see if the same thing happens there?

I can install on my Mac. Necessary to uninstall my NAS server?

No need to uninstall from NAS.

Installed on the Mac, and it is actually going through the process of verifying correctly! Once this finishes can I uninstall on the Mac and continue to use my Synology NAS as my DVR drive?

That means it's something about your NAS which is causing the TVE login not to work.

Can you copy/paste the OS/CPU section from the top of the DVR web UI on your NAS?

OS:
Synology DS412+
Linux
(kernel: 3.10.105)

CPU:
4 cores / Intel(R) Atom(TM) CPU D2700 @ 2.13GHz
load averages: 0.79 0.86 1.01

RAM:
988.61 MB
44.1% free

Does your version of DSM have Container Station?

Maybe it's just called Docker in the Package Center.

If so you can try to run the fancybits/channels-dvr:tve docker container instead and see if that works better.

Installed Docker: fancybits tve, but not sure how/where to access the status/overview page to add/view sources..

Make sure to disable the dvr package installed before.

In the docker config set networking mode to host, then access on port 8089 like you were before.

Got it running, but

Concerns: Running the dvr/tve service on my mac, it detects 178 channels. Running it via Docker/NAS It detects 101. I however subscribe to over 250 channels.

You can click the pencil icon under Cox and then the Edit button to compare.

Is there are specific channels you expect to get but show errors after rescan, email support with a screenshot of the error messages

There are at least 100 errors, mostly "server misbehaving", "encountered exception 'Uncaught' 5:5, as well as some chrome auth_timed_out.

Seems like the TVE feature cannot reliably on your older NAS then. You would have to use your Mac or another device for the DVR.

What are the minimum NAS processor requirements for TVE? And, is an authentication failure really related to the processor - seems like a stretch since it can transcode HD video without even a hiccup...

The issue is likely with the older version of the Linux kernel running on this device (which is 5+ years old). It might be fixable, but it's hard to do without access to a device for testing. If you're comfortable providing us with remote access via SSH then we may be able to look into the issue further.

For recommendations see NAS Recommendations

The Cox login bug on the DS412+ has been fixed in the latest DVR pre-release (v2019.09.10.0019).

Installed and can confirm that it is fixed and works - thank you!

1 Like

Happy New Year!

I went to watch TV today and got some strange url "adobe" errors on screen instead of programming. I went to check settings at http://dvr-diskstation.local:8089/admin/settings, and once again get the "encountered exception 'Uncaught' (5:5)" error that used to show up before the fix in (v2019.09.10.0019).

I can log into cox fine, my credentials/login has not changed....

-Dean