PlexConnect works fine, then randomly stops working & requires system reboot

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/x92iQPCQ
 
A detailed description of the issue (the clearer you can make this the better): PlexConnect is working beautifully, I watch a couple of media files, then I step away for a period of time. I'm not sure how long exactly, but when I try to come back to it, anything I try to load gets a "An error occured loading this content. Try again later." message. Restarting PlexConnect, PMS, and/or the ATV does nothing, only completely restarting the computer PlexConnect and PMS is running on gets it back to working again. Here's the log if I Control+C and restart PlexConnect then try to load some media via ATV: http://pastebin.com/1CqP83Pq
 
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://cl.ly/292K3P0o2U3Z

I too have the same problem. No amount of restarting PlexConnect or the ATV solves the issue. Only a restart of the server that PlexConnect is running on gets it working again.

Annoying because, as above, it works perfectly until I leave it all alone for a while and come back to it the next day.

Will update when I can reproduce with high level debugging on and post logs.

I'm on 0.3.1+ and having this too. Will update to the newest soon

I’m running 10.9.1 with the latest PlexConnect commit with no issues whatsoever. Is this a plexify issue? You can try my openconnect app in my signature.

Plexify won't run on my Mini, so that's neither a problem or a fix.

I don't think wahlman implied that he is using Plexify... actually he is working on some other setup/update scripts.

I don't think wahlman implied that he is using Plexify... actually he is working on some other setup/update scripts.

wahlman asked "Is this a plexify issue?" to which I replied letting him (?) know it isn't. His OS X version is different from mine too, so I'm not sure the "no issues whatsoever" vote is a fair apples to apples comparison. And the plexify alternative that's linked to also doesn't work on my Mini.

And now apparently I can restart my system all I want, PlexConnect doesn't work and just keeps throwing the same errors I shared in the log above :(

Okay, so I restarted the Mini/PMS/PlexConnect and ATV and I can access my media again. When/if it disconnects again, I'll try all the various combos (now including an ATV restart) to see what actually needs to be restarted. While it'd be awesome to not have to restart anything, if I can shave some time off by not having to restart the Mini, that'd be cool :)

You could also try disabling GDM and hard coding the PMS IP, in case GDM auto discovery flakiness is the cause, let us know if that makes a difference.

I'm having the same issue on a Ubunut Server build of plexconnect.  Works great, then out of the blue stops responding.  Its like the DNS server is dying or something.  I have turned the logging up and will begin doing more testing the next time it happens.  Very Strange. 

Setup:

PlexConnect on Ubuntu 12.04 server, Running as a service.

In experimenting with the restart combos, it seems to all be in the ATV. So when it crashes now, I just restart my ATV. While not ideal, it's easier to restart than everything on my Mini. I can live with this, but any ideas as to what might be going on in the ATV to start throwing errors when it accesses PlexConnect/PMS?

I do not have this problem. Almost every week someone is reporting it. I think that one of the reasons why I do not have the problem is because I have a Harmony remote that Powers on/off the ATV + TV + A/V Receiver whenever I need, so in reality the ATV never goes into sleep mode.

PlexConnect and PMS are installed in a NAS. Besides Plex this NAS is being used for other purposes, so it's running 24x7. Therefore PMS and PlexConnect are only restarted very rarely.

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