What is "pil" ? I'm getting the "Trailers Unavailable" message and the Plex log file says
PIL/pillow is a python library for picture processing. If available it might be used to preprocess PMS fanart for aTV.
So I can assume that not having PIL installed would not cause the "trailers not available" error.
In the forums I also saw some references to 'sudo' or something like that. Is that a required part of the installation?
Pil is not required for plexconnect to function, only for the extra preplay fanart screens. It would not cause the error you are facing.
Sudo is used to run PlexConnect on Unix/Linux/FreeBSD platforms. It gives super user privileges so Plexconnect can be ran as root user for example:
sudo PlexConnect.py
So I can assume that not having PIL installed would not cause the "trailers not available" error.
In the forums I also saw some references to 'sudo' or something like that. Is that a required part of the installation?
If you need help please post the requested info. "Trailers not available" can have numerous causes, the most frequent being certs not correctly generated, or not correctly loaded in the ATV.
Still getting the "Trailers not available", so here is the requested info:
ATV model: ATV3
firmware: 7.1(7003)
DNS on ATV: 192.168.1.2
IP of PlexConnect: 192.168.1.5
PlexConnect and Plex Media Server installed on: Dell Experion, Windows 7 professional 64 bit
PMS version: 0.9.11.16.958-80f1748
local IP address on server: 192.168.1.5
PlexConnect version: created 1/2/2015
settings.cfg file:
[PlexConnect]
Your aTV's DNS is set to the wrong address:-
DNS on ATV: 192.168.1.2IP of PlexConnect: 192.168.1.5
Set the aTV's Dns to the same as your PlexConnect machine, in your case 192.168.1.5
My apologies. I did have the DNS set to to 192.168.1.5. It is the ATV IP address that is at 192.168.0.2. I was copying this down late at night.
All other info looks correct.
192.168.0.2? Did you mean 192.168.1.2 because the other would be in a different network subnet.
Crap, it's still late. Yes, it's 192.168.1.2
OK, one more try. This time I hope with the correct information.
ATV model: ATV3
firmware: 7.1(7003)
ATV IP address 192.168.1.2
DNS on ATV: 192.168.1.5
IP of PlexConnect: 192.168.1.5
PlexConnect and Plex Media Server installed on: Dell Experion, Windows 7 professional 64 bit
PMS version: 0.9.11.16.958-80f1748
local IP address on server: 192.168.1.5
PlexConnect version: created 1/2/2015
settings.cfg file:
[PlexConnect]
Is correct then that the ATV IP address should be left at automatic, and the ATV DNS should be changed manually to the IPself address from PlexConnect?
>>the ATV DNS should be changed manually to the IPself address from PlexConnect?
Yes.
>>(your log from previous post)
>>22:59:04 WebServer: http request path: /currentsetting.htm
Who/or what is requesting "currentsetting.htm"?
Sorry, I have no idea what all that means.
Attached is a shorter log. I started PlexConnect.py, changed the ATV DNS to 192.168.1.5, started Trailers, got the "Trailers is unavailable" message, shut down PlexConnect to create log.
Certificates?
Firewall rules?
There shouldn't be any cert or firewall issues. I tried this before several weeks ago and Trailers successfully redirected to Plex. However there was a transcoding issue playing FLAC files, so it didn't work.
There has been a PMS update, so i thought I would try again. Now I just get the "Trailers unavailable" message.
I can see the request for trailers, but maybe the loglevel is not high as not actual processing is occurring. Which is why I was thinking certificate or firewall rules (as the settings.cfg above shows it was high
At this point, all I can think of is to re-create the certificates again, and try the whole process over.
What would I need to change in the Windows firewall?
Python needs to be able to connect over 80, 443 and 53