PlexConnect Not Working After Upgrade to Mavericks (OSX Server)

Dev Community Apps & Creations
1

I just upgraded to Mavericks OSX Server and now PlexConnect won't work.

 

Attached is a log of PlexConnect on startup and then when trying to access from the Apple TV.  No errors are thrown but all I see on screen is: "Trailers is unavailable. Try again later."

 

PlexConnect.log (477 KB)

 

When I go to "trailers.apple.com" in the OSX Server browser, I get an XML file so I believe it should be working OK.  Did Apple TV's latest firmware break something? (Running 6.0.1)

2

Just curious but you installed mavericks, perhaps your pc pulled a new ip, double check you have your ip set correctly in the atv and such?  I know it seems stupid but sometimes the simplest things are the answer.

3

I can confirm that the IP of my server is the same (192.168.1.82).

Here are my PlexConnect settings:

[PlexConnect]
logpath = .
enable_dnsserver = False
ip_webserver = 192.168.1.82
prevent_atv_update = True
port_dnsserver = 53
enable_plexconnect_autodetect = True
port_pms = 32400
port_webserver = 9999
ip_plexconnect = 192.168.1.82
certfile = ./assets/certificates/trailers.pem
ip_dnsmaster = 192.168.1.82
loglevel = High
ip_pms = 192.168.1.82
enable_plexgdm = True
port_ssl = 443
enable_webserver_ssl = True
 
I have also made sure to redo all of the steps outlined here: http://forums.plexapp.com/index.php/topic/71085-a-guide-to-how-i-got-plexconnect-running-on-os-x-server-107/
 
I've had it working fine for months and like I said, viewing it in a browser yields the expected results.  Very strange.
4

>> 22:27:41 WebServer: WebServer: Serving HTTP on 192.168.1.82 port 9999.

Port 9999? Huh?
5

your vhost is disabled in apache due to the update, re-enable it and restart apache 

6

>> 22:27:41 WebServer: WebServer: Serving HTTP on 192.168.1.82 port 9999.

Port 9999? Huh?

I'm using port 9999, according to the instructions for OSX Server here.

your vhost is disabled in apache due to the update, re-enable it and restart apache 

bwynants - I'm not sure exactly how to do this.  Do you mean completing step 10 of this process (link)? If so, I've completed that already.  It's hard to tell if these files are being loaded, though.

7

And now... it seems to be working again, after setting my DNS server to 192.168.1.82 at the router level.  It must mean that the ATV was not using the DNS server I had specified.  Very strange.

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.