• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Enabling SSL for plesk panel login

Sean P

New Pleskian
Hi there, this all used to work, I was able to login to the plesk panel using https://subdomain.domain.tld:8443/ and it picked up the SSL certificate for the subdomain and allowed us to log in over https with no SSL certificate warning.

We recently repurchased an SSL certificate for the same subdomain, I've imported it in to Plesk and clicked "Secure plesk" but it's still giving SSL warnings when I try to login. There's probably something really obvious I've missed but for the life of me I can't find where the problem is, anybody have any ideas?

Many thanks
 
Sorry, just to add to this, it looks like it's still trying to use the old expired certificate, despite me choosing the new one in plesk to secure plesk with.
 
Same here. Purchased a SSL cert dedicated for plesk with a dedicated domainname. Made req file and private key with OpenSSL using 4096 bits and SHA256. Cert chain succesfully imported with no errors. Selecting this cert and pressing Secure Plesk does nothing. Plesk is up-to-date with latest patches etc. Running Centos 6.7, fully patched.
 
It's a real pain, I know the cert is valid as I use it for qmail & courier for connections over SSL using that subdomain.
 
I believe I may have fixed it, I was getting all manner of nginx bind errors when I tried to restart the plesk web server and found a way round it via this forum.

Find all the sw-cp processes:
ps ax | grep sw-cp

Kill them all:
killall -9 pid

Try your restart again:
/etc/init.d/sw-cp-server restart
Stopping sw-cp-serverd: [FAILED]
Starting sw-cp-serverd: [ OK ]

Now I can use ssl on that subdomain for panel access finally!

I must make a note for next January when the cert. expires again ;)
 
Back
Top