Cant get Plex Connect to work

Dev Community Apps & Creations
1

I can't get Plex Connect to work as I am getting the dreaded "01:09:45 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use" error.. I don't know what is using this port. I ran a terminal command to find out what it is and this is what I got COMMAND PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME

named   177 root   20u  IPv6 0x839ecdcb0a1fbcb9      0t0  TCP *:domain (LISTEN)

named   177 root   21u  IPv4 0x839ecdcb0c2dd569      0t0  TCP localhost:domain (LISTEN)

named   177 root   23u  IPv4 0x839ecdcb0d1f93c9      0t0  TCP 192.168.1.5:domain (LISTEN)

named   177 root  512u  IPv6 0x839ecdcb0c1fd231      0t0  UDP *:domain

named   177 root  513u  IPv6 0x839ecdcb0c1fd231      0t0  UDP *:domain

named   177 root  514u  IPv6 0x839ecdcb0c1fd231      0t0  UDP *:domain

named   177 root  515u  IPv6 0x839ecdcb0c1fd231      0t0  UDP *:domain

named   177 root  516u  IPv4 0x839ecdcb0c1fcfd9      0t0  UDP localhost:domain

named   177 root  517u  IPv4 0x839ecdcb0c1fcfd9      0t0  UDP localhost:domain

named   177 root  518u  IPv4 0x839ecdcb0c1fcfd9      0t0  UDP localhost:domain

named   177 root  519u  IPv4 0x839ecdcb0c1fcfd9      0t0  UDP localhost:domain

named   177 root  520u  IPv4 0x839ecdcb09e400a9      0t0  UDP 192.168.1.5:domain

named   177 root  521u  IPv4 0x839ecdcb09e400a9      0t0  UDP 192.168.1.5:domain

named   177 root  522u  IPv4 0x839ecdcb09e400a9      0t0  UDP 192.168.1.5:domain

named   177 root  523u  IPv4 0x839ecdcb09e400a9      0t0  UDP 192.168.1.5:domain

 

What do I need to do to get this working again!!

 
2

What does this output when ran in a terminal:


sudo lsof -i :53


Can you reboot the PlexConnect host to see if that fixes it?

3

When I run the above command in terminal that is the output I am getting.

brian:~ brianpatterson$ sudo lsof -i :53

COMMAND PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME

named   176 root   20u  IPv6 0x43c3f5d7142de2b7      0t0  TCP *:domain (LISTEN)

named   176 root   21u  IPv4 0x43c3f5d716107f57      0t0  TCP localhost:domain (LISTEN)

named   176 root   23u  IPv4 0x43c3f5d716107687      0t0  TCP 192.168.1.5:domain (LISTEN)

named   176 root  512u  IPv6 0x43c3f5d715fc40bf      0t0  UDP *:domain

named   176 root  513u  IPv6 0x43c3f5d715fc40bf      0t0  UDP *:domain

named   176 root  514u  IPv6 0x43c3f5d715fc40bf      0t0  UDP *:domain

named   176 root  515u  IPv6 0x43c3f5d715fc40bf      0t0  UDP *:domain

named   176 root  516u  IPv4 0x43c3f5d715fc3e67      0t0  UDP localhost:domain

named   176 root  517u  IPv4 0x43c3f5d715fc3e67      0t0  UDP localhost:domain

named   176 root  518u  IPv4 0x43c3f5d715fc3e67      0t0  UDP localhost:domain

named   176 root  519u  IPv4 0x43c3f5d715fc3e67      0t0  UDP localhost:domain

named   176 root  520u  IPv4 0x43c3f5d7169d2cdf      0t0  UDP 192.168.1.5:domain

named   176 root  521u  IPv4 0x43c3f5d7169d2cdf      0t0  UDP 192.168.1.5:domain

named   176 root  522u  IPv4 0x43c3f5d7169d2cdf      0t0  UDP 192.168.1.5:domain

named   176 root  523u  IPv4 0x43c3f5d7169d2cdf      0t0  UDP 192.168.1.5:domain

 
How do you reboot the plea host?
4

If you mean reboot the computer - then I have done that countless times.

5

Please provide the info request in the "how to report an issue" link as it will give us an idea of what might be causing the issue, e.g. if you happen to be running the server version of OSX.

6

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