I had similar problems on my server. Turning DNS off was the only solution...except the next problem is that OS X server seems to always have an httpd process running on port 80 (for server management I think) even if you turn off the Websites service. I haven't had time to do much research on this (or if there is a way to turn it off) but my temporary solutions is:
1. Turn off the DNS service (mine is not doing much at the moment so it was safe for me)
2. Turn of the Websites service
3. Kill all httpd processes (in Terminal or Activity Monitor)
4. Quickly launch PlexConnect.py and hope it loads before launchd reloads httpd
I'd like to have a look at having OS X Server the work of DNSServer.py and WebServer.py (since OS X Server is already running these services). It should be possible to make this happen so you can use PlexConnect without disrupting the DNS and Websites services. I don't know if I possess the mad skills to make this happen but I'll have a look at it when I have the time.
I think for simplicity I'm best with my original solution which is to start Airplay then start Plex Home Theatre/Plex. The only problem with it is that I can't use the Apple Remote as it controls the Apple TV rather than Plex Home Theatre and consequently kills Airplay. So I use the bluetooth keyboard for the iMac instead as a controller. Fine for me in a room that has the TV and the iMac in close proximity (Hong Kong!!) but not much of a solution for someone in a house or large apartment where they might be in separate rooms. I prefer to use Plex Home Theatre over the iPad or iPhone apps as I like to see the synopsis on pause.
I had similar problems on my server. Turning DNS off was the only solution...except the next problem is that OS X server seems to always have an httpd process running on port 80 (for server management I think) even if you turn off the Websites service. I haven't had time to do much research on this (or if there is a way to turn it off) but my temporary solutions is:
1. Turn off the DNS service (mine is not doing much at the moment so it was safe for me)
2. Turn of the Websites service
3. Kill all httpd processes (in Terminal or Activity Monitor)
4. Quickly launch PlexConnect.py and hope it loads before launchd reloads httpd
I'd like to have a look at having OS X Server the work of DNSServer.py and WebServer.py (since OS X Server is already running these services). It should be possible to make this happen so you can use PlexConnect without disrupting the DNS and Websites services. I don't know if I possess the mad skills to make this happen but I'll have a look at it when I have the time.
Good luck!
Please let me know if you have any success. Good luck!
I had similar problems on my server. Turning DNS off was the only solution...except the next problem is that OS X server seems to always have an httpd process running on port 80 (for server management I think) even if you turn off the Websites service. I haven't had time to do much research on this (or if there is a way to turn it off) but my temporary solutions is:
1. Turn off the DNS service (mine is not doing much at the moment so it was safe for me)
2. Turn of the Websites service
3. Kill all httpd processes (in Terminal or Activity Monitor)
4. Quickly launch PlexConnect.py and hope it loads before launchd reloads httpd
I'd like to have a look at having OS X Server the work of DNSServer.py and WebServer.py (since OS X Server is already running these services). It should be possible to make this happen so you can use PlexConnect without disrupting the DNS and Websites services. I don't know if I possess the mad skills to make this happen but I'll have a look at it when I have the time.
Good luck!
See my post here if you wish to disable the httpd service from being loaded by launchd.
