Plesk self-signed certificate is displayed instead of the one signed by a public CA: The certificate is not trusted

Created:

2016-11-16 12:48:19 UTC

Modified:

2017-08-16 16:33:31 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Plesk self-signed certificate is displayed instead of the one signed by a public CA: The certificate is not trusted

Applicable to:

  • Plesk 11.x for Linux
  • Plesk 12.0 for Linux

Symptoms

Wrong certificate is displayed for a domain. It is Plesk self-signed instead of the one signed by a public Certificate Authority:

example.com uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
The certificate is only valid for Parallels Panel The certificate expired on
Error code: SEC_ERROR_UNKNOWN_ISSUER

Curl detects certificate incorrectly:

curl -v https://example.com:443
...
* SSL certificate problem: self signed certificate

Correct certificate is selected in domain's Hosting Settings menu.

The certificate file is valid, it is not default or self-signed:

openssl x509 -noout -in /usr/local/psa/var/certificates/cert-XXXXXX -issuer
issuer= /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA

The following error can be found in /var/log/nginx/error.log :

[emerg] 5803#0: open() "/var/www/vhosts/system/test.EXAMPLE.com/logs/proxy_access_log" failed (24: Too many open files)

Cause

Nnginx did not load the correct configuration.

Resolution

Restart Nginx:

# service nginx restart

If there is 'Too many open files' error in the Nginx log, please increase limits according to:

213938485 If there are more than 256 domains, Nginx fails with a "Too many open files" error

Have more questions? Submit a request
Please sign in to leave a comment.