Not able to configure/update SD EPG...

[mvallevand]

His account info is fine I have used it here.  You can even see the account info in one of the valid json returns.  The way that the responses are being returned is what if confusing.  The 403 could be coming from the load balancer which is IP based but only Robert can diagnose this so as long as he ignores the ticket there doesn't appear to be anything NextPVR can do.


Martin

[sub]

Maybe had reason to think your IP address was one of the IPTV sources that had abused their artwork services in the past and they banned your IP or something.

Either way, it doesn't look like a NextPVR issue.

[henryixV]

Thanks for the ruminations and all the effort.  My SD creds are several years old (perhaps even pre-dating JSON and relying on the old method of putting the Lineup in the "login?") and I've never had any issues with it.  The closest explanation I've come to that would be something from my side is that I use T-Mobile for Internet and they use IPv6 internally in their network.  I've seen where my traffic gets handed off to the public 'net from three different states.  However, that tends to be on week-to-week basis, not conversation-based.  I've also been on the T-Mobile deal for 18+ months and would have expected issues long before now (using their network absolutely causes issues with a number of things, including VPN clients, but that's another story).  Maybe something recent caused SD to have an issue with my account...

Hopefully SD will poke their heads up in the next day or so and weigh in on what might be going on.

[mvallevand]

If the problem is with ipv6 and nat maybe try just one IP in the Windows hosts file to avoid the load balancer 

54.163.32.13 json.schedulesdirect.org

Martin 

[henryixV]

Hmm... That's an interesting approach. I'm not sure that's relevant for this particular case because all the 4-to-6 and garbage like that happens within their network. Unfortunately I can't set the hosts file on the SD side pointing to me, which is where I would think the primary issue would be (not to mention that's not even possible, though if I used a VPN that exited beyond the T-Mobile network, that might actually help...). So many options...

Terry

[mvallevand]

I would still try since 6 ipv4 IPs respond to that DNS name

Martin

[henryixV]

SD just responded and validated the issue lies with my access to their service: "Your tokens are getting invalidated because your access is coming from multiple IP addresses, and that's triggering the anti-token sharing detector."

It seems my T-Mobile Internet access has decided to have me exit via several different IPs from their network to the Internet, even in a single day (gleaned from information provided by SD). Whether this is a recent change by T-Mobile or a change in SD's anti-token sharing detector, or both, is not immediately clear as this has been working for 18+ months without issue. A "fix" is not readily apparent but at least the root cause is identified and a dialogue is open. I will make sure to update status here as things progress. I certainly understand if this thread should be moved as it really has absolutely nothing to do with Windows (and technically not even NextPVR).

Oh, and I did make the hosts file change Martin suggested, but, given the new information, it is not expected to have an effect (but, as always, I'd be happy to be proven wrong).

[curtvan]

Did you ever get this resolved? I have the same situation happening and my renewal for Schedules Direct is coming up. I am not inclined to renew if it won't work.

Thanks

[mvallevand]

Did you follow the steps I explained to open a line up ticket with Schedules Direct explaining your problem. They are fixing this on a case by case basis.

Martin

[curtvan]

I just did but have not heard back yet. I was just looking for a status update.

Thank you