- 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:
Which specific config can be blocking the above? Standard Plesk procedure to choose Forwarding instead of Hosting was used for setup.
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.