Server Version#: Latest Linux and NVIDIA Shield Server
Player Version#: all players affected.
Ever since the recent Plex Auth outage, both my servers, Linux and Shield TV, show “server does not allow secure connections”
This results in me unable to use https in app.plex.tv. I have tried to logout on all servers, both using the Head Icon and in Server General Setting page. I have tried to ssh tunnel to servers and log-out from there. I tried deleted the servers, unclaim and claiming again.
I have tried to use Plex default *.plex.direct certificates and my own certificates.
All doesn’t get me the result I want.
I can still access my media when I use http or enable unsecured connection as “always”.
I checked Preference.xml but it’s all good.
Prior to the recent Plex Auth outage, both my servers works perfectly with secured connection using Plex’s own security certificates and even my own domain and my own certificates.
In addition to above problem, ever since the outage, Plex sometimes force me to use Plex Relay even when Direct Access is enabled. Once I restart the server then I could stream directly.
It was reported earlier today that a problem was found when two servers exist.
The second server would not get a new certificate which, obviously, prevents secure operation.
They are working on a hot fix to it now.
And I take it back, yes, it is the same problem, and I thought it was fixed but it is not. After several reboot my Linux PMS can get the cert and get the lock sign back. However Nvidia Shield server still has the problem, can’t access via https, there is no lock sign.
I hope Plex take a look at this…
Same issue here, it seems. Can’t get any device in my home to securely connect, though mostly tested through the web player. Rebuild server from scratch thinking it was something on my end, but brand new server (and rebuilt database anew) and same issue. On a whim I downloaded the Plex Media Player for OSX a while ago and it can connect just fine, but any browser (Incognito/Private Mode and cleared cache) on the very same machine runs into the secure connections error. I got a ‘wonderful’ login loop by always allowing non-secure connections at the prompt, causing my CPU usage to spike and the browser URL bar to keep rapidly switching between addresses trying to resolve the right site. Cleared cache and decided not to try that again. Kinda dead in the water on this one right now…
Think I’m facing a similar issue possibly? I didn’t notice until upgrading to 1.14.0.5468-5a0183d2c. Even though I had secure connections set to required, I had to set to preferred because I keep getting an error that my server doesn’t allow secure connections.
I am having the same issue. At first I thought it was something from my migration. I recently built a new brand new Plex server, and finished migrating the old plex server over this weekend. I get the error “” does not allow secure connections on the new box. I can’t seem it fix it. Sounds like I need to wait for this hot fix and it is not on my end?
Is this still an ongoing issue?? Because im experiencing something similar on a new linux server (2nd on my account) which fails https requests on port 32400 ( This site can’t be reached 1.1.1.1 unexpectedly closed the connection. ) Http works
I have a desktop PMS. I had a hard drive failure and copied over my PMS to the new hard drive. I’ve had the issue since setting up. If you can help, that would be great.
If you can’t reach 1.1.1.1 (secure DNS) , I think you have another issue within the machine itself. I am using that currently without issue in pfSense.
Yes, I can help with destkop Linux. (this is my area). I apologize for any confusion about where the issue was rooted. Many reference nVidia Shield and use it as their server…
Regarding your server, I would like you to perform a bit of an ownership recovery.
We will re-establish authentication for your server and then, after the soft reset, transfer over the previous Machine ID information if you need it for established external users (shares)
Stop PMS
Get into a root shell
cd "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server"
mv Preferences.xml Preferences.xml.old
chown -R plex:plex /var/lib/plexmediaserver"(this will run for a bit)
As it starts the Setup Wizard, Do Not create new shares… The existing are untouched
Set anything else you wish along the way but best to Skip and then Finish
Your secure settings in Settings - Server - Network should now be controllable again.
Please let me know before enabling IPv6. PMS is getting IPv6 support but it’s spotty at best. IPv4 is the preferred and by far most stable means. Metadata will not retrieve properly yet if IPv6 enabled.
I replaced my public ip with 1.1.1.1 for security issues… but I mean the IP of my PMS so i was trying https://my.public.ip:32400, which the web server fails to responds (cuz of missing certificates?). http://my.public.ip:32400 works
I want the default behaivor, to use plex certificate. Currently it seems something wrong on the Plex Server side (corporate) that for some reason it isnt giving the generic certificates. According to the log, its giving a 503 error when my Plex Server tries to grab a new certificate. And because this is missing, https (even with an invalid certificate error) aint working.
so i was trying 