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

Subdomain Permission Problems ...

O

OmegaQuest

Guest
I just installed a fresh 8.2.

Everything seems to work fine (So far) except Subdomains.

When I create a subdomain (Using the same FTP Account option), everything seems fine.

However, when I go to the subdomain via the web, it promps me for a username/password.

The following Permissions are set on the Subdomains Root Directory:
Plesk Domain User = Special Permissions - Allow & List Folder Contents - Allow
Plesk IIS User = Special Permissions - Allow
FTP Sub Accounts = Special Permissions - Deny

-----

The following Permissions are set on the Subdomains httpdocs folder:
Plesk IIS WP User = Special Permissions - Allow & List Folder Contents - Allow
FTP Sub Accounts = Special Permissions - Deny

** There are no other Plesk Permissions on this folder **

-----
I assume this is the reason, but why isnt Plesk setting the correct permissions on Subdomains when they are created?

** Note ** I have also ran "Currect Plesk Permissions Tool" and this did not change anything.
 
Fixed the problem, by logging in with the user and having them create the subdomain instead of the admin account.
 
Back
Top