Schedules Direct Login Failed

[mvallevand]

@davidsde01 could you try again? I heard back from SD and they changed something and the credentials you PM'd work now with curl.

Martin

[davidsde01]

Hi Martin,

That did the trick!  Thanks for reaching out to your contact at SD.  I really appreciate your help!

Dan

[terrief]

I've been seeing a similar issue the last couple days.  I can login to Schedules Direct and my custom lineup is there but NextPVR will not load the schedules.  My custom lineup shows up on the Guide page so the login is correct but when click Update EPG nothing happens.

I tried Mvallevand's suggesting of clearing the schedules direct user and password in config.xml but that didn't help.  I also ran the curl commandline after turning off my VPN and get this:
curl --data baddata https://json.schedulesdirect.org/20141201/token
{"response":"INVALID_JSON","code":1101,"serverID":"20141201.web","message":"Unable to decode JSON. I74","datetime":"2022-10-08T17:26:29Z"}

I installed NextPVR on another machine and am getting the exact same results as my main PVR.

I also installed FreeGuide which uses Schedules Direct and that's working fine.

Attached are the logs from my new install

Terrief

[mvallevand]

Your problem is only related to this thread because it mentions Schedules DIrect. Yoou need to go to Settings->Channels->Advanced to automap to your configured SD OTA lineup.

Martin

[sub]

Yep, what he said. You haven't yet told NextPVR to use Schedules Direct for these channels. Using 'automap' will sort that out for you.

[terrief]

Thanks mallevand & sub, I must have missed that step in the setup guide on github. Everything is working now.

[cogengr]

Sorry to resurrect a weeks-old thread; I'm having similar issues.  Have been using SD for years, but the EPG stopped working recently. 

Curl returns:

C:\Users\PVR>curl --data baddata https://json.schedulesdirect.org/20141201/token
curl: (60) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL (0x80090322) - The target principal name is incorrect.
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Logs attached.

Thanks for whatever insight you can share - I'm at a loss...

[mvallevand]

@cogengr I would contact SD and get them to verify your account.

Martin

[cogengr]

Good advice - will report back!

EDIT:

To close the loop - the culprit was stale DNS entries sitting in Verizon FIOS servers (I'm located in the DC metro area) - I switched to getting DNS from 8.8.8.8 and 8.8.4.4 and it fixed the issue immediately. Not sure why those entries aren't propagating through DNS servers properly.

Excellent and FAST support from the Schedules Direct folks - shout out to Robert for his great sleuthing.