Another "Trailers is unavailable. Try again later." Problem

I've read through previous posts here and nothing so far seems to help. Here's the info:

 

Your ATV model (2 or 3) and firmware version (found under the ATV settings > general > about > Apple TV software): ATV 3 6.0.2
 
The DNS server set on the ATV (found under the ATV settings > general > network > DNS): 10.0.1.2
 
The device and operating system (including version number) that PlexConnect is installed on: Macmini1,1 Mac OS X 10.6.8
 
The local IP address of the device that PlexConnect is installed on: 10.0.1.2
 
The device and operating system (including version number) that the Plex media server (PMS) is installed on: Macmini1,1 Mac OS X 10.6.8
 
The Plex media server (PMS) version number you are running (do not put 'latest'): 0.9.8.6
 
The local IP address of the device that the Plex media server (PMS) is installed on: 10.0.1.2
 
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: 0.3.1+ (Master downloaded Jan 4, 2013)
 
The content of your 'Settings.cfg' file (if you do not have this file you are running an old version, please update): http://pastebin.com/2ZRJQHv6
 
A detailed description of the issue (the clearer you can make this the better): I followed all of the install directions here (https://github.com/iBaa/PlexConnect/wiki/Install-Guide-Mac) using the WiFi option, no errors were given at any point of the process. I select Trailers on my ATV, it thinks for a while, then I get "Trailers is unavailable. Try again later." I have unplugged, waited, and re-plugged in my ATV and AirPort Express. I am able to access my PMS both via the iOS app and via the web.
 
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: http://pastebin.com/vjtqVeb7

Throw away settings.cfg, you want to get it working with the generic one first before you tweak it.

As you are running Snow Leopard you need to install Python 2.7.x.

Also update your PMS.

Thanks for taking a look at my problem.

I got rid of settings.cfg, here's the default that's created: http://pastebin.com/H9pMq2w1

I've installed Python 2.7.6.

I can't update PMS, the latest version doesn't work on the Macmini1,1 Mac OS X 10.6.8 setup I have.

Now that I've installed Python 2.7.6 and deleted the modified settings.cfg file I had, I get a permissions error on the new/default settings.cfg when trying to set loglevel to High even though permissions appear to be set correctly, so here's what I'm expecting to be an inadequate log file: http://pastebin.com/uF1QeUJS



Hmm it is still using your older Python version.
You can change the settings.cfg permissions by right clicking it and selecting get info.


Sent from my iPad using Tapatalk

Any suggestions on how I get it to run the new/current version of Python?

Here are my settings.cfg permissions:

As you can see, everyone has Read & Write access.

When I try to change loglevel to High, I get this:

Voila_Capture108.png

click the little lock in the right corner to unlock it, then u just change the permissions 

add wich ever user u want

I already did that, that’s why Everyone now has read & write privileges.

try duplicate the file and change the copy.. then delete the orginal .. usually works

Is the finder displayed "permissions" the same as the underlying UNIX/BSD/whatever permissions?

Open terminal, cd to your PlexConnect directory, try "ls -all Settings.cfg". The first couple of letters (-rw-r--r--) indicate the latter... Read/Write/Execute permissions deepening on the user, Owner/Group/All.

try duplicate the file and change the copy.. then delete the orginal .. usually works

Okay, this worked. Sorry I was MIA, updating Python broke Sick Beard and I just got that all fixed. Now here's my log (definitely not working now): http://pastebin.com/wXAkVVfg

You have a DNS server already running or you did not properly shut down PlexConnect down previously and the DNS part of it is still running.
Reboot your machine if the latter.
If the former you can disable the PlexConnect DNS part and use your own for trailers.apple.com.

Okay, apparently I'm a little slow with all of this. Thanks for all of the help and sorry for being such a noob.

I rebooted my machine, no luck. I changed settings.cfg to read "enable_dnsserver = False", no luck. Here's the super short log: http://pastebin.com/szEUKn6Q

And is a running DNS server something typical of upgrading Python and adding Cheetah to get it working with Sick Beard? Those are the changes I've made and I wasn't getting a DNS issue with the old version of Python, just PlexConnect not working.

>> 12:57:58 WebServer: Failed to connect to HTTP on 10.0.1.2 port 80: [Errno 13] Permission denied

Hm. You didn't "sudo", did you?

Also, you definitely need a DNS running somewhere...

Nope, didn't sudo, that's better. But now (probably due to the python update) I can't even access my PMS from iOS or Web. New PlexConnect log: http://pastebin.com/2UzVwyb3

I really hope I can get this working, otherwise it's going to be a lot of pain for nada :(

Again... you need a PMS DNS running. If you don't have one setup already, re-enable the one shipped with PlexConnect.

PMS is running, but since the Python/Cheetah update, it's not seeing any media on my Mac Mini. When I try to add a channel (since they suddenly went missing) and browse to my media folder, the browse part doesn't show any files or directories or anything on my computer. I have made no changes to my PMS configuration, just Python, Cheetah, and PlexConnect.

Sorry. Replace PMS with DNS... my bad.

Okay, cool. So now ATV sees PlexConnect. But PMS doesn't see my computer somehow. And I keep getting "Connection to Mac Mini closed". Everything was working fine until the python/cheetah update, any suggestions on where to start troubleshooting that problem? I've restarted both PMS and the computer several times with no luck.

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