plexConnect keeps dropping out

So I've been having this issue for a long while now and I can't figure out how to fix it.  What happens is this; I will have plexconnect running and everything working as it should.  Then over the course of a few days everything will stop working.  When it stops all i get is the apple tv spinning icon.  When this happens all of the Apple TV apps stop working.  To fix the issue I have been going into the network option on the apple TV and chaining the DNS from manual to automatic and back again.  This usually allows me to watch media on plex but everything else is still not working.  Only a reset to plexconnect on the server fixes everything but only for a bit.  

 

I have tried many things to fix it, including reinstalling the Apple TV and my server from scratch.  

 

Not sure what I'm missing or doing wrong but any help would be amazing. 

 

Thanks

My guess is its more then likely a network issue or in very rare cases your atv’s ethernet/wifi is going bad.

You are not alone in this issue. It's been happening to me since I started using Plexconnect and I don't believe it's an issue with my home network, as I've switched routers and still have the issue. I've just come to accept it as an annoying quirk, but it does prevent me from enjoying Plexconnect when I don't feel bothered by resetting the DNS.

I can set the DNS on my ATV3 to my Mac mini and it recognizes Plexconnect and sees my library. Then after an arbitrary amount of time and going back to my ATV, loading trailers brings nothing but the constant spinning icon and will never load. If I go back and change the DNS settings to automatic, trailers loads the regular trailers app immediately and the rest of the apps open without a problem. I can then immediately change back to my Mac mini's DNS and trailers will see my Plex library. If I leave my ATV set to automatic I never have any issue and all of the apps connect to their proper channels and open immediately and will do so for weeks and weeks. It's only when I have the ATV DNS set to Plexconnect does this issue arise.

I, too, have this issue. Forum threads come and go, but I haven't seen a solution to the underlying problem.

A couple variables that I *think* are causing the issue:

- ATV connected to network through WiFi.

- ATV falling asleep/turning off after a period of time.

In one of the threads it was suggested that setting the ATV to never sleep will avoid the issue. I might try this.

Currently, when this happens to me, I restart the Apple TV and it fixes the issue. I guess this is similar to what Aaron P suggested (resetting the DNS settings).

Thank you for the replies.  My aTV is connected via ethernet.  Although i have tried wifi to the same outcome.  

I have also set it to never sleep, although who knows what it actually does when the TV is off...

Glad to know its not just me.  Just very strange seeing as I feel like i have changed every variable and its still happening.

Its also odd that it only effects a small percentage of people.  I have a buddy that has the exact same setup as I do but never an issue...

Well the reason why setting DNS to automatic is because it goes straight out of the router. Otherwise you’re redirecting it to your computer with the Python script servers running.


If AppleTV can’t connect to your computer or doesn’t get a response it times out.


I assume that when the trailers app hangs up, that you can’t access any other content either, right? No music, no anything?


I’m not saying this is surely it, but a lot of network cards and wireless cards as well will enter a low power state, even if the computer itself doesn’t go into full sleep mode. It will do it if it is idle for a bit, then it’ll enter an energy saving state and it’ll take some packets hitting it to wake up again. Unfortunately, the DNS request sent was the packet that woke the network card up, but it takes a second or two to wake up and the request is not acknowledged fast enough, leaving the Apple TV hung up. I guess it doesn’t send more requests if the first times out. What if you try to exit trailers a second then go back in? Does it work the second time?


But likewise, if the Plex hangs, no other traffic should work either because the Python script intercepts DNS requests and then forwards those not from com.apple.trailers to an external DNS to resolve snd respond back. Google 8.8.8.8 by default.


This could be avoided if Apple’s network settings on the Apple TV allowed for both a primary and secondary DNS server like almost every other piece of networking equipment that exists does. Most even allow for a tertiary entry.


The other problem is if your computer is not on and/or the PlexConnect DNS server isn’t running you won’t be able to do anything else until you cut the computer on or wake it or you change the DNS in Apple TV settings.


Still, there has to be a way. I’ll think about it. I’m thinking using hosts file entries or DNS relay in the router or even adding something to the routing tables to accomplish this… I have a feeling this can be handled. I can’t think at 3:30am though, I’m about nodding off. I’ll think and try some things tomorrow. No promise I can find a solution, but I’ll try at least…

I had the same issue. Lowering the streaming bitrate within the Plex connect ATV setting menu to 10mpbs solved my issue. 

My Plexconnect is running 24/7 on a 2012 Mac mini server. It never sleeps and the network never sleeps because I have loads of other services running 24/7 utilizing that same network, including services that are uploading from the Mini nearly 24/7. Plexconnect as a service is rarely restarted unless I'm pulling updates from Github or something. My AppleTV is connected to my Airport Extreme and they are about 4 feet away from each other. 

If Trailers times out, it doesn't matter if I go back to the main menu or click back into trailers, it constantly gives you the spinning wheel. The only way to get the service back is to reset the DNS settings or restart the AppleTV. I thought that when trailers timed out I could still use Netflix but I'll have to confirm that next time it happens. Usually when I'm using the ATV and I can't access Plex, I get frustrated because I don't have the patience to wait for a restart/change/rechange DNS settings so I'll just watch something on Netflix before I fall asleep.

I can't see how streaming rate has anything to do with it because my mini is a quad-core i7 and has plenty of transcoding power to do multiple full HD streams at once, and when accessing the trailers menu it's not like it's doing any transcoding just pulling up the library list.

I also  can confirm that when plexconnect stops working so does everything else.  And also that going back out and in again does not fix the issue.  

The other thing of note that I noticed is that some things drop out before everything drops out.  For instance the trailers don't load and all the other apps dont load but I can still access my movies/TV shows in plex.  Then eventually even those stop working until I relaunch plexconnect on the server side, or do the DNS reset.

Lastly I am also running a server off of a 2012 Mac mini, but I am running linux on it and everything in the house is hardwired so no wifi issues.

I had the same issue. Lowering the streaming bitrate within the Plex connect ATV setting menu to 10mpbs solved my issue.


I can't say if this is relevant or not but just of coincidental note, I also have my bandwidth set to 10Mb/s on the streaming max and I have never had the dropout problem described unless my computer goes to sleep or is off, then I fully expect it not to work.

Though, I don't really see any logical connection between bandwidth settings and the responsiveness of DNS/data queries and responses... but hell, why not try anything I suppose if it is really an issue...

My Plexconnect is running 24/7 on a 2012 Mac mini server. It never sleeps and the network never sleeps because I have loads of other services running 24/7 utilizing that same network, including services that are uploading from the Mini nearly 24/7. Plexconnect as a service is rarely restarted unless I'm pulling updates from Github or something. My AppleTV is connected to my Airport Extreme and they are about 4 feet away from each other.

If Trailers times out, it doesn't matter if I go back to the main menu or click back into trailers, it constantly gives you the spinning wheel. The only way to get the service back is to reset the DNS settings or restart the AppleTV. I thought that when trailers timed out I could still use Netflix but I'll have to confirm that next time it happens. Usually when I'm using the ATV and I can't access Plex, I get frustrated because I don't have the patience to wait for a restart/change/rechange DNS settings so I'll just watch something on Netflix before I fall asleep.

I can't see how streaming rate has anything to do with it because my mini is a quad-core i7 and has plenty of transcoding power to do multiple full HD streams at once, and when accessing the trailers menu it's not like it's doing any transcoding just pulling up the library list.


Yeah, I hear you, it's a total PITA when it happens to me. I'm determined to find a workaround, though. Just as soon as I get the chance/motivation to mess with it.

It's also strange and I can't think of anything obvious that would cause this. Maybe the Apple TV is the one to blame? Maybe its network connectivity goes into low power or something, or maybe it has something to do with DNS caching and clearing. Honestly, until I can really troubleshoot it, it's all guesswork.

I also can confirm that when plexconnect stops working so does everything else. And also that going back out and in again does not fix the issue.
The other thing of note that I noticed is that some things drop out before everything drops out. For instance the trailers don't load and all the other apps dont load but I can still access my movies/TV shows in plex. Then eventually even those stop working until I relaunch plexconnect on the server side, or do the DNS reset.

Lastly I am also running a server off of a 2012 Mac mini, but I am running linux on it and everything in the house is hardwired so no wifi issues.

This is odd as well and if it fails like this, then it points to DNS forwarding failing. For what the PlexConnect server calls "higher level" requests, which are more like "external to the LAN" requests.

Have you or anyone happened to study or check the logs or console for errors? The server writes all activity to a log file in the same folder as the Python server script— that could lead to insight.

Can you or anyone check the log file out after this occurs and report any strange things? Just shut the PlexConnect server down on the desktop by using Control-C or whatever it is on Macs (option c?) and then it will write the session log. It clears each time, though, I think... so grab it before restarting.

That might be a good place to start. Unfortunately, I'll be honest and say that I'm not super familiar on a tech level with OS X and how it manages network duties. I am much more familiar with Windows handling of protocols and services, such as DNS caching, routing tables, packet handling, etc. How much difference there is, I can't say, but likely "not a whole lot" and also "probably a little bit", lol.

We'll get to the bottom of it hopefully. I spent several years as a network engineer, so if I can't figure it out after a solid try then I've failed myself. The only thing that could throw me is anything specific to your machines that I am unable to access and look around. Routers, protocol behavior and general networking concepts will apply universally, though.

One roadblock is that since I have not experienced/duplicated the problem, myself, it's going to be a bit tougher just kind of guessing what might be going on with other people's setup without actual physical access to assess any variables and possible problems that I wouldn't see or know otherwise.

Let me ask this... Is there anyone here who has this problem who uses a PC and NOT a Mac? That will help (possibly) to narrow down if it could be something OS specific. Also, have any of you made sure you're running the latest version of the Plex server and the PlexConnect python code (it changes often) and even Python itself? It is on 2.8, I believe. Honestly that last one probably won't make a difference, I'm just saying this is what all I'm running without issue.

As soon as I toy with it, I'll report back. As said, even so, I'm sure there is a workaround that is independent of these softwares, I just have to look at the code of the server and see exactly how things are handled and how I might isolate and differentiate calls to the trailers data and the others. Are the trailers on a unique IP or domain/sub domain? These are all things I don't know off the top of my head. I just installed both Plex and PlexConnect less than a week ago, so I'm hardly a veteran to the software. My only strong point or advantage is my knowledge of networking and programming. So I also want to look at the PlexConnect source code, that will tell me a lot more of what is going on behind the scenes at a technical level.

I am on PC and I DON't have this problem. I leave both machines (Apple TV and PMS machine) up and running and they fall into various states, and never does PlexConnect drop off. 

Can I ask if you have set your PMS to a static IP address?

I am on PC and I DON't have this problem. I leave both machines (Apple TV and PMS machine) up and running and they fall into various states, and never does PlexConnect drop off. 

Can I ask if you have set your PMS to a static IP address?

I don't have the issue and all of my network devices are using static IP's. Just FYI.

Can I ask if you have set your PMS to a static IP address?

PMS and PlexConnect are running on the same machine and it has a static IP (they are always running - no sleep). The AppleTV communicates on the network over WiFi.

After changing my AppleTV to never sleep, I haven't had the issue.

I too have this issue. it started 1-2 weeks ago. I run plexconnect on an UNRAID server. it used to work flawlessly. I'm not sure when this problem started - maybe couple of plex updates ago - I started to notice that I couldn't get access to my Plex library using the trailers app - just constant spinning. I can add to the fact that none of the other network apps work whenever the trailer app stops working - HOWEVER today I haven't been able to access Plex through the trailers app but I can still access all the other apps which is new and weird...

I'm not sure what fixes the issue. i don't have good luck turning off manual dns, or restarting plex connect. the only way I can get things to work again is to restart my unraid server completely, unplug the atv3 completely. this usually fixes the issue but it's a pain. my atv3 is connected via wifi. I'm running the newest atv3 and the newest plexconnect software to date.

I'm on PC and pretty sure I'm having the same issue.

Was happening to me on my Mac and stopped. But on my friend's PC it's just open on launch (Normally, added plexconnect.py to Startup folder and it's running via Python app) and sometime it just decide to get REAL slow (Like frozen) and sometimes it's "Gets released" after a while and turn back to normal but restart needed most times. It's really weird-He has nothing special, no servers or anything like this. It's sure REALLY annoying :)

I'm currently experimenting by making all the settings static ie. dedicated IP addresses for DNS, PMS & Plexconnect (all done by changing items in settings.cfg).  Also set IP on atv to manual dedicated.  So far so good but too early to claim success, I'll give it a week.  BTW: atv is wireless.  Side note: plexconnect seems to respond faster with all IP's set manually vs searching.

My ATV is on a static IP along with my PMS. I tried the ATV setting to not sleep and it didn't make a difference. Eventually trailers just spins and spins and spins and isn't reachable.