• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

creating a secure (https) subdomain

You need to create subdomain.xyz.com as a domain and not a subdomain. Then you will have the option to allow ssl.
 
Thanks Troy

I figured out a way to do it through the httpd.include file in conf folder. Now subdomains inside my conf folder also can be secure.

Actually saving 1 domain licence :)
 
You may want to consider using a vhost.conf file to make your change to the subdomain. I had trouble with Plesk overwriting the httpd.include file when I would update the domain through Plesk. I found somewhere else on this forum to use a vhost.conf in the conf directory instead and it won't be overwritten. Not sure what you changed, but it should work in your case too. After making the changes you will need to run this for the changes to take.

/usr/local/psa/admin/bin/websrvmng --vhost-name=domain.com
service httpd restart
 
Back
Top