"Trailers Unavailable" everything else works

Dev Community Apps & Creations
1

Ok, this stopped a week or so ago.

 

I have reset the apple TV, updated to 6.0, restarted my imac, removed and readded plex.

Banging my head here.

 

Plex version Version 0.9.8.6.175-88ffbb2

I started to have issues when I installed 10.8.5.But none of apple's fixes should interfere. 

 

terminal file

Jasons-iMac:PlexConnect jason$ sudo ./PlexConnect.py
20:53:16 PlexConnect: ***
20:53:16 PlexConnect: PlexConnect
20:53:16 PlexConnect: Press CTRL-C to shut down.
20:53:16 PlexConnect: ***
20:53:16 PlexConnect: started: 20:53:16
20:53:16 PlexConnect: IP_self: 192.168.0.15
20:53:16 DNSServer: started: 20:53:16
20:53:16 DNSServer: ***
20:53:16 DNSServer: DNSServer: Serving DNS on port 53.
20:53:16 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.0.15
20:53:16 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
20:53:16 DNSServer: forward other to higher level DNS: 8.8.8.8
20:53:16 DNSServer: ***
20:53:16 WebServer: started: 20:53:16
20:53:16 WebServer: started: 20:53:16
20:53:16 WebServer: ***
20:53:16 WebServer: ***
20:53:16 WebServer: WebServer: Serving HTTP on 0.0.0.0 port 80.
20:53:16 WebServer: ***
20:53:16 WebServer: WebServer: Serving HTTPS on 0.0.0.0 port 443.
20:53:16 WebServer: ***
20:53:16 PlexGDM: ***
20:53:16 PlexGDM: looking up Plex Media Server
20:53:16 PlexGDM: ***
20:53:17 PlexGDM: servers discovered: 1
20:53:17 XMLConverter: PlexGDM - PMS: 192.168.0.15:32400
20:54:20 DNSServer: DNS request received!
 

 

Log file.

20:53:16 PlexConnect: started: 20:53:16
20:53:16 Settings: getsetting enable_plexconnect_autodetect=True
20:53:16 PlexConnect: IP_self: 192.168.0.15
20:53:16 Settings: getsetting enable_dnsserver=True
20:53:16 DNSServer: started: 20:53:16
20:53:16 Settings: getsetting port_dnsserver=53
20:53:16 Settings: getsetting ip_dnsmaster=8.8.8.8
20:53:16 Settings: getsetting prevent_atv_update=True
20:53:16 DNSServer: ***
20:53:16 DNSServer: DNSServer: Serving DNS on port 53.
20:53:16 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.0.15
20:53:16 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
20:53:16 DNSServer: forward other to higher level DNS: 8.8.8.8
20:53:16 DNSServer: ***
20:53:16 WebServer: started: 20:53:16
20:53:16 Settings: getsetting ip_webserver=0.0.0.0
20:53:16 Settings: getsetting port_webserver=80
20:53:16 Settings: getsetting enable_webserver_ssl=True
20:53:16 WebServer: started: 20:53:16
20:53:16 Settings: getsetting ip_webserver=0.0.0.0
20:53:16 Settings: getsetting port_webserver=80
20:53:16 Settings: getsetting port_ssl=443
20:53:16 Settings: getsetting certfile=./assets/certificates/trailers.pem
20:53:16 Settings: getsetting certfile=./assets/certificates/trailers.pem
20:53:16 WebServer: ***
20:53:16 WebServer: ***
20:53:16 WebServer: WebServer: Serving HTTP on 0.0.0.0 port 80.
20:53:16 WebServer: ***
20:53:16 WebServer: WebServer: Serving HTTPS on 0.0.0.0 port 443.
20:53:16 ATVSettings: init class CATVSettings
20:53:16 WebServer: ***
20:53:16 ATVSettings: load settings
20:53:16 Settings: getsetting enable_plexgdm=True
20:53:16 PlexGDM: ***
20:53:16 PlexGDM: looking up Plex Media Server
20:53:16 PlexGDM: ***
20:53:16 PlexGDM: Sending discovery message: M-SEARCH * HTTP/1.0
20:53:16 PlexGDM: Received data from ('192.168.0.15', 32414)
20:53:16 PlexGDM: Data received:
 HTTP/1.0 200 OK
Content-Type: plex/media-server
Resource-Identifier: b80ce4518df58bc93527049e31b3bc703d4e326d
Name: Jason Plex Server
Port: 32400
Updated-At: 1379815410
Version: 0.9.8.6.175-88ffbb2
 
 
20:53:17 PlexGDM: servers discovered: 1
20:53:17 PlexGDM: Jason Plex Server 192.168.0.15:32400
20:53:17 XMLConverter: PlexGDM - PMS: 192.168.0.15:32400
20:53:17 ATVSettings: setOption: update pms_uuid to ('b80ce4518df58bc93527049e31b3bc703d4e326d',)
20:54:20 DNSServer: DNS request received!
20:54:20 DNSServer: Source: ('192.168.0.18', 56628)
20:54:20 DNSServer: Domain: 12-courier.push.apple.com
20:54:20 DNSServer: ***forward request
20:54:20 DNSServer: -> DNS response from higher level
20:54:21 DNSServer: DNS request received!
20:54:21 DNSServer: Source: ('192.168.0.18', 56628)
20:54:21 DNSServer: Domain: 12-courier.push.apple.com
20:54:21 DNSServer: ***forward request
20:54:21 DNSServer: -> DNS response from higher level
20:54:24 DNSServer: DNS request received!
20:54:24 DNSServer: Source: ('192.168.0.18', 56628)
20:54:24 DNSServer: Domain: 12-courier.push.apple.com
20:54:24 DNSServer: ***forward request
20:54:24 DNSServer: -> DNS response from higher level
20:54:33 DNSServer: DNS request received!
20:54:33 DNSServer: Source: ('192.168.0.18', 56628)
20:54:33 DNSServer: Domain: 12-courier.push.apple.com
20:54:33 DNSServer: ***forward request
20:54:33 DNSServer: -> DNS response from higher level
21:04:05 DNSServer: DNS request received!
21:04:05 DNSServer: Source: ('192.168.0.18', 49427)
21:04:05 DNSServer: Domain: 40.courier-push-apple.com.akadns.net
21:04:05 DNSServer: ***forward request
21:04:05 DNSServer: -> DNS response from higher level
21:19:15 DNSServer: DNS request received!
21:19:15 DNSServer: Source: ('192.168.0.18', 54162)
21:19:15 DNSServer: Domain: 38-courier.push.apple.com
21:19:15 DNSServer: ***forward request
21:19:17 DNSServer: -> DNS response from higher level
21:19:17 DNSServer: DNS request received!
21:19:17 DNSServer: Source: ('192.168.0.18', 54162)
21:19:17 DNSServer: Domain: 38-courier.push.apple.com
21:19:17 DNSServer: ***forward request
21:19:17 DNSServer: -> DNS response from higher level
21:31:50 DNSServer: DNS request received!
21:31:50 DNSServer: Source: ('192.168.0.18', 60468)
21:31:50 DNSServer: Domain: 18-courier.push.apple.com
21:31:50 DNSServer: ***forward request
21:31:50 DNSServer: -> DNS response from higher level
21:42:05 DNSServer: DNS request received!
21:42:05 DNSServer: Source: ('192.168.0.18', 51073)
21:42:05 DNSServer: Domain: 21.courier-push-apple.com.akadns.net
21:42:05 DNSServer: ***forward request
21:42:06 DNSServer: -> DNS response from higher level
21:52:21 DNSServer: DNS request received!
21:52:21 DNSServer: Source: ('192.168.0.18', 56955)
21:52:21 DNSServer: Domain: 25-courier.push.apple.com
21:52:21 DNSServer: ***forward request
21:52:21 DNSServer: -> DNS response from higher level
22:02:36 DNSServer: DNS request received!
22:02:36 DNSServer: Source: ('192.168.0.18', 63322)
22:02:36 DNSServer: Domain: 31-courier.push.apple.com
22:02:36 DNSServer: ***forward request
22:02:36 DNSServer: -> DNS response from higher level
22:12:51 DNSServer: DNS request received!
22:12:51 DNSServer: Source: ('192.168.0.18', 51041)
22:12:51 DNSServer: Domain: 23.courier-push-apple.com.akadns.net
22:12:51 DNSServer: ***forward request
22:12:51 DNSServer: -> DNS response from higher level
22:23:05 DNSServer: DNS request received!
22:23:05 DNSServer: Source: ('192.168.0.18', 60569)
22:23:05 DNSServer: Domain: 16-courier.push.apple.com
22:23:05 DNSServer: ***forward request
22:23:05 DNSServer: -> DNS response from higher level
22:33:20 DNSServer: DNS request received!
22:33:20 DNSServer: Source: ('192.168.0.18', 62289)
22:33:20 DNSServer: Domain: 28.courier-push-apple.com.akadns.net
22:33:20 DNSServer: ***forward request
22:33:20 DNSServer: -> DNS response from higher level
22:43:35 DNSServer: DNS request received!
22:43:35 DNSServer: Source: ('192.168.0.18', 55943)
22:43:35 DNSServer: Domain: 33-courier.push.apple.com
22:43:35 DNSServer: ***forward request
22:43:35 DNSServer: -> DNS response from higher level
22:53:50 DNSServer: DNS request received!
22:53:50 DNSServer: Source: ('192.168.0.18', 52197)
22:53:50 DNSServer: Domain: 14.courier-push-apple.com.akadns.net
22:53:50 DNSServer: ***forward request
22:53:50 DNSServer: -> DNS response from higher level
23:04:05 DNSServer: DNS request received!
23:04:05 DNSServer: Source: ('192.168.0.18', 51487)
23:04:05 DNSServer: Domain: 29-courier.push.apple.com
23:04:05 DNSServer: ***forward request
23:04:05 DNSServer: -> DNS response from higher level
23:14:20 DNSServer: DNS request received!
23:14:20 DNSServer: Source: ('192.168.0.18', 62261)
23:14:20 DNSServer: Domain: 42.courier-push-apple.com.akadns.net
23:14:20 DNSServer: ***forward request
23:14:20 DNSServer: -> DNS response from higher level
23:24:35 DNSServer: DNS request received!
23:24:35 DNSServer: Source: ('192.168.0.18', 61865)
 
 
What am I missing here?
2

Here is my settings.cfg

[PlexConnect]
logpath = .
enable_dnsserver = True
ip_webserver = 0.0.0.0
prevent_atv_update = True
port_dnsserver = 53
enable_plexconnect_autodetect = True
port_pms = 32400
port_webserver = 80
ip_plexconnect = 0.0.0.0
certfile = ./assets/certificates/trailers.pem
ip_dnsmaster = 8.8.8.8
loglevel = High
ip_pms = 192.168.178.10
enable_plexgdm = True
port_ssl = 443
enable_webserver_ssl = True
3

Start over use my updated guide in my signature first link. Remove any unused items in /library/launchdaemons or /library/launchagents not in my new guide. Download new pms and plexconnect, delete old ones entirely. Also links in my first post were recently updated as well reinstall certs etc. Im on 10.8.5 using (2) atv 720p’s on ios 5.2. I doubt your issue is with your ios or osx versions. I was using a lot of bad info to start with. Troubleshoot then post results by ruling things out. I fixed a few atv3’s on ios 6 this way. Looks like plexconnect isnt intercepting your requests from your atv properly. Hope this helps you. My working plexconnect looks like this which leads me to believe its a cert issue:

4

ok, so nothing wrong in the log files?

I will give this a go, should have time tomorrow night.

Thanks

5

The forward requests going to apple is your issue, those should be intercept requests going to your pms. Fresh start should get you going again.

6

I disagree the forward requests all look normal, they are the non trailers.apple requests. What I don’t see is any trailers.apple intercept did you visit the trailers app during this part of the log?

7

Strange I had a guy with a very similar log that I fixed where his requests were being forwarded instead of being intercepted. Ended up being a simple router reset and changing his ip to automatic but both were running ios 6, and both are unable to connect post #25 because from what I can tell his atv ip is 192.168.0.18 but its forwarding to apple not intercepting and redirecting to his pms which leads me to belive the trailers app on his atv is still going to apple:
http://forums.plexapp.com/index.php/topic/81604-can-this-work-via-ethernet/page-2

And here post #27 cert issues:
http://forums.plexapp.com/index.php/topic/81449-trailers-not-available-try-again-later-imac/page-2#entry469252

Curious drewbie how does plexconnect.py look when you run it from terminal?

Also I dont know if this is any headway but a simple google search shows that these may in fact be genuine apple requests by an unrealated app facetime where in his case its the atv trailers app of course:
https://discussions.apple.com/thread/2621383?start=0&tstart=0

So is his appletv phoning home to apple?

8

That is correct the ATV makes a lot of calls back to apple, trailers.apple are intercepted, update calls as well if you has that Turned on, but all other calls are forwarded, and I see loads of them even when the ATV is not in use, exactly like is being shown in the log, which is why I disagreed with your statement, because to me it looks like it is working and taking the calls from the ATV, but again I don’t see the trailers app being used/intercepted.


And this is what is confusing me because even if the certificate is not installed currently on the atv(or does not match the .pem loaded by plexconnect (as the logs show that was doyen on)) the. I still expect to see a intercept.

9

I disagree the forward requests all look normal, they are the non trailers.apple requests. What I don't see is any trailers.apple intercept did you visit the trailers app during this part of the log?

I did a few times testing it, searched the log file, this is all that came up

20:53:16 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.0.15
13:20:26 DNSServer: Domain: trailers.apple.com
16:00:44 DNSServer: Domain: trailers.apple.com
17:47:51 DNSServer: Domain: trailers.apple.com
18:33:29 DNSServer: Domain: trailers.apple.com
19:16:12 DNSServer: Domain: trailers.apple.com
20:51:31 DNSServer: Domain: trailers.apple.com
20:53:22 DNSServer: Domain: trailers.apple.com
10

@ drewbie, ah good to know, thought it was all intercepted.


@ jason start over its your best bet. I know it sucks but trying to debug is usually harder trust me.

11

Should i see this more in the log?

20:53:16 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.0.15

12

I usually do but my log was a screen shot just initially using sudo ./plexconnect.py

13

@ drewbie, ah good to know, thought it was all intercepted.

@ jason start over its your best bet. I know it sucks but trying to debug is usually harder trust me.

ok. 

Makes sense.  As a computer tech I have a NEED to fix things, but your advice is solid.

14

You will get there, my 1st link in my signature is a win win, took a lot of tries and fails to get it straight, im sure being tech savvy you will get it. I pulled my hair out for weeks to get a thorough guide for osx but it works usually everytime for everyone plus its up to date to 10.8.5. Not knocking anyone elses, I just expanded what I got from ibaa and other sites and tried to simplify it for everyone and added my own little tricks I found on the way.

15

Should i see this more in the log?

20:53:16 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.0.15

No, just once during startup.

16

Could it be an IP address conflict… I had something like this and realized that my aTVs we’re sharing the same ip therefore unable to get pass through “accessing trailers”…is your router dchp enabled?

17

Could it be an IP address conflict.. I had something like this and realized that my aTVs we're sharing the same ip therefore unable to get pass through "accessing trailers"..is your router dchp enabled?

Yes, if I check my router, every device has a different ip

18

I could change the starting IP to after my static IP for my server, this could solve a potential ip conflict. Ill try this.

19

Any luck?

20

Ya the IP thing didn't help, no time to redo the entire setup, was out of town all weekend.