After setting up everything and attempting to bask in the glory of PlexConnect....the Trailers app on my ATV errors out with "Trailers is unavailable. Try again later"
What did I do to set it up? Glad you asked! (based on instructions from https://github.com/iBaa/PlexConnect/wiki/Install-Guide-Linux):
- Extract plexconnect on my media server (an ubuntu 10.04LTS machine)
- Generate the SSL certificates (using OpenSSL on the media server) and move the .pem and .cer files into the certificates folder in Plexconnect. I skipped the "install the certificates to AppleTV via USB (optional)".
- Ran Plexconnect.py and everything seems good.
- Launch Trailers app and it eventually times out, showing the above mentioned error message.
Here's the console output (nothing else happens until I use Control-C to shutdown PlexConnect):
Here's some more details for ya:
-
Your ATV model (2 or 3) and firmware version (found under the ATV settings > general > about > Apple TV software):
-
Model MD199C/A Firmware ver. 6.0.1 (6646.80.1)
-
-
The DNS server set on the ATV (found under the ATV settings > general > network > DNS):
-
192.168.0.111
-
-
The local IP address of the device that PlexConnect is installed on:
-
192.168.0.111
-
-
The device and operating system (including version number) that PlexConnect is installed on:
-
Ubuntu Linux 10.04.2
-
-
The device and operating system (including version number) that the Plex media server (PMS) is installed on:
-
Ubuntu Linux 10.04.2 (same as Plexconnect)
-
-
The Plex media server (PMS) version number you are running (do not put 'latest'):
-
Version 0.9.8.18
-
-
The local IP address of the device that the Plex media server (PMS) is installed on:
-
192.168.0.111
-
-
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.
- PlexConnect: Version: 0.3.1+
- Python: 2.6.5 (r265:79063, Sep 26 2013, 18:51:09)
-
The contents of your 'Settings.cfg' file
-
**during troubleshooting I noticed that ip_pms had been autofilled with an ip I didn't recognize. Thus, I commented it out and provided the correct ip address.**
-