Failed to create socket on UDP port 53

Dev Community Apps & Creations
1

Hello

 

Recently i did hard reset to my router and since then i have problem running the Plex connect .

I wen and download the latest version and when i'm trying to run it i get this message :

 

Last login: Fri Aug  9 17:28:51 on ttys000
MacMini:~ ofirarbel$ cd /Users/ofirarbel/Documents/PlexConnect-XML_templates 
MacMini:PlexConnect-XML_templates ofirarbel$ sudo ./PlexConnect.py
17:31:12 PlexConnect: ***
17:31:12 PlexConnect: PlexConnect
17:31:12 PlexConnect: Press CTRL-C to shut down.
17:31:12 PlexConnect: ***
17:31:12 PlexConnect: started: 17:31:12
17:31:12 PlexConnect: IP_self: 10.0.0.102
17:31:12 DNSServer: started: 17:31:12
17:31:12 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use
17:31:12 PlexConnect: DNSServer not alive. Shutting down.
17:31:12 PlexConnect: Shutting down.
17:31:12 PlexConnect: shutdown
MacMini:PlexConnect-XML_templates ofirarbel$ 
 
 
any one had this issue before?
also what is the last beta version and where can i download it?
 
 
thanks 

 

2

Troubleshooting common error messages:

https://github.com/iBaa/PlexConnect/wiki/Troubleshooting

Latest version - github as well. Link see below.

3

but i don't have any DNS server 

i went to my router config page and it's on it's original settings

4

>> but i don't have any DNS server 

Sure? Internet sharing active or something?

Try to figure out WHO is sitting on that nice port...

5

This is a big problem

I can't figure what is wrong

this is my Router DNS page settings :

Screen+Shot+2013-08-10+at+3.07.04+PM.png

6

...port53 is NOT blocked on your router. Well. At least this is not the root cause for the error message.

You have something running on port53 on MacOS - another application or an old instance of PlexConnect/DNSServer.

There are a couple of threads discussing how to figure out the "bad" application - unfortunately I don't know off of my head how this can be done, either.

7

Have you tried rebooting your mac ever since? If PlexConnect stops abruptly, it might block the port for an undetermined time. One way around is to reboot your Mac.

Otherwise, it’s Baa said. You have something on that port 53 but very unlikely because OSX reserves that port usually and you can’t use it if you’re not the administrator. Hence the sudo requirement when running PlexConnect

8

The same problem on DS712+ after Installing DSM 4.3 beta :((( ...is there any solution

9

...first you got to figure out what's sitting on that port. When doing so, look at port 80 as well, it might be you next issue. :-D

10

It could also be another instance of plexconnect if hes sure that hes not running anything dnsserver like

11

...first you got to figure out what's sitting on that port. When doing so, look at port 80 as well, it might be you next issue. :-D

how can I do this??? before DSM update everything was OK.

12

I mac restart worked for me, plexconnect was runing in the background and could not be manualy stopped

13

>> I mac restart worked for me, plexconnect was runing in the background and could not be manualy stopped

Well. No. You can stop it...

In terminal "ps -ef" gives you a list of running tasks/processes.

Find PlexConnect and Python processes and use "sudo kill -9 " to get rid of all of them. Should be 1 python and 3 PlexConnect ones...

No reboot required.

14

how can I do this??? before DSM update everything was OK.

Hm. One possible way was using "lsof" or something. Use this as your search term here in the forum... a quick one - for example - brought this: http://forums.plexapp.com/index.php/topic/70892-error-with-installation-failed-to-create-socket-on-udp-port-53/?hl=lsof#entry409705

15

how can I do this??? before DSM update everything was OK.

Have a look at these posts:             #205            ,             #117            

16

I had the same problem and it turned out to be internet sharing in my network settings on my Mac. Turned that off and it works perfectly now.

17

he already fixed it as it was another instance of plexconnect running in the background.. :)

18

Have a look at these posts:             #205            ,             #117            

Thanks, setup DNS server, now 'trailers' is unavailble... :(

19

I’ve read DSM 4.3 cimes with a back ground Process called DNSsomething. If you kill it, IT should free the port.

And this is something else than setting up the dns server.

20

Folks,

Perhaps I'm coming into this thread a bit late, but I was having this problem too running Plex Media Centre on a Mac Mini connected to my LAN. Plex Connect running on the Mini too.

I found that Plex Connect would work for a bit upon restarting the Mac, then would stop working (seemingly at random). Trying to restart Connect said that the port was already in use. I wasn't sharing the internet connection, but found that quitting iTunes on the Mac Mini seems to have sorted things. I had iTunes running with Home Sharing enabled, so I can only assume this was the other server that was causing the problem.

With iTunes off, Plex Connect has been running fine for the last 2 weeks.

Andy