Setting "EPG Source" to "Schedules Direct" causes an "Unhandled exception".

[mvallevand]

From a browser can you connect to https://json.schedulesdirect.org/2014053.../mfdb-json Have you enabled TLS only I know they disabled SSL (a good thing)

Martin

[sub]

But the interesting part is the log file, which is much more verbose with this error. It is now complaining about a lack of trust. The log is attached.

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

Very odd. To be honest, I've got no idea what to suggest on this one. It sounds like it's not connecting directly to Schedules Direct, but instead via some other non-trusted intermediary.

[MarkHotchkiss]

Very odd - I posted a reply about two hours ago. It was there about 15 minutes later, and now it's gone. I will try again:


Hi Sub,

Yeah, I couldn't make out what the log was really saying. Tonight, when I can again bypass the proxy-server, I will try again with Wireshark. I have an easier time when I can actually see the packets.


Hi Martin,

Thanks for that - It may get me somewhere. When I click on the link that you provided, I get this:

Code:

{"response":"OK","code":0,"client":"mfdb-json","version":"0.22","serverID":"20140530.1","datetime":"2014-11-04T20:02:01Z"}

It's encouraging that it at least says "OK", even though that was through the proxy-server.

I'm pretty familiar with Secure Socket Layers, but not TLS (as you can see, I haven't even googled what it stands for yet). So that gives me another avenue to explore. Did the old Schedules Direct use SSL and not TLS?

[sub]

The old schedules direct just used http (port 80), not https.

[mvallevand]

I did some searching and I am not still sure .NET 4.0 on XP supports TLS 1.0 but json.schedules.direct.org doesn't support SSL.

Martin

[Braklet]

I did some searching and I am not still sure .NET 4.0 on XP supports TLS 1.0 but json.schedules.direct.org doesn't support SSL.

This problem may well be due to security measures taken against the POODLE vulnerability (https://www.us-cert.gov/ncas/alerts/TA14-290A).

The most common patch is to disable ALL SSLv2/SSLv3 access to prevent the vulnerable fallback, and opt for TLSv1 or better. Some folks recommend even disabling TLSv1.

Anyway, I'm not a Windows developer and can't even hazard a guess about what the .NET clients expect, but Martin's observation is right in line with breaking industry actions. The HTTPS client can't expect to succeed using SSL.

I'm still paying close attention to this thread since I too am running NPVR on an XP host, so these problems aren't just a single person's. I am just sticking with 3.1.1 for now.

B

[mvallevand]

ACTCMS kindly did some testing using some sample code I wrote and TLS 1.0 does work with SchedulesDirect if XP is set up correctly.

Martin

[sub]

I've also been able to confirm it's not a general XP + NextPVR 3.3.8 problem. I've run up an XP VM, installed 3.3.8 (+patch), and been able download listings from Schedules Direct.

[mvallevand]

Here is a test app to see if you can connect to SD using TLS

Martin

[MarkHotchkiss]

Thanks Martin, Sub and Braklet.

Martin, I tried you program, and now I'm really on to something.

First from my laptop and I got this result:

Code:

Trying SSL
The underlying connection was closed: An unexpected error occurred on a send.

Trying TLS
{"response":"OK","code":0,"client":"mfdb-json","version":"0.22","serverID":"20140530.2","datetime":"2014-11-06T08:18:18Z"}

Default
{"response":"OK","code":0,"client":"mfdb-json","version":"0.22","serverID":"20140530.1","datetime":"2014-11-06T08:18:18Z"}

The error for SSL is different from what you received, but TLS seems to work the same.

I then tried it from the nPVR computer, and got this result:

Code:

Trying SSL
The server committed a protocol violation. Section=ResponseStatusLine

Trying TLS

The server committed a protocol violation. Section=ResponseStatusLine


Default

The server committed a protocol violation. Section=ResponseStatusLine

So something is clearly wrong with XP on the media computer. I will start by updating .NET

Unfortunately, I now have to go out on location for a few weeks, so I won't be able to wrestle with the problem until after Thanksgiving. I will be reverting back to 3.2.9 in the meantime, before my wife kills me (She does not yet know that I failed to record "Dancing with the Stars" on Monday - Please don't tell her).