Server Version#: 1.19.4.2902 (Ubuntu)
Player Version#: iOS 4.4.1
I know that this is an old version of the iOS app but I have it running on 2 or 3 iPhone 5’s just to cast to TVs and Chromecasts. I am not looking for a dev to fix the app but I am hoping that someone else has had this issue and can help me fix or at least understand what happened.
As of Tuesday night all of these devices worked fine. I made no changes to the devices. I made no changes to the server (no updates to Ubuntu or to the PMS software). I have been running PMS 1.19.4.2902 no the server since some time in June. Suddenly last night we wanted to listen to some music on one of the iPhones and the server wouldn’t load. It was dinner time so I didn’t worry about it. Later I wanted to watch a movie so I grabbed a different iPhone–it would connect to the TV’s Chromecast but the library wouldn’t load. I closed and restarted the Plex app several, several times. No go. I rebooted the iPhone twice. No go. I made it ‘foget’ and reconnect to the WIFI twice. No go. I restarted the service twice and rebooted the server twice. No go. I went and got my actual iPhone (the one I use all the time)–and it connected to Plex just fine. The ones on 4.4.1 show the server as offline but my other iPhone and web clients on my 5 macs and Ubuntu box can connect to the server.
What happened between Tuesday night (when they worked fine on 4.4.1 and Wednesday night (last night–when the ones running 4.4.1 stopped working)?
Is there any way to get them working again? They were more reliable than my actual phone with the Chromecasts (and were working up until the day before yesterday)…
Thanks!
Edit: I just tried on an iPad running 3.5.3 and it works…just none of the devices running 4.4.1 
Edit 2: I installed PMS on one of my MacBooks and the iPhones running 4.4.1 can SEE it…but not my real PMS running on Ubuntu that everything else can see…
Edit 3: SOLUTION (unhappily) I DISABLED SECURE CONNECTIONS and they can now see that server. This setting has ALWAYS been set to PREFERRED and I cannot understand why a setting that worked for sooooo long suddenly caused an issue…weirder than weird, man. Thanks!