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

[MarkHotchkiss]

That's why I asked about port addresses (see post #27). I have a proxy-server that needs outgoing ports explicitly opened, unlike most firewalls. It's much harder to maintain than a normal firewall, but much more secure.

I was expecting a timeout or some other error message if the proxy-server was blocking the request. The system does not usually fail silently like this.

I will try to put Wireshark on the connection later, and get a glimpse at the traffic, and I will also research JSON (I had not dealt with it before now).

Thanks again for your hard work.
Mark

[sub]

It's just talking to the standard https port 443.

[MarkHotchkiss]

Dang - I've never had problems with Https.

So the next step is wireshark. I will let you know what I find, but obviously this is my problem.

Thanks again, Sub.
Mark

[sub]

I've attached a version which is bit better at handling failures in this area. It'll at least give you a basic message telling you it's unable to connect, and should give you a more detailed message in the log files.

[MarkHotchkiss]

Hi Sub,

Thanks for the updated file. When I now click on "Find Lineups Available", I get an immediate "Unable to connect to Schedules Direct" message box. I attached the log, which indeed has additional errors listed, but probably not enough to diagnose from. I can proceed from here, by capturing the packets.

[sub]

2014-11-03 15:09:57.370 [ERROR][1] Unexpected error doing Schedules Direct login: System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at NShared.SchedulesDirectJSONEPGSource.DoPOSTRequest(String url, String token, String body)

That's an odd error. I'm not sure why you're getting this but no one else is.

[sub]

You could see if this makes any difference. It implements a suggestion I saw by googling that error message.

[MarkHotchkiss]

Sorry, sub, no difference that I can see. But here is the npvr.log anyway.

By the way, you probably know this already, but the "protocol violation" error occurs in the log as soon as I select "Schedules Direct" from the "Sources:" pull-down, not later when I get the "Unable to connect to Schedules Direct" message box.

I'm looking at the packet-dump right now, and will update you with what I find, but you shouldn't put much more time into it, as it's only my problem. Later tonight, when no one else is on the network, I will bypass the proxy-server and see what happens.

[sub]

I'm looking at the packet-dump right now, and will update you with what I find, but you shouldn't put much more time into it, as it's only my problem.

You probably wont see much, since it's https.

Later tonight, when no one else is on the network, I will bypass the proxy-server and see what happens.

I suspect it'll work then. It's most likely something odd ball about the proxy server causing this remaining error.

[MarkHotchkiss]

Hi Sub,

I took a cursory look at the wireshark dump, and all I could see is that nPVR made two connections to Schedules Direct, and both connections were returned "Accepted". I have not parsed out the rest of the dump yet, because bypassing the proxy-server was more interesting.

As I type this, I am on the nPVR machine, connected directly to the Internet, without any firewall. Fetching lineups still fail at the same point (with your new message box), but it now takes a few seconds when selecting "Schedules Direct" from the "Source:" pull-down and then when selecting "...manage lineups...". The response was instant when using the proxy-server, but not when connected directly.

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.