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

Question Using plesk as subdomain instead of a specific port

Markus_DE

New Pleskian
Hello everyone,
I'm trying to make plesk (Windows IIS Version) accessible through a subdomain instead of a specific port - plesk.example.com for example instead of example.com:8443

The idea to create a normal subdomain and changing document root in IIS to the same as the *:8443 site does not work (error 500).

Any other ideas or maybe a simple switch I just did not see?

Regards
 
Back
Top