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

SSL Cert for Plesk in Virtuozzo Container

S

SeanJ

Guest
Having tried, without success, to replace the default/root cert being used for our Plesk installation from Media Temple a few folks on the forum directed me to http://kb.odin.com/en/1090 as a means to resolve our issue.

I've been unable to find any additional information related to part of the directions, i.e. extract and run it on Virtuozzo node. I'm unclear if this means the files should be extracted and run in the root directory of the server or another location.

Any additional information or guidance would be much appreciated.

Sean
 
doesn't really matte where you extract it. You are going to extract a perl script which you are going to execute. with the command below it in the example. When done you can just delete the perl script.
 
Apparently this can't be run (or can, but to no effect) from within the container itself which means this isn't a work-around unless you are the operator of the Virtuozzo environment/node.

Running it from root within the container does not change the SSL for the server, which leaves the base SSL still self-signed rather then making use of the new one.

Sean
 
Back
Top