Problem reaching Schedule Direct - Only Emby Jail

[Baenwort 97]

So I can reach scheduledirect.org from both a W10 PC, TrueOS laptop, Android and iOS phones, and from the FreeNAS system itself via the CLI and using PING. However, Emby server reports that it can reach scheduledirect when I try to retrieve lineup data or when I try to re-add scheduledirect after deleting the entry in the LiveTV tab of the server config. It even works from the server jail CLI.

 

I've attached the Emby log with the error and below is the result of a ping command from the jail at the same time the log was generated.

root@emby_2:/ # ping -c 5 json.schedulesdirect.org                              
PING lb-sd-832157689.us-east-1.elb.amazonaws.com (52.4.157.82): 56 data bytes   
64 bytes from 52.4.157.82: icmp_seq=0 ttl=227 time=63.500 ms                    
64 bytes from 52.4.157.82: icmp_seq=1 ttl=227 time=56.190 ms                    
64 bytes from 52.4.157.82: icmp_seq=2 ttl=227 time=50.479 ms                    
64 bytes from 52.4.157.82: icmp_seq=3 ttl=227 time=51.388 ms                    
64 bytes from 52.4.157.82: icmp_seq=4 ttl=227 time=51.149 ms                    
                                                                                
--- lb-sd-832157689.us-east-1.elb.amazonaws.com ping statistics ---             
5 packets transmitted, 5 packets received, 0.0% packet loss                     
round-trip min/avg/max/stddev = 50.479/54.541/63.500/4.918 ms  

SDerrorLog.txt

Edited February 1, 2018 by Baenwort

[Luke 37087]

It's not just schedules direct it's all other domains as well so it looks like you need to configure the network connection of the jail.