I just looked at your certificate.
It was:
Created: Sun, 19 Mar 2023 20:05:20 +0000
Updated: Sun, 19 Mar 2023 20:05:28 +0000
Have you restarted the server and all players ?
Thanks for getting back to me. I had previously in day asked another team member to reset it but it think because of the time zones he never replied until about 20.05 and that was when i restarted the Shield. It never changed anything at the time, I still couldnt get into my server setttings and my remote access still wasnt working. It seems to be working again, thanks so much for your help.
Glad you’re up and running.
(I’m cooking today – hence why I’m a bit slow on replies 
)
1 Like
I also have the same issue, would it be please possible to reset my certificate?
Many thanks
Your certificate was valid. I have reset your certificate to be safe.
If you still have authentication errors, check the networking and any other certificates you have installed.
If unable to resolve, please attach tar.gz or ZIP of your DEBUG server logs.
hi
right after install PMS Version 1.32.0.6865 on my synology- my ssl certificate isn’t work anymore.
it starts now with a self issued cert.
in the logs i can see that error:
Apr 04, 2023 10:38:23.928 [0x7f3e8089fb38] INFO - Plex Media Server v1.32.0.6865-ba892e5ce - Synology DS716+II x86_64 - build: linux-x86_64 synology-dsm7 - GMT 02:00
Apr 04, 2023 10:38:23.928 [0x7f3e8089fb38] INFO - Linux version: DSM 7.2.64216-0, language: en-US
Apr 04, 2023 10:38:23.928 [0x7f3e8089fb38] INFO - Processor: 4-core Intel(R) Celeron(R) CPU N3160 @ 1.60GHz
Apr 04, 2023 10:38:23.928 [0x7f3e8089fb38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Apr 04, 2023 10:38:23.928 [0x7f3e8089fb38] INFO - /volume1/@appstore/PlexMediaServer/Plex Media Server
Apr 04, 2023 10:38:23.930 [0x7f3e80b11a90] DEBUG - BPQ: [Idle] -> [Starting]
Apr 04, 2023 10:38:23.931 [0x7f3e80b11a90] DEBUG - FeatureManager: Using cached data for features list
Apr 04, 2023 10:38:24.084 [0x7f3e80b11a90] DEBUG - [CERT] Subject name is /CN=*.xxx.plex.direct
Apr 04, 2023 10:38:24.085 [0x7f3e80b11a90] DEBUG - [CERT] Installed certificate with fingerprint xxx.
Apr 04, 2023 10:38:24.085 [0x7f3e80b11a90] DEBUG - [CERT/OCSP] Stapling requests will be made to 'http://r3.o.lencr.org/'.
Apr 04, 2023 10:38:24.085 [0x7f3e80b11a90] INFO - [CERT/OCSP] Successfully retrieved response from cache.
Apr 04, 2023 10:38:24.091 [0x7f3e80b11a90] ERROR - [CERT] PKCS12_parse failed: error:0308010C:digital envelope routines::unsupported
Apr 04, 2023 10:38:24.091 [0x7f3e80b11a90] ERROR - [CERT] Found a user-provided certificate, but couldn't install it.
@noyse, I am seeing the same thing:
I have not had time to check the debug logs though.
Same issue here but using Docker. Own ssl certificate generated with NPM and converted to pfx archive stopped working. As we share the same version I suspect it was since the latest release 1.32.0.6865
Apr 04, 2023 10:29:14.363 [0x7f5b2a441b38] ERROR - [CERT] PKCS12_parse failed: error:0308010C:digital envelope routines::unsupported
Apr 04, 2023 10:29:14.363 [0x7f5b2a441b38] ERROR - [CERT] Found a user-provided certificate, but couldn't install it.
Seeing same issue also. Same log messages. Centos 8 Stream for me.
I have one client (chrome browser on an old macbook) getting the error “app.plex.tv unable to connect securely” (other clients are able to connect fine). I see some TLS issues in the log:
May 03, 2023 16:12:38.188 [0x7f84698feb38] DEBUG - CERT: incomplete TLS handshake from 127.0.0.1:60604: sslv3 alert certificate unknown (SSL routines)
May 03, 2023 16:12:40.631 [0x7f84698feb38] DEBUG - CERT: incomplete TLS handshake from [::ffff:192.168.2.1]:54780: sslv3 alert certificate unknown (SSL routines)
May 03, 2023 16:12:40.637 [0x7f84696fbb38] DEBUG - CERT: incomplete TLS handshake from [::ffff:91.XXX.XXX.XX]:54782: sslv3 alert certificate unknown (SSL routines)
May 03, 2023 16:12:40.726 [0x7f84698feb38] DEBUG - CERT: incomplete TLS handshake from 127.0.0.1:60612: sslv3 alert certificate unknown (SSL routines)
May 03, 2023 16:12:40.773 [0x7f84698feb38] VERBOSE - WebSocket: processed 1 frame(s)
May 03, 2023 16:12:40.795 [0x7f84696fbb38] VERBOSE - We didn't receive any data from 192.168.2.1:54764 in time, dropping connection.
May 03, 2023 16:12:40.804 [0x7f84696fbb38] VERBOSE - We didn't receive any data from 91.160.XXX.XX:54766 in time, dropping connection.
May 03, 2023 16:12:40.844 [0x7f84696fbb38] VERBOSE - We didn't receive any data from 127.0.0.1:44480 in time, dropping connection.
Might resetting the certificate for my server help? Thanks!
Questions:
-
Does it work anyway? If so – Ignore it
-
Is the macbook still supported by Apple ?
-
Are you using your own custom certificate ?
I noticed your certificate refreshed two times today.
Have you restarted the player app so it has the correct certificate ?
Ah, the macbook is no longer supported by Apple, so that’s probably the issue, thank you.
It doesn’t work accessing the server via app.plex.tv, but it does work if I access it directly through server-ip:port, so that’s an acceptable workaround for the time being, thank you!
If no longer supported by Apple, the internal SSL certificate will expire at some point.
Once expired, it won’t be able to partake in SSL connections.
This is likely what’s happening now.
Using IP addresses is HTTP only. (not HTTPS) so it doesn’t need SSL.
The way to configure the server for this:
- Settings - Server - Network - Show Advanced
- IP addresses allowed without auth
- Add the Macbook IP
- Be careful with that field… Its difficult to see leading/trailing spaces. Spaces cause the whole server to go stupid until fixed.
1 Like
Perfect, thank you so much!
Hey chuckpa,
I’m having the same NET:ERR_CERT_COMMON_NAME_INVALID on plex.tv/web
Could you please reset/ check my certificate?
Thanks!
Your server cert updated today.
Did you restart the server and player apps (full restart)?
@ChuckPa Hi Chuck, I have the same issue again. Not able to connect to Plex from my network due to SSL problems, could you please renew my cert. again please?
Thank a LOT!
I’ve reset the cert but you DO need to start the server 
lol
It’s not been seen in 11 days 
Well, thats weird, according to NAS was up and running. I reinstalled it and now it works. Thanks
