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

Issue Forwarded domain can't be secured

TomBoB

Silver Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
18.0.62 Update #1
Hi all, according to this article a forwarded domain should be able to be secured.

Server has Nginx as proxy in front of Apache. Running that test as per article shows Enabled:true.
There is no option to secure the domain in Plesk apart from webmail subdomain.
When attempting to do via CLI, it throws an error:

Code:
4133423:66979a9028b27 ERR [extension/sslit] Unable to secure domain clientdomain.com via CLI.
Validation failed:
Unable to secure a domain name due to configuration of the specified domain.
exit status 1

Which specific config can be blocking the above? Standard Plesk procedure to choose Forwarding instead of Hosting was used for setup.
 
Hi,
Yes was/is enabled.
Couldn't let client wait. So created hosting quickly and used a Nginx directive to do the redirect/forwarding quickly. Which we now use as a way around above.
Will carefully watch each step next time we have to set up a new forwarding for a domain.
Thanks for coming back to us!
 
Hello, did some super quick testing. May have to backtrack what I said above. The symptoms of disabling SSL/TLS are exactly what had happened. Will have to carefully go through the log files.
As we always always use SSL - the is no use case ever where we don't - above is odd. But it matches what happened. Thanks for pointing it out!!
 
Back
Top