Error with installation "Failed to create socket on UDP port 53"

If you look at post #16 in this thread, I essentially renamed the "system configuration" folder and restarted the Mini. This removed the DNS server. Both myself and Apple are reasonably confident that this is a Plex Connect issue, because when attempting to reinstall plex connect again, I got the same error and the DNS issue has returned.

I've given up at this stage.....

My setup now is to run PMS on my mini. I can then open the plex app on my ipad and airplay it to my ATV.

I think I'll wait until Plex has a proper installer.

Hope this helps.

Cheers, Brett

Hello I have just joined this forum for this very issue.  I find myself in the same situation as Brett05.  I purchased a mac mini server with 10.7 server with grand plans of hosting my own email.  This never occurred and then I just purchased an ATV3 last week and wanted to install Plex Connect.  After much fluffing around I discovered it couldn't run on server so I updated to 10.8.  I have been trying again to run the PlexConnect.py file an get the same message as started this thread.  I guess this now means I have to find out how to turn off the DNS server as well.  When someone works this out can you please post on this thread so I can also hopefully get up & running as well.  PS I don't know anything about linux but and do know how to follow instructions to type into terminal. I have also been using macs for 10 years but only on the front end so I know my way around system preferences well enough.

If you look at post #16 in this thread, I essentially renamed the "system configuration" folder and restarted the Mini. This removed the DNS server. Both myself and Apple are reasonably confident that this is a Plex Connect issue, because when attempting to reinstall plex connect again, I got the same error and the DNS issue has returned.

I've given up at this stage.....

My setup now is to run PMS on my mini. I can then open the plex app on my ipad and airplay it to my ATV.

I think I'll wait until Plex has a proper installer.

Hope this helps.

Cheers, Brett

Then you spoke to someone at Apple who is clueless (please bear in mind that when you speak to an 'expert' at Apple you are actually almost certainly speaking to a customer service guy from an outsourced company in the same manner as when you ring your utility company - they just hide it a little better).
PlexConnect does NOT INSTALL THE BIND application!
You either have something else causing it to be installed and/or run (i am not sure if it is present on a default OSX install) either because of something else installed at some point or you have malware on your system hoping to hijack your DNS for nefarious means).
You can test this by backing up your machine, formatting it, installing 10.8.x client OS and then PlexConnect - you will not see the same issue.

I wasn't just dealing with the regular run of the mill support guys at Apple. I got upgraded through to a level 1 (1 being the hightest) advisor. He said that he is up to speed on BIND but it's something that has to be very very deliberately enabled.

I'll run a malware check to see if there are any issues of that nature.

Cheers, Brett

I solved this on Linux in a way that should also work for OSX (in my case I new I was running named as well as a webserver) and may be useful for others and for my own records as this is a bit of a hack and I should do proper code modes and send a pull request.

What you can do is simply add a secondary IP to your system that PlexConnect will use, on CentOS 6 modify

/etc/sysconfig/network-scripts/ifcfg-eth0

ADD: IPADDR2:

In OSX open network preferences and click the + icon to add another network adaptor on the same hardware e.g. Wifi and manually assign an address

Restart your network and make sure you can ping the new IP

In PlexConnect.py modify this line in def getIP_sef()

IP =

In WebServer.py modify this line

server = HTTPServer(('',80), MyHandler)

to

server = HTTPServer((,80), MyHandler)

In DNSServer.py modify this line

DNS.bind(('',53))

to

DNS.bind((,53))

Fill in any of the usual PlexConnect/PMS details from the very simple howto and you should be OK to run PlexConnect (worked for me anyway).

If you are also running a HTTP server on your box that is listening on all IP ports you will likely also want to modify the config so that it only listens on your old IP(s) and not the new one for PlexConnect

Please do not do the above as PlexConnect now has advanced options to allow you to do this, without changing the code.

If you do wish to use your own DNS server, web server or both there are guides for OSX, Windows and Linux in this forum (check the stickies).

  :)

One reason you might be running a DNS server on OS X without realizing it is Internet Sharing.  Go to System Preferences -> Sharing and if Internet Sharing is enabled, disable it and then try to run PlexConnect again.  Worked for me.

Same boat. Was working and now it's not. Nothing changed on machine either - not that would impact DNS Server at least.

Same boat. Was working and now it's not. Nothing changed on machine either - not that would impact DNS Server at least.


Please read the sticky on how to report an issue.
There is no way ANYONE could diagnose what issue you have from your post.

One reason you might be running a DNS server on OS X without realizing it is Internet Sharing.  Go to System Preferences -> Sharing and if Internet Sharing is enabled, disable it and then try to run PlexConnect again.  Worked for me.

Wow! Thank you so much. I cannot believe it's as easy as this! I've been searching for this for months and not one person from anywhere knew the answer.

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