• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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