There was a problem communicating with the Schedules Direct Server

[Dave Beddows]

So it looks like my guide stopped getting updates 12 days ago.

I've tried all the usual things:
restarting the computer
toggling a channel to force an epg
removing the sdmd5 files
Checked my SD account was up to date
Checked the test url at SD to make sure I'm not blocked

When I tried to delete my lineup and add it again I get the message "There was a problem communicating with the Schedules Direct Server"

I'm running:
V9.0.8.429
Java 1.8.0_241
Windows 7 6.1

I tried to turn on JSON logging. I had to add debug_sd=true to the properties file but it did not generate a sd_epg log

Anyone got any ideas?


Below is the error log from sagetx_0:

Sat 2/1 22:48:03.502 [FSManager@574acb] FSManager is running...
Sat 2/1 22:48:03.507 [EPG@19ddb6b] Increased ArrayList pool to size=1
Sat 2/1 22:48:03.508 [Scheduler@4e362b] initGraph0 (ver 2.1.0) called capDev='Hauppauge WinTV-7164 Analog Capture-0', Country:'Canada', TuningMode:Air, TunerType: Cap:0x8810
Sat 2/1 22:48:03.509 [EPG@19ddb6b] sage.epg.sd.SDRipper@673a93 needs an update in 0:00:00
Sat 2/1 22:48:03.509 [EPG@19ddb6b] sage.epg.sd.SDRipper@162f337 needs an update in 0:00:00
Sat 2/1 22:48:03.510 [EPG@19ddb6b] EPG needs an update in 0 minutes
Sat 2/1 22:48:03.511 [EPG@19ddb6b] EPG attempting to expand Local Over the Air Broadcast - V4P1C4 (sdepg)
Sat 2/1 22:48:03.512 [EPG@19ddb6b] expand called on Local Over the Air Broadcast - V4P1C4 (sdepg) at Sat 2/1 22:48:03.512 expandedUntil=Sat 2/1 22:42:44.679 scannedUntil=Sat 8/16 23:12:55.807
Sat 2/1 22:48:03.513 [EPG@19ddb6b] EPG Expanding Local Over the Air Broadcast - V4P1C4 (sdepg) at Sat 2/1 22:48:03.513
Sat 2/1 22:48:03.515 [Carny@1221f59] Carny got a Std job of null
Sat 2/1 22:48:03.517 [SageTV@5f9677] Splash: Waiting for SageTV to finish initialization...
Sat 2/1 22:48:03.524 [MsgMgrSocket@b00f62] Spawned thread for MsgManger server socket listening...
Sat 2/1 22:48:03.527 [Scheduler@4e362b] BAD Tuner index :1 dev:\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800} name:@devicenp:\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800} locci:4-0 (1 0) select
Sat 2/1 22:48:03.527 [Scheduler@4e362b] Check BDA capture device:Hauppauge WinTV-7164 Analog Capture-0 (\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800}) on location:'pci:4-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88910070&REV_81' [state1, index:0] .
Sat 2/1 22:48:03.530 [Scheduler@4e362b] >>BDA capture device found:@devicenp:\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400}; loc:'pci:4-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88910070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa400 desc:@oem3.inf,%halesite.devicedesc8891%;Hauppauge WinTV-HVR-2250 (8891)
Sat 2/1 22:48:03.530 [Scheduler@4e362b] BDA Capture found: (0) @devicenp:\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400} on loc pci:4-0.
Sat 2/1 22:48:03.530 [Scheduler@4e362b] >>BDA capture device found:@devicenp:\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401}; loc:'pci:4-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88910070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa401 desc:@oem3.inf,%halesite.devicedesc8891%;Hauppauge WinTV-HVR-2250 (8891)
Sat 2/1 22:48:03.530 [Scheduler@4e362b] BDA Capture found: (1) @devicenp:\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401} on loc pci:4-0.
Sat 2/1 22:48:03.530 [Scheduler@4e362b] Mutil-tuner(2) BDA capture is found on location:'pci:4-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88910070&REV_81' for Hauppauge WinTV-7164 Analog Capture-0. (@devicenp:\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400},0,desc:@oem3.inf,%halesite.devicedesc8891%;Hauppauge WinTV-HVR-2250 (8891)).
Sat 2/1 22:48:03.530 [Scheduler@4e362b] Add BDA filters (capture:'@devicenp:\\?\pci#ven_1131&dev_7164&subsys_88910070&rev_81#4&45b69f9&0&00e2#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400}') for device=Hauppauge WinTV-7164 Analog Capture
Sat 2/1 22:48:03.530 [Scheduler@4e362b] Not specify TV type ( Network type ), to search matching one.
Sat 2/1 22:48:03.533 [Carny@1221f59] CARNY Processing 14981 Agents & 9392 Airs
Sat 2/1 22:48:03.542 [Scheduler@4e362b] Loaded Sage TV Splitter Filter 0x491e54
Sat 2/1 22:48:03.542 [Scheduler@4e362b] BDA Filters are loaded
Sat 2/1 22:48:03.543 [MainMsg@ed0661] switchToConnector0 tuningMode:Air.
Sat 2/1 22:48:03.544 [Scheduler@4e362b] initGraph0 (ver 2.1.0) called capDev='Hauppauge Colossus Capture 0-0', Country:'Canada', TuningMode:, TunerType: Cap:0x100800
Sat 2/1 22:48:03.544 [Scheduler@4e362b] Add analog filters for device=Hauppauge Colossus Capture 0
Sat 2/1 22:48:03.551 [Scheduler@4e362b] Found the pin2
Sat 2/1 22:48:03.926 [AsyncPropSaver@df81c2] Saving properties file to C:\Program Files\SageTV\SageTV\Sage.properties
Sat 2/1 22:48:03.927 [Seeker@53bf8f] Checking video directories for new files
Sat 2/1 22:48:03.929 [LibraryImporter@146385] Increased Thread pool to size=6
Sat 2/1 22:48:03.932 [Seeker@53bf8f] Diskspace checking is running
Sat 2/1 22:48:03.932 [Seeker@53bf8f] Verifying existence of all TV media files in database fixDurs=false avoidArchive=true
Sat 2/1 22:48:03.933 [LibraryImporter@146385] Checking video directories for new files
Sat 2/1 22:48:03.941 [Seeker@53bf8f] Seeker waiting for 153722840937144 mins.
Sat 2/1 22:48:03.943 [AsyncPropSaver@df81c2] Done writing out the data to the properties file
Sat 2/1 22:48:04.266 [EPG@19ddb6b] SDEPG Exception thrown: java.security.cert.CertificateException: No subject alternative DNS name matching json.schedulesdirect.org found.
Sat 2/1 22:48:04.267 [EPG@19ddb6b] javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching json.schedulesdirect.org found.
Sat 2/1 22:48:04.268 [EPG@19ddb6b] at sun.security.ssl.Alerts.getSSLException(Unknown Source)
Sat 2/1 22:48:04.268 [EPG@19ddb6b] at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
Sat 2/1 22:48:04.268 [EPG@19ddb6b] at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
Sat 2/1 22:48:04.268 [EPG@19ddb6b] at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
Sat 2/1 22:48:04.268 [EPG@19ddb6b] at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.security.ssl.Handshaker.processLoop(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.security.ssl.Handshaker.process_record(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.net.http://www.protocol.https.HttpsClien...onnect(Unknown Source)
Sat 2/1 22:48:04.269 [EPG@19ddb6b] at sun.net.http://www.protocol.https.AbstractDe...onnect(Unknown Source)
Sat 2/1 22:48:04.270 [EPG@19ddb6b] at sun.net.http://www.protocol.http.HttpURLConn...tream0(Unknown Source)
Sat 2/1 22:48:04.270 [EPG@19ddb6b] at sun.net.http://www.protocol.http.HttpURLConn...Stream(Unknown Source)
Sat 2/1 22:48:04.270 [EPG@19ddb6b] at sun.net.http://www.protocol.https.HttpsURLCo...Stream(Unknown Source)
Sat 2/1 22:48:04.270 [EPG@19ddb6b] at sage.epg.sd.SDSageSession.post(SDSageSession.java:134)
Sat 2/1 22:48:04.270 [EPG@19ddb6b] at sage.epg.sd.SDSageSession.post(SDSageSession.java:106)
Sat 2/1 22:48:04.270 [EPG@19ddb6b] at sage.epg.sd.SDSession.post(SDSession.java:451)
Sat 2/1 22:48:04.270 [EPG@19ddb6b] at sage.epg.sd.SDSession.authenticate(SDSession.java:334)
Sat 2/1 22:48:04.270 [EPG@19ddb6b] at sage.epg.sd.SDSageSession.<init>(SDSageSession.java:47)
Sat 2/1 22:48:04.271 [EPG@19ddb6b] at sage.epg.sd.SDRipper.openNewSession(SDRipper.java:221)
Sat 2/1 22:48:04.271 [EPG@19ddb6b] at sage.epg.sd.SDRipper.ensureSession(SDRipper.java:160)
Sat 2/1 22:48:04.271 [EPG@19ddb6b] at sage.epg.sd.SDRipper.extractGuide(SDRipper.java:1007)
Sat 2/1 22:48:04.271 [EPG@19ddb6b] at sage.EPGDataSource.expand(EPGDataSource.java:709)
Sat 2/1 22:48:04.271 [EPG@19ddb6b] at sage.EPG.run(EPG.java:776)
Sat 2/1 22:48:04.271 [EPG@19ddb6b] at java.lang.Thread.run(Unknown Source)
Sat 2/1 22:48:04.271 [EPG@19ddb6b] Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching json.schedulesdirect.org found.
Sat 2/1 22:48:04.272 [EPG@19ddb6b] at sun.security.util.HostnameChecker.matchDNS(Unknown Source)
Sat 2/1 22:48:04.272 [EPG@19ddb6b] at sun.security.util.HostnameChecker.match(Unknown Source)
Sat 2/1 22:48:04.272 [EPG@19ddb6b] at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source)
Sat 2/1 22:48:04.272 [EPG@19ddb6b] at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source)
Sat 2/1 22:48:04.272 [EPG@19ddb6b] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source)
Sat 2/1 22:48:04.272 [EPG@19ddb6b] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
Sat 2/1 22:48:04.272 [EPG@19ddb6b] ... 24 more
Sat 2/1 22:48:04.272 [EPG@19ddb6b] ERROR Updating EPG Source Local Over the Air Broadcast - V4P1C4 (sdepg)
Sat 2/1 22:48:04.273 [EPG@19ddb6b] ErrorText:expand called on Local Over the Air Broadcast - V4P1C4 (sdepg) at Sat 2/1 22:48:03.512 expandedUntil=Sat 2/1 22:42:44.679 scannedUntil=Sat 8/16 23:12:55.807
EPG Expanding Local Over the Air Broadcast - V4P1C4 (sdepg) at Sat 2/1 22:48:03.513

[SHS]

See if NextPVR dose the same thing if yes the you get hold of Schedules Direct

[Dave Beddows]

Nextpver gives me "Unabled to communicate with Schedules Direct. Please try again later."

Now it is possible my test with nextpvr may not be valid because I have never used it before and set it up today. I went to channel details and chose schedules direct as the epg source. I get the connection error when I go to choose the line up. I don't get as far as to be prompted for a username & password for schedules direct.

I have tried this with the windows firewall turned off.

I have submitted a report to schedules direct. Hope I can resolve this before my guide runs out.

I also tried a earlier know working version of wiz.bin

[tvmaster2]

I’m currently showing the next 16 days of listing info for U.S cable, OTA & CDN satellite. Normal as always.

[SHS]

Originally Posted by Dave Beddows

Nextpver gives me "Unabled to communicate with Schedules Direct. Please try again later."

Now it is possible my test with nextpvr may not be valid because I have never used it before and set it up today. I went to channel details and chose schedules direct as the epg source. I get the connection error when I go to choose the line up. I don't get as far as to be prompted for a username & password for schedules direct.

I have tried this with the windows firewall turned off.

I have submitted a report to schedules direct. Hope I can resolve this before my guide runs out.

I also tried a earlier know working version of wiz.bin

May guest it something else is going on
Zip up NextPVR log there in C:\Users\Public\NPVR\Logs

[Dave Beddows]

Here is the NPVR log

[SHS]

Originally Posted by Dave Beddows

Here is the NPVR log

Your get this
Unexpected error doing Schedules Direct login: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

I not sure what above mean ask sub on NextPVR forum post the logs it may help pin point and solve your problem with SageTV too

[peternm22]

By the looks of it, it can't verify the SSL/TLS certificate when connecting to Schedules Direct.

Can you see if you can open this website in your browser? https://json.schedulesdirect.org/

Try it in Chrome/IE/Edge as those all use the same certificate store I believe. If you have Firefox installed, try that too as I think it uses a different certificate store than the other browsers.

It will be just a blank page even if it works, but I'm curious if you get any SSL/TLS errors when trying to go to the website on any browser.

If you do get an SSL/TLS error, then there is a problem with your internet connection (could be a firewall or antivirus, your router could be filtering something, a few possible reasons).

[Dave Beddows]

From Google Chrome:

A warning page comes up with a recommendation to no go to an unsecure page.

This server could not prove that it is json.schedulesdirect.org; its security certificate is from *.dispatchit.com. This may be caused by a misconfiguration or an attacker intercepting your connection.

If I choose to go anyway I get a page "Dispatch" page requesting me to log in.

-----------------------------------------------------------------------------------------------

Internet Explorer returns

The security certificate presented by this website was issued for a different website's address.
Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.
We recommend that you close this webpage and do not continue to this website.
Not recommended Continue to this website (not recommended).
If you arrived at this page by clicking a link, check the website address in the address bar to be sure that it is the address you were expecting.
When going to a website with an address such as https://example.com, try adding the 'www' to the address, https://www.example.com.

If I continue webpage cannot be found
------------------------------------------------------------------------------------------------

I don't have firefox or Edge installed.
I also tried it from my laptop with the exact same results.
I also made sure there were no entries in my windows hosts file.

I assume by the fact Chrome can get to a login page it is not being blocked by a firewall. Not sure why Explorer doesn't like it

[Dave Beddows]

By the way the "Dispatch" site Chrome took me to has a "Not Secure" url of https://json.schedulesdirect.org/users/sign_in


Looked up the original email I was sent in Oct 2016 when I signed up for schedules direct.

The link they gave no longer works but that may be just because they changed their setup. I just thought I might try to log into that "Dispatch" site with the username and activation code they sent in 2016. I'll wait though just in case it is not a good idea.


This is the instruction to register for the 1st time that was sent in 2016
Welcome to Schedules Direct.
Our account activation process requires one final step. Point your
browser to https://www.schedulesdirect.org/login and log in with your
new username:

[Dave Beddows]

I just had this reply from schedules direct a few minutes ago.

We're not blicking on our end, and it looks like your last access was today around 1P, so you're communicating with the service. I'm not sure what else may be happening, but it's not TCP/IP level or routing.

I'm sure he meant blocking not blicking

If they are EST then that may have been when I was trying NextPVR. I ran that around 10:20 PST. Not sure if it counts but I logged into my schedules direct account about 1pm EST to add NextPVR to my account profile.

[Dave Beddows]

Please standby I may have found the issue.

I thought I would log into my Asus router to check the logs and found it's gui was frozen. Should have done a power cycle on it last night before all this. Didn't think it was as I have multiple devices accessing the internet through it.
Now I can get to Schedules Direct from Sage source set up. I no longer get the, "There was a problem communicating with the Schedules Direct Server" message.
So I deleted and added an EPG to one of my sources and that seemed like it worked. At least it accepted my username and password so I am getting there from here.

So far the guide hasn't updated and the 2 sdmd5 files that I moved back to the Sage directory have not changed.
If it hasn't updated after Dr Who has finishes recording in 1/2 hour, I'll shut down and restart Sage.

[peternm22]

Something screwy is going on.

While you are on the https://json.schedulesdirect.org/ site, do this in Chrome:

Press Ctrl + Shift + I to bring up Developer Tools. Click the Security tab. Click "View Certificate".

Can you screenshot the info on the 3 tabs and upload it here? I've attached an example of the screenshots I'm looking for.

[SHS]

You may need clear or clean out both IE and Chrome temp that will apply to new MS Edge (Chromium) or any other you install
Right-click Command Prompt and choose Run as administrator and do ipconfig /flushdns and netsh int ip reset Once done, restart your computer.

[peternm22]

It sounds like something was screwing up your DNS queries, and routing you to the wrong place you when tried to connect to Schedules Direct.

It could be a weird random hiccup, but it's also possible that some malware may have gotten into your router. It's better to be safe than sorry.

A lot of router malware lives only in RAM, so when you reboot it, it essentially removes the malware. However, if you don't fix the security hole, you will likely get re-infected.

Is your router firmware up to date? Is Asus still providing recent firmware patches? Try Googling your router model number and look for any security problems that have been patched.

[SHS]

Originally Posted by peternm22

It sounds like something was screwing up your DNS queries, and routing you to the wrong place you when tried to connect to Schedules Direct.

It could be a weird random hiccup, but it's also possible that some malware may have gotten into your router. It's better to be safe than sorry.

A lot of router malware lives only in RAM, so when you reboot it, it essentially removes the malware. However, if you don't fix the security hole, you will likely get re-infected.

Is your router firmware up to date? Is Asus still providing recent firmware patches? Try Googling your router model number and look for any security problems that have been patched.

I'm beating it dns cache hiccup problem I add the command to address just in case.
I highly doubt it a malware because all his or her other device on would act off the wall as well

[peternm22]

Originally Posted by SHS

I'm beating it dns cache hiccup problem I add the command to address just in case.
I highly doubt it a malware because all his or her other device on would act off the wall as well

I agree it's likely just a weird hiccup, but it doesn't hurt to make sure your router firmware is up to date just in case.

[SHS]

Originally Posted by peternm22

I agree it's likely just a weird hiccup, but it doesn't hurt to make sure your router firmware is up to date just in case.

True

[Dave Beddows]

I just checked and the firmware it is not the most current. I will update it tonight. It is an older router so the latest one is still a few years old.

The guide is back in it's entirety. The 2 sdmd5 files are now showing today's date.
Think I'll backup the wiz.bin & properties files tonight. Wasn't happy when I noticed my backups were 1 year old. How time flies.

Did notice that when I tried to force an EPG update it only did the channels associated to the source lineup that I did a channel toggle on. I had to do one on my colossus lineup to get the EPG for it to come down.

Anyway I am happy, I just have to wait for Sage to notice the guide is there and actually schedule my recordings.

Thank you everyone for all your help. Especially on Superbowl Sunday. Can't believe it turned out to be a router issue with everything else in the house working so well.