• 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.

Plesk uses old SSL certificate

4

4drob

Guest
We've ran into this problem on a number of servers. Often when renewing or adding a new SSL cert, Plesk insists on using the old one even though all conf/include files say otherwise. We finally found a fix, which involves removing SSL completely from all domains and re-adding it. I didn't come across this in any SWSoft documentation or knowledge base (atleast with a few searches), so I wanted to share it just in case others were having a similar problem.

So if you assign the new cert by IP or domain yet when browsing to the domain it still says its expired, try running:

ls /var/www/vhosts/ | xargs -n 1 -iREP /usr/local/psa/bin/domain.sh -u REP -ssl false
ls /var/www/vhosts/ | xargs -n 1 -iREP /usr/local/psa/bin/domain.sh -u REP -ssl true -same_ssl true
/usr/local/psa/admin/sbin/websrvmng -a
 
Back
Top