Issues with ATV3 , no trailers

Dev Community Apps & Creations
1
 

  • Your ATV model (2 or 3) and firmware version (found under the ATV settings > general > about > Apple TV software): ATV3, version 5.3

  • The DNS server set on the ATV (found under the ATV settings > general > network > DNS): Have tried both:  192.168.1.109, and 192.168.1.133 , tried plexconnect on 2 PC's

  • The device and operating system (including version number) that PlexConnect is installed on:  
    1) Home server, SR-2 mobo, Xubuntu 12.04 base, latest PlexConnect pulled straight from git last night, python 2.7.3.  This one is 192.168.1.109
    2) Desktop, i7-3770k, Windows 8 x64, python 2.7 installed today, along with latest plexconnect.  This one is 192.168.1.133

  • The local IP address of the device that PlexConnect is installed on: 192.168.1.109, or 192.168.1.133

  • The device and operating system (including version number) that the Plex media server (PMS) is installed on:  
    Same as above for plex connect, have two PMS running

  • The Plex media server (PMS) version number you are running (**do not put 'latest'**):
    Server - 0.9.7.28
    Desktop - 0.9.8.5

  • The local IP address of the device that the Plex media server (PMS) is installed on:
    192.168.1.109, 192.168.1.133 

  • 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 testing branch e.g. the Elan/PlexInc one.
    Both have the latest, Server's was downloaded at around 11PM EST on 09-21-13, desktops at 3PM EST on 09-22-13

  • The content of your 'Settings.cfg' file (if you do not have this file you are running an old version, please update)
    Config is the same for both windows and Ubuntu hosts, just the .pem path is changed for the correct location, the pastebin is for the ubuntu host (the one i'd prefer to use)
    http://pastebin.com/MHdG56Pe

  • Detail on the media file if it is an issue related to playing a media file 
    Cannot access trailers

  • A detailed description of the issue (the clearer you can make this the better):
    I am attempting to access trailers, however I keep getting the no trailers issue.  Unlike most issues reported here, the webserver is up and going, however I am receiving the following issue in the plex window:

    14:34:41 DNSServer: DNS request received!
14:34:41 DNSServer: Source: ('192.168.1.205', 63679)
14:34:41 DNSServer: Domain: trailers.apple.com
14:34:41 DNSServer: ***intercept request
14:34:41 DNSServer: -> DNS response: 192.168.1.109


    When looking to access:  192.168.1.109:80, I receiver an access error, but there is a page, however :443 is not working.

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:
Log file should be here:http://pastebin.com/F3dCxH6f

2

It's confusing with the 2 server issues...

settings.cfg from the linux one?

>> certfile = /home/spencer/Desktop/PlexConnect/assets/certificatestrailers.pem

You are missing a '/'.

Logfile from Windows?

Only DNS requests, nothing for WebServer - Win seems to have this often... Firewall?

3

Firewall yes, however all opened to plex and python.  

Missing a '/' where?  That settings.cfg I included is from linux.

And ya, the two server issue is a bit confusing, have the one on windows as a temp thing as a holding place for files while I clean it up.  And as a test to find stuff.. Would disabling/shutting down the one on windows help some? (Same issue was present prior to having plex on windows.)

Windows log file -  http://pastebin.com/HkXneE9Z

Also, issue is present if the ATV is on wireless, or wired.

4

>> >> certfile = /home/spencer/Desktop/PlexConnect/assets/certificatestrailers.pem

>>Missing a '/' where?  That settings.cfg I included is from linux.

Between the 's' and the 't'...

5

Ahh, nice catch, dont know how I didnt see that.  Let me see if that fixes it. 

Edit; Appologies, I had copied an old file that was giving me issues, not the current one in use which is this one:

http://pastebin.com/fbTrad1J

6

To add, the same issue is around if there is only one plex server running on the network, or more.  

Anything else to test or look at ?  Googling still doesnt show me any one with a similar issue.

7

Just verifying, because I don't know your setup, but does your server (.109) have more than one IP address?

From what I was reading in the settings file, you have PMS on 192.168.178.10, and set plexconnect to 0.0.0.0, which is the same IP address as the machine as it's installed on. 

If that's the case, then you need to change the IP addresses for PMS, PlexConnect, and the Webserver to 192.168.178.109, in order for those all to connect to the ATV.

In my setup, PMS, PlexConnect, and the Webserver are all on 10.0.1.10, with the ATV DNS redirecting to 10.0.1.10.

I would check the IP address settings and force them to connect, instead of using auto or dynamic.

8

The .109 is a DHCP set for the machine, that is the only IP for that machine.  I did not catch that, ill swap that in the settings file and see what happens. 

Thanks.

9

He has Plexgdm functioning so it is selecting the necessary IP address automatically. Unless, it is selecting the wrong address this does not need to be changed.

10

Can we try to concentrate on one machine first?

(rolling the dice...) - let's talk about the Linux one... :-)

With PlexConnect running, we have seen that the DNS requests get through and are answered...

What happens if you try to fake the aTV http/https requests from your second machine - what do you get back when pointing your browser to :80 and/or :443?

11

443 gives page not found, 80 give me the following text on the page:

Error response

Error code 403.

Message: Not Serving Client 192.168.1.133.

Error code explanation: 403 = Request forbidden -- authorization will not help.

 

This is when visiting:  192.168.1.109:80 , or :443, which is the linux machine.

12

The shown response for port 80 looks fine - PlexConnect only ships data to aTV devices.

From my point of understanding, the same should happen for :443, maybe first triggering a certificate warning.

For some reason  port 443 seems to not work correctly. I guess I repeat myself here - is it already used for other applications?

13

I do not believe so, It shouldnt, and actually two days ago I received the same warning, not sure why I am not currently, going to look and see if I can find something using 443 as well now (no other software changes with the exception of PlexConnect have been done to the machine)

14

Ran netstat to find out, and python is the only thing using 443:

the following is the output for port 443.

tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      27867/python    

15

Does your router block https? Do you need a forwarding rule for :443?

16

I dont believe so, ill poke around in the routers settings after class today, that never popped into my mind.

17

Unable to tell, but I went ahead and opened up 443 to the machine to make sure, still not functioning, same output in PlexConnect as above for the trailers app.

18

You should not have to mess with any files on any os besides adding trailers.pem to the correct folder in plexconnect. When you want to go from windows to linux just point your dns on the atv to the correct machine’s ip and you should be good to go. If all else fails start over delete all files and programs and install a fresh copy of plexconnect & plex media server, generate new certs install them to your os and atv again and see what happens. 9x out of 10 its something you may have missed. The time you spend trying to debug you can just reinstall and get it working faster usually. The only reason you should have to change files within plexconnect typically is if you are using a nas device.

19

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