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

Severe SSH Issue

t.van.der.plas

Basic Pleskian
Dear all,

we are currently experiencing severe ssh issues with plesk and are unsure if that is a missing feature or if we are too stupid to do it right? follwing situation:

we have a shop system running on top of a plesk server, one domain per language, accessing the same htdocs.

No problem here as we were able to define the main url: myurl.de and add the myurl.com, myurl.fr, myurl.nl etc. as domain aliases.

The problem comes when trying to define ssl certs. For the main domain (myurl.de) this is fairly easy (excusive ip, and cert added to this domain) but how can we add additional certs (for .com, .fr, .nl) to the domain aliases?

Without these certs we get an browser errormessage that i have tried to reach myurl.com but the cert has been issued to myurl.de

Cheers

Tobias
 
Back
Top