Schedules Direct - Errors on Auto Update, Manual Updates Work

[blaal02]

Hi,
I'm having troubles getting an EPG auto update to work. But updating manually from NPVR works fine.
Attached logs show the auto-update issue (NRecord.log), and the manual update working (NPVR.log).
Running on Win 8.1 x64. System did have 3.3.8 installed (and same EPG update issue). But 3.3.8 uninstalled & Users\Public\NPVR deleted before this install.
I tried the latest version I could see of NShared.dll (from 5/22). Also, the SchedulesDirect URL in the config file didn't seem to have the same date as the interface that was reported in the manual log, so I changed it. But neither seemed to make any difference.
Any thoughts?
Thanks!!

[sub]

Also, the SchedulesDirect URL in the config file didn't seem to have the same date as the interface that was reported in the manual log, so I changed it.

That setting isn't used anymore. There were quite large changes between SD API versions, so it became obvious there was no point in letting the user configure the url, since you need to code and parsing logic that matches. Instead the release now hardcodes the Schedules Direct it needs.

Was it a one-off error, or consistently doing this? Can you post another set of logs from a previous night so I can compare?

[blaal02]

Hi Sub,
Setting not used anymore - makes sense; I was just grasping!!
Unfortunately, it's highly reproducible. What got me a bit surprised was the address it said it was trying to connect to; loopback on some high port number - reminiscent of an FTP style backward connection. Or maybe it thinks I'm using a proxy? (Not intentionally!). This is sounding like something you've not already seen 17 times, so probably something I've done. But it's a fairly simple machine - Win 8.1 x64, NextPVR 3.4.8, Kodi 14.2. US OTA - all of 6 stations, Hauppague 1850.
I tidied everything up to get you a clean log, so nothing from yesterday. But I'll get a new one shortly.
Thanks again!

[sub]

Unfortunately, it's highly reproducible. What got me a bit surprised was the address it said it was trying to connect to; loopback on some high port number

Yep, this is confusing me too. I'm not sure why it's doing that. It wouldn't normally do anything like.

I was thinking either you've got something weird like a hosts file that resolves json.schedulesdirect.org to 127.0.0.1, or firewall software that is redirecting through it's own local proxy. Eitherway, it didn't look normal.

[blaal02]

As we had basically concluded... my problem! I did indeed find traces of proxy settings on local port 60138 in the registry. I'm not sure where the settings came from, and just removing from the registry didn't help - so I gave up & reinstalled Windows! (Wanted it on a different drive anyway, and it is a fairly simple machine. But has been through a few iterations). Thanks again for pointing me in the right direction.