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.