Cannot load Schedules Direct in Version 6.1

[wingman]

I have been using NextPVR (version 4.x running on 64-bit Windows 10) with Schedules Direct for 5 or 6 years with no problems, but recently updated to NextPVR 6.1 and have not been able to get it to load Schedules Direct EPG.  I have checked and doublechecked my SD login username and pw, but SD is not listed as an available EPG Source on the Settings/Guide page (only option is DVB/ATSC EPG).  If I click on Add SD Channel Lineup and enter my zip code (67037) and click Search, nothing happens.  On the Settings/Channels page, each channel shows DVB/ATSC EPG as the EPG Source.  If I click on the wrench, select "...Add Schedules Direct Lineup...." (which isn't always available as an option), enter my SD login credentials and zip code, and click Search, nothing happens and the channel EPG Source remains unchanged.  I do not have a very detailed nuts-and-bolts knowledge of configuring NextPVR and SD, so it is not clear to me where the disconnect is.  Can you assist?

Thanks - Ed

[mvallevand]

I think this is probably what you need to do https://forums.nextpvr.com/showthread.ph...#pid578563

Martin

[wingman]

Martin - Thanks for the prompt response. I have repeatedly verified username and password, to the point of even cutting and pasting them from my successful login at schedulesdirect.org, so I'm pretty certain it is not my credentials. Plus, when I have entered my SD username or password incorrectly on the Settings/Guide page, I receive an error telling me so. I do not know what the IPv6 issue is. Everything worked fine in version 4.5, so I'm not sure where the issue is in my version 6.1 setup

[mvallevand]

Right so you need to create the ticket. The issue with T-Mobile for sure and Verizon are they don't provide a fixed IPv4 address to SD so they think you are multiple users with one account. VPN users will have this too


Martin

[wingman]

I have created a SD ticket and am awaiting a response.  In the meantime, my internet service provide is Cox (not TMobile or Verizon).  I neglected to mention that I am also running ExpressVPN, however this was never a problem with NVPR version 4.x.  Disabling ExpressVPN appears to allow NVPR to connect to SD, so what do I need to do to enable NVPR to also connect to SD when ExpressVPN is active (as NVPR was able to do with NVPR version 4.x)?  Thanks

[mvallevand]

Wait. It has nothing to do with v4 vs v6 and everything to do with changes made by Schedules Direct.

Martin

[wingman]

Hopefully the response to my SD ticket will provide some help, but this definitely appears connected to my ExpressVPN since NVPR is able to connect to SD when ExpressVPN is disabled. Note that this worked fine in NVPR version 4 up until I uninstalled it earler this week to install NVPR version 6. I don't doubt that it may be a SD issue, I just do not know how to resolve it. I'm looking into port forwarding, the info I've found so far applies to ExpressVPN running on a router, whereas mine is installed on my Windows10 PC.

[mvallevand]

For sure the VPN plays into it but SD have to deal with it not NextPVR.

Martin.

[boringgit]

Have you looked into split tunnelling?

Effectively you send most of your traffic over the VPN but break some out locally.

If you are a privacy "enthusiast" you may not like this idea.... But if it fixes SD....

[wingman]

Thanks boringgit - I'll look into this...