December 24th 2022

Did not receive a response from a token request

There is a known problem some locations (east coast Verizon for sure) with IPV6 routing. The Amazon load balancer used by the SD-JSON service supports IPV6 and most OSs and providers prefer IPV6. This is causing above error, especially with EPG123.

To work around the problem, you can disable IPV6 in your network settings (who really uses it anyway??) Or upgrade EPG123 to v1.7.3.5 which uses instead of

The problem is not on the Schedules Direct side, but ISP or home network routing, we've been unable to duplicate the problem.