>>What I have ended up finding to be the culprit was the ip_pms setting in the Settings.cfg file. It seems that it managed to change itself somehow from the correct IP of my PlexConnect server to 192.168.178.10 which I've discovered is the default setting in the Settings.py file of PlexConnect. I followed the installation instructions to the letter when reinstalling PlexConnect but for some reason that ip_pms setting remains at 192.168.178.10 and as soon as you manually change the DNS in your ATV you lose connection.
ip_pms has NOTHING to do with the internet connectivity of your aTV. In fact, as long as enable_plexgdm is on, that settings is not used at all...You got to make sure ip_dnsmaster is set correcty... to either google (8.8.8.8), you ISP's or any other good one out there.Be that as it may, I only had to make one change to the Settings.cfg file and that was to change ip_pms, to go from NO internet connectivity to FULL connectivity. Nothing else was changed.Also, ip_dnsmaster was set correctly to 8.8.8.8.Once you change the aTV DNS to manual and you computer's IP, you got to make sure PlexConnect is running there... otherwise your aTV will loose it's function, being unable to lookup the service's hosts.>>I have one question for anyone who might have an answer. This is what I see in Terminal when PlexConnect runs:>>...>>13:53:36 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in useYou already got some sort of DNS server running. If you spend your time getting PlexConnect to run, it might be just another instance of it. Do you still have another terminal window hiding in the background? Did you install it as service or daemon?There are no other Terminal windows hiding in the background. I followed the instructions to run PlexConnect as a launchctl daemon from here: https://github.com/iBaa/PlexConnect/wiki/Install-Guide-Mac. I have no idea if that was necessary or even desirable.
>>What I have ended up finding to be the culprit was the ip_pms setting in the Settings.cfg file. It seems that it managed to change itself somehow from the correct IP of my PlexConnect server to 192.168.178.10 which I've discovered is the default setting in the Settings.py file of PlexConnect. I followed the installation instructions to the letter when reinstalling PlexConnect but for some reason that ip_pms setting remains at 192.168.178.10 and as soon as you manually change the DNS in your ATV you lose connection.
ip_pms has NOTHING to do with the internet connectivity of your aTV. In fact, as long as enable_plexgdm is on, that settings is not used at all...You got to make sure ip_dnsmaster is set correcty... to either google (8.8.8.8), you ISP's or any other good one out there.Be that as it may, I only had to make one change to the Settings.cfg file and that was to change ip_pms, to go from NO internet connectivity to FULL connectivity. Nothing else was changed.Also, ip_dnsmaster was set correctly to 8.8.8.8.Once you change the aTV DNS to manual and you computer's IP, you got to make sure PlexConnect is running there... otherwise your aTV will loose it's function, being unable to lookup the service's hosts.>>I have one question for anyone who might have an answer. This is what I see in Terminal when PlexConnect runs:>>...>>13:53:36 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in useYou already got some sort of DNS server running. If you spend your time getting PlexConnect to run, it might be just another instance of it. Do you still have another terminal window hiding in the background? Did you install it as service or daemon?There are no other Terminal windows hiding in the background. I followed the instructions to run PlexConnect as a launchctl daemon from here: https://github.com/iBaa/PlexConnect/wiki/Install-Guide-Mac. I have no idea if that was necessary or even desirable.
Actually, I think the port 53 problem was because I had run PlexConnect.py twice in Terminal. That's why it showed as being already in use.
I have restarted my Mac and this is the PlexConnect.log:
16:24:21 PlexConnect: started: 16:24:21
16:24:21 PlexConnect: Version: 0.3.1+
16:24:21 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)]
16:24:21 PlexConnect: Host OS: darwin
16:24:21 PlexConnect: IP_self: 10.0.1.113
16:24:22 DNSServer: started: 16:24:22
16:24:22 DNSServer: ***
16:24:22 DNSServer: DNSServer: Serving DNS on 10.0.1.113 port 53.
16:24:22 DNSServer: ***
16:24:22 WebServer: started: 16:24:22
16:24:22 WebServer: ***
16:24:22 WebServer: WebServer: Serving HTTP on 10.0.1.113 port 80.
16:24:22 WebServer: ***
16:24:22 WebServer: started: 16:24:22
16:24:22 WebServer: ***
16:24:22 WebServer: WebServer: Serving HTTPS on 10.0.1.113 port 443.
16:24:22 WebServer: ***
16:36:03 PlexAPI: ***
16:36:03 PlexAPI: looking up Plex Media Server
16:36:03 PlexAPI: ***
16:36:04 PlexAPI: GDM: Servers discovered: 1
16:36:04 PlexAPI: Servers (local+MyPlex): 1
There is full connectivity and everything is working as it should. And again, this was accomplished by only changing ip_pms in Settings.cfg.
no... more likely it was accomplished by starting/running PlexConnect on your computer. Shut it down, and aTV will loose connection.
Believe me ip_pms has 1) nothing to do with aTV's ability to access the net and 2) is not even used with plex_gdm=False.
no... more likely it was accomplished by starting/running PlexConnect on your computer. Shut it down, and aTV will loose connection.
Believe me ip_pms has 1) nothing to do with aTV's ability to access the net and 2) is not even used with plex_gdm=False.
That's very strange indeed.
1. When I change it back to 192.168.178.10 and I have no connectivity, what would you attribute that to, then?
2. In my case, enable_plexgdm = True. Could that have anything to do with it?
PlexConnect not running? Please attach a log...
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
