Hi,
Plex is running just fine and I can access it using all my devices except Plex Web (Safari for Mac) which says it is unreachable.
Any advice on how to fix it?
are you using local ( ip:32400/web) or hosted (app.plex.tv) web app? have you tried both http and https?
Hi,
I was using https://app.plex.tv/desktop which was a bookmark and has worked for years.
http://app.plex.tv/desktop does not work
https://192.168.1.63:32400/web gives a “connection not private” warning
http://192.168.1.63:32400/web requires me to sign in, yet shows the fact that I am recording right now - weird…
…and works once I have signed in.
because TS won’t technically work over a local network. If you are on chrome there should be a advanced button then a link to proceed anyway.
are those poster our free streaming content?
I’m curious if you can access from there via a incognito/private window
Yes. Showed my recording and your free content.
I’m not in a position to check right now, but will do it tomorrow.
Cheers!
Those pesky not private messages are “normal.” You need to purchase a certificate that is beyond this post’s scope. Bottom line, certificates are created to ensure that some bad-actor didn’t insert a phony certificate in the middle of your chain to compromise your sensitive transactions otherwise known as “man-in-the-middle” attack. The interesting thing is that you said it worked for years which it shouldn’t have. Browsers are getting more strict to protect you.
We provide certificates for free. It is just that on a they don’t really do anything on a local network
Yes there are free certificates. Yes this is non-trivial to make work on a “local” network and may require a dynamic DNS route back to a sub domain of your router wan IP along with router port forwarding to the DMZ server without breaking the security of the network:-). This assumes one has purchased a domain, the certificate.
fair enough. but regardless the https://app.plex.tv should work without doing anything special just need to figure out why. may just need to start server to refresh its certificate.
After checking an incognito window @JCHH I would open the page and look at the console logs of the browser to see what might be going on as you try to go to that page. (Don’t post them here unless you blank out any tokens in them that might show)
Once I have logged in, I get the same error
…and to confirm, it is still working fine on Plex for Mac.
Agreed. It has worked for me for years - thanks for the help.,
Thanks, I do understand how to do this but, this link has worked for a long time as it is without anything special and I need to understand why it is not working now 
What’s the result of pinging your server’s local *.plex.direct FQDN from the client system? This FQDN is derived from the server’s local IP address (delimited by hyphens instead of periods), your certificate UUID, and the domain “plex.direct.” An example would be:
192-168-1-100.your_certificate_uuid.plex.direct
You can find your certificate UUID by running the following from the terminal on your server, if it’s also a Mac:
defaults read com.plexapp.plexmediaserver CertificateUUID
If you’re on Windows, it’s in the registry at:
HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server → CertficateUUID
If you’re on Linux, it’s in your Preferences.xml file in your Plex data directory.
Once you’ve determined the FQDN (don’t post it here), try to ping it from client system to see if you receive replies from your server’s local IP address.
Jchh,
I haven’t resolved pieces of your post so hopefully this helps somewhat.
— Sometime back, I believe at least a year ago, browsers started protesting the certificate issue for your safety. This has been getting more solidly enforced with time and at some point I wouldn’t be surprised when the browsers start refusing to allow exceptions
— None of the common browsers (Firefox, Chrome and Safari) will work with a bad certificate. I assume Windows browsers are similar.
As such I have two theories:
-
you were running an old browser and it got recently updated
-
Plex used to let you connect to HTTP and now it is redirecting to HTTPS for improved security.
Item 1) above is very common. People are seeing this all over the internet. My network stack has this issue and when I have some time I need to fix it.
To fix 2) you should be able to use a self signed certificate and register it on both the Server AND the client. For your security don’t put the private key on the server. I have done this for standard Mac Java apps but haven’t done for IOS so I cannot guarantee it. Hopefully with a bunch of googling you can find a solution that works for you.
Good luck.
Hi,
Thanks for your reply!
-
I am â– â– â– â– about running the latest versions. I am on a Mac with Big Sur.
-
I have only ever connected by browser using Safari over https (using a bookmark) to https://app.plex.tv/desktop
…just spotted that my use of <@nal> has been redacted - obviously the system doesn’t understand context!
Big Sur claims more security and that is a recent change:-). Not surprising if Apple broke something for you. I just upgraded about two weeks ago to Catalina since I cannot move to Big Sur yet.
It was working fine recently and I upgraded to Big Sur weeks* ago, so I don’t think it’s that.
Edit: changed months to weeks.
You can look at the web app logs here for errors. https://app.plex.tv/desktop#!/logs
But I would also look at the console logs of the browser itself as the page is loading for errors
If you want to try to get a new certificate you can delete the certificate.p12 file in the cache folder of the server which would be in the PMS data folder on most systems. on Mac it is in the library/caches/plexmediaserver folder. After deleting restart server and clients.
Will try that tomorrow - thanks.
I forgot to ask. what is your server running on? the same mac you are trying to access it via safari or a different device?
