• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Changing the PSA SSL Certificate

dragnovich

Basic Pleskian
Had you tired to change the PSA certificate?? and found the it DOES NOT CHANGE, even doing everithing you found in the forums... I did not make it work.

So I do a little logic thinking, and fixed the problem, this is what I do.

Backup the files:
/usr/local/psa/admin/conf/rootchain.pem
/usr/local/psa/admin/conf/httpsd.pem

When you buy your certificate you will receive various CRT files, open those files in a separate window (process) ready to copy text.

Then edit the file (/usr/local/psa/admin/conf/httpsd.pem):
and paste the certificate RSA PRIVATE KEY first, then one empty line and then the Domain Certificate file). IE:
-----BEGIN RSA PRIVATE KEY-----
bla bla bla bla bla bla bla bla
-----END RSA PRIVATE KEY-----

-----BEGIN CERTIFICATE-----
bla bla bla bla bla bla bla bla
-----END CERTIFICATE-----

Then open the file (/usr/local/psa/admin/conf/rootchain.pem):
And paste here the CA root certificate you received with the certificate keys. Some root certificates requiere more that one certificate, in that case you will receive all (or directed to a download page). So paste ALL other certificates you received in this file separated by a blank space (Do not paste the, CSR request, the Key Certificate and the Site Certificate).

Stop & start the PSA process:
/etc/init.d/psa stop
/etc/init.d/psa start

Close all browser windows you have open, and access your Plesk Panel:
https://yourdomain:8443/

And voala!

If it does not work with your Plesk version, the solution was just researching the Apache Plesk configuration file (/usr/local/psa/admin/conf/httpsd.conf), where the psa tells the apache what certificate files to use. And find where apache reads the certificate, with the lines SSLCACertificateFile & SSLCertificateFile and edit those files.
 
Back
Top