• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Question Let's Encrypt for ONLY alias domain?

HostaHost

Silver Pleskian
Anyone know a way to work around Plesk trying to get an LE cert issued for both the primary domain and the alias? For a website under development, the primary site may be pointed elsewhere, but it needs to be defined in Plesk with the real domain so the paths, email addresses, etc. are all correct. We'd like to have an LE cert issued for just the alias domain to allow development to be secure, before switching to the primary domain later on.
 
Unfortunately that doesn't work. The issue is that while that does allow you to have an LE cert issued to an alias, it attempts to order the certificate for the primary domain first with the alias as an alternate name, so when the primary fails (because it isn't pointed at the development site), the alias fails too.
 
Back
Top