I run apache on the same machine as plexconnect and my solution was to change the apache port to 8080 and use my router to forward traffic from public 80 to private 8080.
Best of both worlds in my opinion. Outside world still sees my site and local network sees plexconnect.
Ah, dumb moment on my part. I'll disable the web server and put it on another port :)
To accomplish running PC on port 90, and keep my webserver on 80, I changed the port in PC, and added a VirtualHost on trailers.apple.com in apache with a transparent proxy passing it to the other port...
The only issue I see with that is that it isn’t just the trailers.apple.com calls that need to be redirected. It’s all the traffic from the AppleTV even the stuff from Netflix, Hulu, etc.
FYI I fixed mine, which also had port 80 running, by doing the following from the terminal:
cd /etc/apache2
sudo vi httpd.conf
find the line that has port 80 in it by typing /80 and hitting return
change this line to something like 8080 (HIT R to overwrite)
save the file (escape Z Z)
then
sudo apachectl restart
Good luck and msg me if you get stuck with these instructions.
I am having the same issue on Mac OS X 10.8.3 with PMS 0.9.7.22.511
Initially PlexConnect could not even see PMS (on same box). In 'setting.py' I had to change the ip_pms to the ip that my PMS was running on. I also had to delete the auto generated settings.cfg and then re-run the sudo ./PlexConnect.cy command.
I now get the following:
Password:
PlexConnect : ***
PlexConnect : PlexConnect
PlexConnect : Press ENTER to shut down.
PlexConnect : ***
PlexConnect : IP_self: 192.168.1.102
PlexGDM : ***
PlexGDM : looking up Plex Media Server
PlexGDM : ***
PlexGDM : servers discovered: 1
PlexConnect : PMS: 192.168.1.102:32400
DNSServer : ***
DNSServer : Starting up.
DNSServer : intercept trailers.apple.com: 192.168.1.102
DNSServer : forward other to higher level DNS: 8.8.8.8
DNSServer : ***
WebServer : Failed to connect to port 80 (http): [Errno 48] Address already in use
PlexConnect : WebServer not alive. Shutting down.
DNSServer : Shutting down.
I see that port 80 is in use, but cannot seem to identify what is using it? I am not knowingly running a web server. I have also disabled little snitch and even closed down dropbox on the off chance that was causing issues.
I have run sudo lsof -i :80 and nothing is showing up there.
I have run sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist however it appears as though apache is not running on my system.
Not trying to hijack the post but just trying to add information.
Thanks everyone for their input/assistance.
EDIT: Perhaps there is a webserver running. When I enter 127.0.0.1:80 into my browser, it shows a page that says It Works! Hopefully that will help out a bit
I am having the same issue on Mac OS X 10.8.3 with PMS 0.9.7.22.511
Initially PlexConnect could not even see PMS (on same box). In 'setting.py' I had to change the ip_pms to the ip that my PMS was running on. I also had to delete the auto generated settings.cfg and then re-run the sudo ./PlexConnect.cy command.
I now get the following:
Password:
PlexConnect : ***
PlexConnect : PlexConnect
PlexConnect : Press ENTER to shut down.
PlexConnect : ***
PlexConnect : IP_self: 192.168.1.102
PlexGDM : ***
PlexGDM : looking up Plex Media Server
PlexGDM : ***
PlexGDM : servers discovered: 1
PlexConnect : PMS: 192.168.1.102:32400
DNSServer : ***
DNSServer : Starting up.
DNSServer : intercept trailers.apple.com: 192.168.1.102
DNSServer : forward other to higher level DNS: 8.8.8.8
DNSServer : ***
WebServer : Failed to connect to port 80 (http): [Errno 48] Address already in use
PlexConnect : WebServer not alive. Shutting down.
DNSServer : Shutting down.
I see that port 80 is in use, but cannot seem to identify what is using it? I am not knowingly running a web server. I have also disabled little snitch and even closed down dropbox on the off chance that was causing issues.
I have run sudo lsof -i :80 and nothing is showing up there.
I have run sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist however it appears as though apache is not running on my system.
Not trying to hijack the post but just trying to add information.
Thanks everyone for their input/assistance.
EDIT: Perhaps there is a webserver running. When I enter 127.0.0.1:80 into my browser, it shows a page that says It Works! Hopefully that will help out a bit
That sounds like the built in osx web sharing feature. Do you have osx server app installed on this box?
Same problem here. PlexConnect worked for 2 days without issue until this afternoon. I thought I'd start from scratch again and then I got the following:
Same problem here. PlexConnect worked for 2 days without issue until this afternoon. I thought I'd start from scratch again and then I got the following:
Password:
19:17:04 PlexConnect: started: 19:17:04
19:17:04 PlexConnect: ***
19:17:04 PlexConnect: PlexConnect
19:17:04 PlexConnect: Press CTRL-C to shut down.
19:17:04 PlexConnect: ***
19:17:04 PlexConnect: IP_self: 10.0.1.5
19:17:04 PlexConnect: started: 19:17:04
19:17:04 DNSServer: started: 19:17:04
19:17:04 DNSServer: ***
19:17:04 DNSServer: Starting up.
19:17:04 DNSServer: intercept trailers.apple.com: 10.0.1.5
19:17:04 DNSServer: forward other to higher level DNS: 8.8.8.8
19:17:04 DNSServer: ***
19:17:04 WebServer: started: 19:17:04
19:17:04 WebServer: Failed to connect to HTTP on 0.0.0.0 port 80: [Errno 48] Address already in use
19:17:04 PlexConnect: WebServer not alive. Shutting down.
19:17:09 DNSServer: Shutting down.
thinking of downgrading and going back to the old plex :mellow: This is getting on my nerves!
Or you could read the wiki on common errors messages and find out what is already hogging port 80 on your system and fix the root cause:
I know -I couldn't provide all the info because I've been traveling and have hardly been at the computer plex runs on of late
I have to say though - as an ex-technical writer, the quality of the info in the wiki, and the official install instructions/info have gone downhill compared to when I first started using plex a few years ago. If that information was more accessible, and also easier to understand for those not that technically inclined, most people wouldn't need to post in the first place. :rolleyes:
I know -I couldn't provide all the info because I've been traveling and have hardly been at the computer plex runs on of late
I have to say though - as an ex-technical writer, the quality of the info in the wiki, and the official install instructions/info have gone downhill compared to when I first started using plex a few years ago. If that information was more accessible, and also easier to understand for those not that technically inclined, most people wouldn't need to post in the first place. :rolleyes:
Fair enough that you do not have access to it but then expecting others to be able to understand what the problem is and help you without really necessary information is a little silly.
If you are talking about the PlexConnect instructions i am amazed how you have found it has gone downhill from a few years ago as it did not even exist until a few months ago (PlexConnect is created by a third party team and not Plex Inc.).
Also bear in mind it is a alpha/beta at the moment so there is a reason why the instructions do not contain e.g. screencasts; these will come once the code stabilises and it becomes more accessible e.g. removal of the need for the terminal.
If you want to be an early adopter then you can either understand you are an early adopter, but feel free to use your skills to message me rewrites of things that do not meet your standards and i will look to see whether they should be used instead ;)
It is a core team of three people, with some other making contributions and we have a lot on as well e.g. within 4 months i have been married, found and bought a house, moved in and have a child on the way.
Contributions of help are always welcome to help us with our busy schedules :)
