PLEX HTTPS configuration causing security warnings; "https://domain.com" does not point to PLEX

While my configuration has a variety of errors, I will only address two of my largest issues.

PLEX Server 1.17.0.1709-982421575 (macOS)
PLEX Client (macOS, Firefox)

I currently have my PLEX setup running with nginx, Let’sEncrypt, and a Freenom domain. I have generated certifcates with certbot and a PKCS12 certifcate for PLEX. In PLEX’s network settings, I have put the path to the certificate, the password chosen during its generation (via openssl), and domain name https://[domain].gq:32400.

Currently, my server works however, when I try to access it via https://127.0.0.1:32400 on my server, I get a “SSL_ERROR_BAD_CERT_DOMAIN” and a description saying “Firefox does not trust this site because it uses a certificate that is not valid for 127.0.0.1:32400. The certificate is only valid for *.85d91b22d7d0487881399322a2314960.plex.direct.”

Another issue I have is that my domain does not point to my IP if I go to https://[domain].gq, but it does work when going to https://[domain].gq:32400, with the SSL_ERROR_BAD_CERT_DOMAIN warning. My public IP does direct to PLEX, but with HTTP.

My nginx server blocks: https://pastebin.com/kgkxrs6W

Sorry if my explaination is jumbled, I am very confused by all of my server’s problems and inexperienced.

Thanks in advance!

1 Like

same issue,… it’s very enoing…
can’t find any clear solution for this stupid problem.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.