Trailers is unavailable. Try again later.

Dev Community Apps & Creations
1

Hello,

 

i still get the "Trailers is unavailable. Try again later." message on Apple TV (3) although the log looks fine to me. See here: http://pastebin.com/YEm5nGZW

My Apple TV 3 Firmware is 5.2.1

PMS runs on my Mac Mini. IP Address: 192.168.1.2

PlexConnect also runs on the Mac Mini.

Mac Mini has OSX Mountain Lion.

Media is stored on external harddrive.

PlexConnect Version (most recent one: 13.06.2013 23:44)

DNS is set to 192.168.1.1

Settings.cfg looks like this: http://pastebin.com/GmVKrmAU

 

 

So all the other channels (Youtube, etc.) work fine over the DNS, but when i launch the Trailers app, it just shows "Trailers is unavailable. Try again later.". I never saw the plex menu, although the log correctly says "***intercept request". Any ideas?

2

The DNS server setting on your ATV is set to 192.168.1.2 right?

3

Yes it is. Otherwise the trailer-app would work normally.

4

>> I never saw the plex menu, although the log correctly says "***intercept request". Any ideas?

According to your logs, WebServer isn't triggered.

Firewall? Port changes?

5

Firewall is active but it is on "allow incoming connection" for Plex, Plex DLNA Server and Plex Media Server. No port changes.

6

Firewall: what about PlexConnect/Python?

7

I turned the firewall off and it still has the same problem.

8

I have the same problem.

I have two apple tv. The first one is working great (IOS 5.2)

The second one is running IOS 5.0.2, same error.

I have attached two screenshots of my ATVs. I don't know if it's related but you can see that the home screen isn't the same on both devices .

both are jailbroken. 

9

>> I have the same problem.

No, it's not the same problem - at least as far as I can understand. Alex1399 isn't getting any Plex content - or is he? You are set up and browsing your library...

5.0.2 doesn't support the NavBar in trailers app. Therefor you get that ugly, but fully functional fall back. It is not an error... it's a feature.

By the way... how is PlexConnect handling those two aTV in parallel? Any issues?

10

Baa,

ok I read Alex1399's post again. It seems he gets this message as soon as he start 'trailers'.

I get the exact same message but it's when I start a movie. I can get into the application, I can browse, etc...

So I can't really answer you right now with the ATV in parallel...I'll need to get this working.

11

I can make a video if you want

12

dentifrice:

Which version of PlexConnect? The latest? Check this... http://forums.plexapp.com/index.php/topic/70195-getting-an-error-when-accessing-the-pre-play-screen-read-this/

13

ok let me verify this and download latest version

14

I update PMS and Plexconnect and now it works !

I'll try to use both ATV to see how it goes

15

It seems to work great with both at the same time !

16

For me the problem still exisists DIRECTLY after launching the trailers app it gets the error message. PMS and Plexconnect are up-to-date.

17

On your PlexConnect-machine:

1) Open Safari and point it to the PMS_Addr - in your case 192.168.1.2:32400. Does PMS return an XML? Well, why wouldn't it...

2) in settings.cfg set loglevel to High. Rerun. Post "PlexConnect.log" again.

18

XML gets returned. High level log: http://pastebin.com/dEjuuRPi

* i just updated the log since i did not capture everything the first time *

19

Log looks perfect to me.

Do you have a second computer to help in debugging? From there use a Browser and try to request a PlexConnect page: "http://192.168.1.2" should actually do the trick. Since it won't be an aTV, I would expect a 403, "Not Serving Client <..>" message.

20

I almost thought it would work now, cause when i followed your instructions i figured out, that a pow-server (for ruby-on-rails-development) was running on port 80, so when i visit (192.168.1.2) from a different computer (or just try "localhost" on the current one) POW responded. Unfortunately after shutting down POW the problem still exist...

*Update:*

I found something interesting in the POW documentation:

"The firewall rule installed by Pow redirects all incoming traffic on port 80 to port 20559, where Pow runs. This means if you have another web server running on port 80, like the Apache that comes with Mac OS X, it will be inaccessible without either disabling the firewall rule or updating that server's configuration to listen on another port."

So i somehow have to find where to change this firewall rule.