I have a Mac Mini running OS X server, I've read all of the issues people are having with it. An idea I have is running PlexConnect on a port other than 80. How I figure it is something like this.
Set the Apple TV DNS server to your OS X Server
Start an instance of PlexConnect running on port 4000 (for example)
In the hosts file of your server route all traffic from trailers.apple.com to 10.0.1.2:4000 (Server IP with the new port)
I'm not sure if this will work, however, I would like to give it ago. What I can't figure out is how to start PlexConnect on another port. When I try and initialize PlexConnect via the 'sudo ./PlexConnect.py command I get this. What would I edit to run PlexConnect on a different port?
PlexConnect : ***
PlexConnect : PlexConnect
PlexConnect : Press ENTER to shut down.
PlexConnect : ***
PlexConnect : IP_self: 10.0.1.7
PlexGDM : ***
PlexGDM : looking up Plex Media Server
PlexGDM : ***
PlexGDM : servers discovered: 1
DNSServer : Failed to create socket on UDP port 53: [Errno 48] Address already in use
I have a Mac Mini running OS X server, I've read all of the issues people are having with it. An idea I have is running PlexConnect on a port other than 80. How I figure it is something like this.
Set the Apple TV DNS server to your OS X Server
Start an instance of PlexConnect running on port 4000 (for example)
You can't, it needs to be where the trailers app is looking for it, which means port 80 for http/.xml and port 53 for DNS.
host files cannot be used for port translation, only name resolution.
If you are not actually using port 80 on the server and have a router/firewall that lets you do internal NAT, you could have all incoming traffic to port 80 actually go to another port.
If you are not actually using port 80 on the server and have a router/firewall that lets you do internal NAT, you could have all incoming traffic to port 80 actually go to another port.
but... it wants to be on port 80... so if port 80 is not being used... no need to do anything... it'll just run.
but... it wants to be on port 80... so if port 80 is not being used... no need to do anything... it'll just run.
you're right. i didn't think it all the way through. i didn't have my coffee.....
This would work if they let us change the port though. he could change plexconnect to port 8008, then set the nat to send port 80 to port 8008 and atv would still think its 80.
I got PlexConnect working where I originally had the following error:
DNSServer : Failed to create socket on UDP port 53: [Errno 48] Address already in use
My situation was, a program installed on my OSX 10.8.3 called Splashtop Streamer used port 53. I tried to change the port setting in the PlexConnect setting.py without avail.
After removing the Splashtop software, PlexConnect started successful.
I tried to use another port for PlexConnect (8080), because I allready have an Apache instance which listen on port 80.
I just changed the listen port on WebServer.py, and configure an Apache virtual host to act as a reverse proxy to bind request intended for trailers.apple.com to the PlexConnect webserver.
In the PlexConnect logs, I can see that requests from the ATV are successfully relayed from Apache to the PlexConnect webserver.
But when I launch the Traliers app, I could see that PlexConnect successfully intercept the request, but the ATV says that the trailers server is "unavailable for now".
It works well if I stopped my Apache instance and configure PlexConnect to run on port 80.
Did I miss something in the Apache proxy?
I think that some requests are special in some way and are not routed by the Apache proxy.
