• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

CA Cert for Plesk Login

N

nathacof@

Guest
I have a customer who wishes to use their XRamp wildcard SSL certificate for practically everything.

However IE is complaining when he navigates to the login screen:

"The Security Certificate presented by this website was not issued by a trusted Certificate Authority."

It works fine everywhere else.

Now I can grab the CA certs from XRamp's site, but they are already added under Server -> Certificates.

Since Plesk runs it's own instance of Apache it's safe to assume I need to install the CA certs into this instance. How would I adjust the Plesk webserver specific settings?

FYI: http://kb.swsoft.com/en/1712 < Following this KB does not resolve the certificate error in IE even though the CA cert is in place.
 
OK So a coworker of mine figured this out during lunch. It appears that the psa database was not being update to use the proper cert file.

He created the CA Cert:

/usr/local/psa/var/certificates/cert-wildcard

and update the PSA database:

mysql> update certificates set ca_file='cert-wildcard' where name='*.example.com' LIMIT 1;

And everything worked fine after that point.
 
Back
Top