• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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