Every time I use the web app, I’m getting report something wrong with the certificate. I gave it time for Plex to renew the certificate, but that’s not happening after this long. I would really like to see this resolved.
Thanks
Every time I use the web app, I’m getting report something wrong with the certificate. I gave it time for Plex to renew the certificate, but that’s not happening after this long. I would really like to see this resolved.
Thanks
Please report the exact error message. Make a screenshot if possible.
This usually only happens when there are other parties interfering, like corporate firewalls or anti virus software.
Yes, it’s Kaspersky terminating it. When I get home, I’ll take a screenshot and write down the message as well.
Thanks
I am pretty confident that it is Kaspersky which is the reason for the failure in the first place.
When Kaspersky is decrypting the secure communication between the Plex clients and the server, it does the following:
Without Kaspersky’s interference, the packet would have a certificate that shows your Plex server’s fully qualified domain name.
You must tell Kaspersky to not decrypt encrypted communication.
I am pretty confident that it is Kaspersky which is the reason for the failure in the first place.
When Kaspersky is decrypting the secure communication between the Plex clients and the server, it does the following:
Without Kaspersky’s interference, the packet would have a certificate that shows your Plex server’s fully qualified domain name.
You must tell Kaspersky to not decrypt encrypted communication.
@OttoKerner said:
I am pretty confident that it is Kaspersky which is the reason for the failure in the first place.When Kaspersky is decrypting the secure communication between the Plex clients and the server, it does the following:
- decrypt the packet
- inspect the packet
- re-ecrypt the packet - but this time using its own cyrptographic “intermediate” certificate.
And that is making the data packet invalid, because the certificate and the domain name from where it is coming from don’t match anymore.Without Kaspersky’s interference, the packet would have a certificate that shows your Plex server’s fully qualified domain name.
You must tell Kaspersky to not decrypt encrypted communication.
Spot on. It is Kaspersky. =)
I have a similar problem when connecting to my server directly (https://server.url:32400):
While Firefox/Win7 at work shows it trusts the certificate, Chromium/Linux says it’s not a secure connection.
Who is right? 
@Coxeroni said:
I have a similar problem when connecting to my server directly (https://server.url:32400):
While Firefox/Win7 at work shows it trusts the certificate, Chromium/Linux says it’s not a secure connection.
Who is right?
Are you using Kaspersky?
Nope, so probably I wasn’t allowed to hijack the thread? 
@asaintfort said:
Could you also show what’s on the ’ General’ and ‘Details’ tabs?