switched DNS back to auto, updating firmware on ATV...
Because you have something hogging the DNS port 53, in the terminal [type] “sudo lsof -i -P” (without the quotes) to see what it is.
Because you have something hogging the DNS port 53, in the terminal [type] "sudo lsof -i -P" (without the quotes) to see what it is.
nothing on 53.... :wacko:
It was:
17:18:23 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use
17:18:23 PlexConnect: DNSServer not alive. Shutting down.
It was:
17:18:23 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use
17:18:23 PlexConnect: DNSServer not alive. Shutting down.
i even rebooted, and tried again, nothing comes up for port 53
So what comes up now?
So what comes up now?
18:13:27 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use
Same thing...
18:13:27 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use
Same thing...
odd thing is....this wasn't happening when i started the post
Updated fw to 6.0.2 ..... still getting caught on port 53 error, nothing showing up in activity monitor or terminal cmd
Well, PlexConnect must be running in order to link your aTV to PMS. If it doesn't - as stated in you log - you don't get that functionality.
>>17:18:23 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use
Something is using your DNS port (53) already... you got to figure out, what. :-)
Yeah, obviously port 53 is in use. So updating to 6.0.2 has nothing to do with that. First, get your plexconnect stuff running properly.
Port 53 is used by dns. Are you sure you:
1) Don't have any dns software running
2) Don't have some remains of an old plex connect running? (maybe some auto-start thing?) (don't know which OS you are on, but on Windows you can detect a running (background) plexconnect by checking for python.exe instances in the task manager)
If I had to make a bet, I'd say it's number 2 (old plexconnect stuff running), cause you didn't have the problem before and you have been fiddling around for some time now. You can also try another machine or reinstall your OS if you can't make it work.
Plexconnect isn't really that hard, I'm flabbergasted by how people can screw this up... But we are going to help you offcourse :)
My way of installing a new instance plexconnect is (I always do a fresh install after an update and I have also changed my plexconnect 2 times since I'm using it):
1) Make sure the cert is on ATV (you've already done that)
2) Copy certificates folder to asset folder of new instance (you've already done that, I think)
3) Start plexconnect
4) Shutdown plexconnect with CTRL-C (now a settings.cfg is created, THIS IS THE ONLY FILE YOU NEED TO EDIT)
5) Edit settings.cfg to my liking. Mine has GDM disabled and ip_pms pointing to my PMS
6) Start plexconnect
7) Start the trailers app and set everything the way I want it (MyPlex, Movie settings, subtitle settings, etc)
8) CTRL-C plexconnect again (this saves the ATV settings I made in step 7)
9) Start plexconnect (either manually, or through a scheduled task, server, launch script, etc)
10) Profit.
Apart from step 1 this is a 5 minute job...
/edit
I'm a bit harsh maybe, read back and you had it going for a while, you were just out of luck that your ATV was still on an old FW version. If you can manage to clear your DNS issue your good to go (as you're on the new firmware now :) ).
Yeah, obviously port 53 is in use. So updating to 6.0.2 has nothing to do with that. First, get your plexconnect stuff running properly.
Port 53 is used by dns. Are you sure you:
1) Don't have any dns software running
2) Don't have some remains of an old plex connect running? (maybe some auto-start thing?) (don't know which OS you are on, but on Windows you can detect a running (background) plexconnect by checking for python.exe instances in the task manager)
If I had to make a bet, I'd say it's number 2 (old plexconnect stuff running), cause you didn't have the problem before and you have been fiddling around for some time now. You can also try another machine or reinstall your OS if you can't make it work.
Plexconnect isn't really that hard, I'm flabbergasted by how people can screw this up... But we are going to help you offcourse :)
My way of installing a new instance plexconnect is (I always do a fresh install after an update and I have also changed my plexconnect 2 times since I'm using it):
1) Make sure the cert is on ATV (you've already done that)
2) Copy certificates folder to asset folder of new instance (you've already done that, I think)
3) Start plexconnect
4) Shutdown plexconnect with CTRL-C (now a settings.cfg is created, THIS IS THE ONLY FILE YOU NEED TO EDIT)
5) Edit settings.cfg to my liking. Mine has GDM disabled and ip_pms pointing to my PMS
6) Start plexconnect
7) Start the trailers app and set everything the way I want it (MyPlex, Movie settings, subtitle settings, etc)
8) CTRL-C plexconnect again (this saves the ATV settings I made in step 7)
9) Start plexconnect (either manually, or through a scheduled task, server, launch script, etc)
10) Profit.
Apart from step 1 this is a 5 minute job...
/edit
I'm a bit harsh maybe, read back and you had it going for a while, you were just out of luck that your ATV was still on an old FW version. If you can manage to clear your DNS issue your good to go (as you're on the new firmware now :) ).
Fine advice!
Hi guys, out of frustration i returned ATV and bought an Android Box, thanks for everyones efforts!
Such a shame...
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
