AppleTV / Plexconnect issue

I am posting on behalf of my father and brother who are trying to get Plexconnect working between a Plex Server running on a Macbook and Plexconnect running on Apple TV. The following is therefore all remote from me so relayed by email / phone calls but as the more "IT literate" member of the family I have been asked to post the following:

 

Apple TV is set up according to:

 

https://github.com/iBaa/PlexConnect/wiki/Install-Guide

 

PlexServer is running on a Macbook (10.9.5) which is setup with a Static IP of 192.168.0.7 from the home DHCP pool (Sky Broadband DSL router)

 

Issues as follows:

 

1. When you try to view movies from the  PlexServer (via the Trailers Avatar) the error message seen on Apple TV is:

 

trailers is unavailable please try later

 

2. When you try to view movies from the Macbook the error message attached is shown

 

This corresponds to:

 

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

 

Appreciate ideas as to what to try next ?

In the pic attached it stats the error is that Port 53 is already in use, you/they need to identify what is using that port.

and if it is plexconnect.py (As the image sort of suggested they they have plexconnect running twice, so reboot and then run the sudo lsof -i :53 | grep LISTEN command again and see what it says, Before starting plexconnect)

also make sure they check the certificate is loaded on the ATV.

Next time you post please provide all the information requested in the pinned "READ BEFORE POSTING" thread, specifically the section on how to report an Issue this has a template of questions, which includes a log file, the image you posted is of the command window which is not the same as the log file.

Apologies - I posted the first query in a hurry and had not realised the protocol !

My brother has just collected this output:

  • Your ATV model (2 or 3) and firmware version (found under the ATV settings > general > about > Apple TV software): Model MC572B/A and firmware 6.2.1
  • The DNS server set on the ATV (found under the ATV settings > general > network > DNS):192.168.0.7
  • The local IP address of the device that PlexConnect is installed on:192.168.0.7
  • The device and operating system (including version number) that PlexConnect is installed on: MacBook Pro OSX Ver 10.9.5
  • The device and operating system (including version number) that the Plex media server (PMS) is installed on: MacBook Pro OSX Ver 10.9.5
  • The Plex media server (PMS) version number you are running (do not put 'latest'): Ver 0.9.11.1
  • The local IP address of the device that the Plex media server (PMS) is installed on: 192.168.0.7
  • The PlexConnect version number. If using Github source then a time and date of download (look at the creation date of the folder) and if you are using any non-standard setup e.g. Plexify or a fork. 23rd October 2014
  • The contents of your 'Settings.cfg' file (this is created at first clean shutdown of PlexConnect, using CTR+c)[PlexConnect]
  • enable_plexgdm = True
  • ip_pms = 192.168.178.10
  • port_pms = 32400
  • enable_dnsserver = True
  • port_dnsserver = 53
  • ip_dnsmaster = 8.8.8.8
  • prevent_atv_update = True
  • enable_plexconnect_autodetect = True
  • ip_plexconnect = 0.0.0.0
  • hosttointercept = trailers.apple.com
  • port_webserver = 80
  • enable_webserver_ssl = True
  • port_ssl = 443
  • certfile = ./assets/certificates/trailers.pem
  • loglevel = Normal
  • logpath = .
  • Detail on the media file if it is an issue related to playing a media file (in order to get the necessary information on a particular media file go into the Plex web interface, select the video file, when it brings up the page for the media file click on the "i" information button on the left hand side, it will then bring up a "media info" box, click on the "View XML" button, it will then open a browser window with the relevant information, copy this tohttp://www.pastebin.com and use the pastebin link to post the details; posting the information directly in the forum may mess up the formatting and generally takes up a lot of space):
  • A detailed description of the issue (the clearer you can make this the better): 
  • Ensure you post your 'PlexConnect.log' file to pastebin and post the link ('PlexConnect.log' is located in your PlexConnect folder). If possible, follow these steps to create a "more detailed fresh" one:

Plexconnect.log:

15:24:54 PlexConnect: started: 15:24:54

15:24:54 PlexConnect: Version: 0.4-dev

15:24:54 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)]

15:24:54 PlexConnect: Host OS: darwin

15:24:54 PlexConnect: IP_self: 192.168.0.7

15:24:54 DNSServer: started: 15:24:54

15:24:54 DNSServer: Failed to create socket on UDP port 53: [Errno 48] Address already in use

15:24:54 PlexConnect: DNSServer not alive. Shutting down.

15:24:54 PlexConnect: Shutting down.

15:24:54 PlexConnect: shutdown

15:24:54 PlexConnect: shutdown

 

Last login: Sun Oct 26 15:45:21 on console

macbook-pro:~ gema$ sudo lsof -i :53 | grep LISTEN

Password:

macbook-pro:~ gema$ 

>>sudo lsof -i :53 | grep LISTEN

Where does the "| grep LISTEN" come from? Check the output without that filtering...

Thanks for the reply....was asked for the | grep LISTEN by drewbie 

Will check without that and reply 

I got it from the fist image posted, as that was showing the command and the output. (Not being an apple person I was not sure of the actual command)

Here is the output

You can kill that process to get PlexConnect working but it will respawn, which is a good thing as it is needed for a few critical things.

Any Epson printers on that home network?

The PID you are suggesting to kill is 41 I assume ? Am checking on the EPSON printer question 

Yes, although just realised Python is using it as well.

Try rebooting the machine and running the command again to see if Python still shows up as well (maybe rogue auto starting process in launch daemons that is causing the conflict).

The printer is HP....will ask for the reboot 

Here is what we got after a reboot:
 
macbook-pro:~ gema$ sudo lsof -i :53
COMMAND   PID           USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
mDNSRespo  41 _mdnsresponder   29u  IPv6 0xe8e0da599832d087      0t0  UDP *:domain
mDNSRespo  41 _mdnsresponder   30u  IPv4 0xe8e0da59987f3ce7      0t0  TCP *:domain (LISTEN)
mDNSRespo  41 _mdnsresponder   31u  IPv6 0xe8e0da599686225f      0t0  TCP *:domain (LISTEN)
Python    204           root    4u  IPv4 0xe8e0da599834f517      0t0  UDP macbook-pro:domain
macbook-pro:~ gema$ 

As there is still an instance of Python running without you manually starting PlexConnect i think you need to find out what that is first (maybe a leftover launch daemon plist from trying to install it?).

What files are in /Library/LaunchDaemons on the Macbook?

Last login: Thu Oct 30 09:30:43 on ttys000
macbook-pro:~ gema$ cd /Library/LaunchDaemons
macbook-pro:LaunchDaemons gema$ 
macbook-pro:LaunchDaemons gema$ ls
com.adobe.fpsaud.plist
com.logmein.logmeinblanker.plist
com.logmein.logmeinserver.plist
com.logmein.raupdate.plist
com.microsoft.office.licensing.helper.plist
com.plex.plexconnect.bash.plist
com.trusteer.rooks.rooksd.plist
macbook-pro:LaunchDaemons gema$ 

>>com.plex.plexconnect.bash.plist

You got PlexConnect already installed as "daemon"...

It should as well create a PlexConnect.log. Check that for any remaining issues - or de-install that daemon

sudo launchctl unload /Library/LaunchDaemons/com.plex.plexconnect.bash.plist

and do the manual way

sudo ./PlexConnect.py

Baa - to be sure I understand you suggest to

1. Unload the plist from the LaunchDaemons and then

2. Manually start the Plexconnect.py

and then try again ? Do you want to see the output of lsof -i :53 as well or do you believe that this should fix issues ?

It should fix the particular problem you are seeing and allow us to see if it should be working.

Currently you go to start PlexConnect manually but it fails because you have PlexConnect running already as a daemon, which is hogging port 53, so it shuts down. If you remove this daemon then we can see what is happening and once it is working we get the autostart working so you don't have to touch again unless you want to update it.

...plus mDNSResponder might be related to "internet sharing".

mDNS is certainly Bonjour - are you asking me to take any action there as well ?

mDNS can be triggered by a bunch of things but shouldn't usually hog the port, i asked about the Epsom stuff because it has known bad behaviour relating to mDNS.

Just take action on the PlexConnect plist, start PlexConnect manually and we can see if there are any further errors and where we go from there.