After one day of trying and trying, reading thread after thread in several forums, I am close to sell my ATV3 again because I am not able to get PlexConnect to work. I am a really sad panda.
I could follow every step in the manual and I repeated them several times. All I get is the Failed to connect to HTTP on 192.168.1.44 port 53: [Errno 48] Address already in use
I changed the Settings.cfg file to use port 80 instead and I get the same error message.
I am using a new iMac with the latest Mavericks build. I have Dropbox, Transmission, Airmail, Beamer, Firefox, Radium and Little Snitch installed (I have other software but they don't use Internet).
I use a RT-N16 Router. I have ports 53 and 80 completely open. Ah, and I changed my local IP to a static one.
What else should I do? Can someone please help me, I really don't have any knowledge to get this to work.
This is the complete message:
sudo "/Applications/PlexConnect-master/PlexConnect.py"
01:10:15 PlexConnect: ***
01:10:15 PlexConnect: PlexConnect
01:10:15 PlexConnect: Press CTRL-C to shut down.
01:10:15 PlexConnect: ***
01:10:15 PlexConnect: started: 01:10:15
01:10:15 PlexConnect: Version: 0.3.1+
01:10:15 PlexConnect: Python: 2.7.5 (default, Mar 9 2014, 22:15:05)
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)]
01:10:15 PlexConnect: Host OS: darwin
01:10:15 PlexConnect: IP_self: 192.168.1.44
01:10:15 DNSServer: started: 01:10:15
01:10:15 DNSServer: ***
01:10:15 DNSServer: DNSServer: Serving DNS on 192.168.1.44 port 54.
01:10:15 DNSServer: intercept: ['trailers.apple.com'] => 192.168.1.44
01:10:15 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
01:10:15 DNSServer: forward other to higher level DNS: 8.8.8.8
01:10:15 DNSServer: ***
01:10:15 WebServer: started: 01:10:15
01:10:15 WebServer: Failed to connect to HTTP on 192.168.1.44 port 80: [Errno 48] Address already in use
01:10:15 PlexConnect: WebServer not alive. Shutting down.
01:10:15 PlexConnect: Shutting down.
01:10:20 DNSServer: Shutting down.
01:10:20 PlexConnect: shutdown
01:10:20 PlexConnect: shutdown
You need to find out what is using port 53. If you want to debug start removing programs one by one until you find the culprit and check your listen port isnt 53 in your apache2 config in /etc/apache2/httpd.conf. List your current plists in /library/launchdaemons. Can you test with a different os/device to rule out a network issue? If you dont want to troubleshoot reinstall your os.
If you edited your settings.cfg as @bakman1 noticed maybe you should start with a fresh copy of PlexConnect with unedited settings (do not edit settings.cfg). That is for advanced settings typically.
@wahlman.j: I am using a new setting.cfg since yesterday (actually I replaced the entire PlexConnect-master folder).
This is how it looks now:
11:02:47 PlexConnect: ***
11:02:47 PlexConnect: PlexConnect
11:02:47 PlexConnect: Press CTRL-C to shut down.
11:02:47 PlexConnect: ***
11:02:47 PlexConnect: started: 11:02:47
11:02:47 PlexConnect: Version: 0.3.1+
11:02:47 PlexConnect: Python: 2.7.5 (default, Mar 9 2014, 22:15:05)
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)]
11:02:47 PlexConnect: Host OS: darwin
11:02:47 PlexConnect: IP_self: 192.168.1.44
11:02:47 DNSServer: started: 11:02:47
11:02:47 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use
11:02:47 PlexConnect: DNSServer not alive. Shutting down.
11:02:47 PlexConnect: Shutting down.
11:02:47 PlexConnect: shutdown
11:02:47 PlexConnect: shutdown
The problem of port 53 persists.
Regarding your other tips:
what is apache2 config in /etc/apache2/httpd.conf? Isn't this a server thing? I have Mavericks installed. Not using it as a server. Also, I have this computer since just 3 days. I am using the Mavericks the computer came with.
>> sudo lsof -i :53 >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> Python 308 root 4u IPv4 0x72e0d069cb9fb645 0t0 UDP 192.168.1.44:domain
Looks like PlexConnect might already be running on your system, did you install the "daemon" stuff already? At that point you can't run it in a terminal again... But you won't need as everything should be good.
>>LaunchDaemons has: com.adobe.fpsaud.plist, com.apple.aelwriter.plist and com.apple.qmaster.qmasterd.plist
Is this the one in /user/library or top level /library?
PlexConnect will live inside the top level... running as root.
Log in as admin, do a sudo launchctl list | grep plexconnect. Will it show? Should come up with something like: 66-com.plex.plexconnect.bash
Also, this iMac should be new. At least it was completely sealed. And initially I could set it up as a new computer too. I did add some more memory, Fusion Drive and stronger graphic card, they probably did some test before sending it(?).
@Baa:
Yes, at the beginning, the first time I set PlexConnect up I run the daemon. I then used cd "/Applications/PlexConnect-master/support/OSX”
sudo ./uninstall.bash to uninstall it. I think there where some plist that I deleted manually...
Yes, the LaunchDaemons is root. Actually the user library doesn't have a LaunchDaemons, only a LaunchAgents. I run the sudo Isof again with port 53:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Python 308 root 4u IPv4 0x72e0d069cb9fb645 0t0 UDP 192.168.1.44:domain
It still appears the same.
I run the sudo launchctl list and yes, it showed up like that:
Unload and remove that file. It should be in /library/launchdaemons or /library/launchagents. Sounds to me that you used OpenConnect or openplex based on your httpd.conf (unrelated I think/hope)
Open terminal and type this when you navigate to the folder either:
Well. PlexConnect is running on your machine already.
From my point of view: "Everythign is fine." :-D
What is your issue now?
Did you reboot you machine after deleting those plists? At that point, PlexConnect shouldn't run anymore...
You could also use "sudo kill 96" or something to get rid of it. You might have to kill all the daughter processes as well. So a reboot might be easier.
Do you mean with sudo /Applications/PlexConnect-master/PlexConnect.py? Because if yes, thats what I am trying all the time and what gives me the error message...
