No Login Form Found

[jeffs]

Hi. Recently, a bunch of channels are failing in the guide (and recording) with a "no login form found" error. Re-signing in with TV Everywhere (via FIOS) doesn't seem to make a difference. Also, if I go directly to the website for HGTV, one of the failing channels, I can easily sign in with the same credentials, but signing in through Channels and doing a rescan always fails with that login form error.

Did these stations change their login forms in a way that Channels can't process behind the scenes?

Thanks!

[number1mom]

Experiencing the exact same issue with the "Discovery" network channels! I have DISH login.

[jerryoa]

I'm seeing the same issue for ABC.

Here are some log entries:

2023/02/26 19:00:43.265357 [TVE] action=auth mvpd=DTV requestor=ABC
2023/02/26 19:00:43.562884 [TVE] action=version product=HeadlessChrome/110.0.5481.105 jsVersion=11.0.226.16 protocol=1.3 revision=@46de4a7f41979e829b430bc1ee30ef483aa227ac
2023/02/26 19:00:43.564159 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=DTV&requestor_id=ABC&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2023/02/26 19:00:43.564664 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2023/02/26 19:00:46.200185 [TVE] action=wait_for_page
2023/02/26 19:00:46.221977 [TVE] action=request type=Document method=POST url=https://idp.dtvce.com/dtv-idp-authn/authn/v2
2023/02/26 19:00:46.221977 [TVE] action=auth_domain domain=idp.dtvce.com
2023/02/26 19:00:55.505262 [TVE] action=page_ready
2023/02/26 19:00:55.505262 [TVE] action=wait_for_page done=true reason=page_ready
2023/02/26 19:00:55.505262 [TVE] action=fill_form u=<redacted>
2023/02/26 19:00:55.505781 [TVE] action=screenshot
2023/02/26 19:00:55.539401 [TVE] action=screenshot size=8177
2023/02/26 19:00:55.540127 [TVE] action=capture_html
2023/02/26 19:00:55.541971 [TVE] action=capture_html size=263
2023/02/26 19:00:55.542510 [TVE] action=script_error err=&runtime.ExceptionDetails{ExceptionID:1, Text:"Uncaught", LineNumber:9, ColumnNumber:5, ScriptID:"5", URL:"", StackTrace:(*runtime.StackTrace)(0xc0006f4540), Exception:(*runtime.RemoteObject)(0xc000bf0f30), ExecutionContextID:0, ExceptionMetaData:easyjson.RawMessage(nil)} 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:"", WebDriverValue:(*runtime.WebDriverValue)(nil), ObjectID:"", Preview:(*runtime.ObjectPreview)(nil), CustomPreview:(*runtime.CustomPreview)(nil)} exp_value="no login form found"
2023/02/26 19:00:55.678224 [ERR] Could not start stream for TVE-DTV ch6001 KTNV: TVE: "no login form found"

[Pooh-Bear]

Unfortunately in the same boat with DISH - looks like TVE auth is currently affected with DISH being cyberattacked right now (DISH's identity provider domain, identity1.dishnetwork.com, has been down for multiple days alongside most of DISH's other web services). We'll just have to wait it out!

For everyone else, double check your DNS settings on the Channels DVR server to ensure that the auth domain can be reached by it (eg. idp.dtvce.com)

[jeffs]

Does anyone have any suggestions? A large number of my TVE channels are no longer functional. This is not a Dish network issue. This is FIOS.

I guess I'm not used to seeing it so quiet in here.

[tmm1]

See TVE Troubleshooting tips

Specifically:

@chDVRuser

• Update to the latest DVR prerelease version see this article for how

and

@chDVRuser

submit DVR diagnostics from the DVR web UI Support>Troubleshooting

[jeffs]

Updating to the latest prerelease software, removing TV Everywhere and re-adding it fixed this issue.

[jerryoa]

Updating to the latest pre-release version worked for me as well.

[gtpeterman]

Was experiencing this issue. Updated to beta server version, removed and readded now I see this:

Logs here:
ac3f9d62-feb3-452a-aaf5-0ec0f689143e

[tmm1]

On the Support > Troubleshooting page click the button to update chrome

[gtpeterman]

doesn't work. Get "https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/97.0.4692.56": dial tcp: lookup registry-1.docker.io on 192.168.0.1:53: no such host

Downloaded 1.05 pkg for synology and updated manually. Now troubleshooting shows chrome up to date, but now I get this:

[tmm1]

Problem with your dns settings

[gtpeterman]

Any links or anything on how to resolve?

Troubleshooting page shows green checks on all items. Including DNS, TVE and TVE DNS.