Server Version#: 1.43.3.10861
Player Version#: Web
Tried to log onto my Plex Server through the web this AM and it’s returning an untrusted cert warning, then some XML, not a web page. The server is up and working otherwise, and it’s processing new media and serving content normally. App clients having no visible issues.
It’s been several weeks since I logged into Plex Web on the server, so not exactly sure when this issue arose.
No idea how to start looking into this. Thoughts ??
A good start would be to at least provide the name and version of the browser.
Are you perhaps using local server IP in the url?
If so then it will fail
Try this: https://app.plex.tv/
The “Y”-generation of certs require a new-ish root certificate to be trusted on your web browser/OS.
Some manufacturers still don’t have this root certificate integrated. Apple for instance, or Sony (on Playstation).
I have triggered the recreation of a new certificate for your server, which is based on the previous root certificate. Try stopping and restarting your server, if it doesn’t pick up the new cert right away.
Any (Brave, Edge, Chrome, Firefox)
No, straight IP and port.
Do you have the signer thumbprints so I can verify the root store ? This is W11, BTW.
That works, but it’s using different cert (plex.tv) not the Lets Encrypt server-specific one.
This has nothing to do with your personal server. It’s not using the plex.tv domain, but a subdomain on the *.plex.direct domain.
Yup, just shows the server itself is otherwise healthy.
Are you certain you are loading the web app?
Don’t forget the /web folder at the end when loading the local version.
Also seeing only the below in the Trusted Root CA store (W11),
The new cert issued this AM (presumably on forced reboot) has a different signing chain. So, that confirms the what, but not the why.
In theory I could trust these manually and mitigate the symptom, but curious why M$ has not updated them, and why more users are not experiencing the same issue.
but wait, the error is about the CN, not the signing chain. Using internal IP to access.
That is because the certificate is issued for like: *.<MACHINE_IDENTIFIER>.plex.direct so it will fail if using https://<IP>:32400/web with a warning that it is invalid
You can in the browser select to ignore and continue and it should work
Regarding a redirect from https://<IP>:32400 to https://<IP>:32400/web then that only works if you do not have set the IP address to be allowed without AUTH
No, it won’t. At least not on Windows.
I’m assuming I have a cached sign-in on this browser session, but have never been prompted to confirm home screen defaults on sign in. The behavior is very different than the past “normal”. Trying to determine why these behaviors started recently (past couple weeks).
Previously I would use “https://local_ip:port”, bypass the cert name mismatch error, and get right in. Now the redirect to “/web” seems required, and the “Customize your media” page is displaying.
You probably have the computer’s ip or subnet in the field List of IP addresses and networks that are allowed without auth
This allows a client to bypass authentication and connect to the server directly. When you access in a browser, it gives that prompt first since you’re a “new” user. It allows full access to server settings and content, no profiles. It’s used as a workaround when internet goes down, but it also has impacts like this.
