"We failed to reach a server" for PlexConnect trying to reach PMS

Dev Community Apps & Creations
1

Hi, I recently had to reconfigure my network when I switched to a new pfsense-based firewall. As part of the change, I moved my core network from 192.168.0.x to 192.168.1.x. I think I’ve fixed everything up, but I am unable to get PlexConnect to talk to PMS anymore.

If the log is literal in its output, it looks like PlexConnect is generating some funny URLs which are apparently not resolvable by my DNS. Full log pastebin: http://pastebin.com/6YVxdKNk The specific error is:

21:43:39 PlexAPI: No Response from Plex Media Server
21:43:39 PlexAPI: We failed to reach a server. Reason: [Errno -2] Name or service not known

Some versions:

  • I’m on an ATV v3 with 7.2.1. I can confirm that the ATV is pointing at the PlexConnect DNS.
  • Both PMS and PlexConnect are running on 192.168.1.13.
  • This is an Ubuntu 14.04 LTS machine, all up to date. It has worked for months before this.
  • I’m running PMS 0.9.16.3.1840-cece46d.
  • I’m running PlexConnect cfd51deffb

Settings.cfg:
[PlexConnect]
enable_plexgdm = False
ip_pms = 192.168.1.13
port_pms = 32400
enable_dnsserver = True
port_dnsserver = 53
ip_dnsmaster = 8.8.8.8
prevent_atv_update = True
enable_plexconnect_autodetect = False
ip_plexconnect = 192.168.1.13
hosttointercept = trailers.apple.com
port_webserver = 8001
enable_webserver_ssl = True
port_ssl = 443
certfile = ./assets/certificates/trailers.pem
allow_gzip_atv = False
allow_gzip_pmslocal = False
allow_gzip_pmsremote = True
loglevel = High
logpath = .

Any help is greatly appreciated! Thanks!

2

Oh and I can confirm that if I hit https://192.168.1.13:32400 from my Mac I get a cert warning (expected) and then an unauthorized page, so it looks like that is the correct address for PMS.

3

The thing is: plex.tv “knows” 3 addresses for your server. With the latest PlexConnect version each of them is triggered - the fastest response is supposed to win.
Now 2 of those addresses return with an error. That might be okay, if the third one (hopefully your local IP) went through. Unfortunately there is no indication of the successful end of the discovery process in your log - it kind of need prematurely.
Are you able to provide a log of the complete discovery? Is the PMS (re-)published correctly on the new network?

4

Thanks Baa, for your quick reply. I just figured out what was wrong. In short, I needed to workaround “DNS rebind” issues, as described in this thread: http://forums.plex.tv/discussion/213022/videos-wont-play-on-apple-tv/p1. I added some config for plex.direct to my router and now all is well.

Again, thanks for your quick reply, and for building this fantastic web client for Plex on ATV/3g!