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

error while setup physical hosting

S

shark95763

Guest
When I create a new domain, I always get this error , no matter what password's or username's I try to create :

Unable to assign variables for PHostingForm: Unable to get hardquota state: Unable to add the user (panzernl), invalid parameter is (-1): (2245) The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.

--------------------------------------------------------------------------------

0: D:\Program Files\SWsoft\Plesk\admin\htdocs\domains\hosting\phosting_setup.php:279 psaerror(string "Unable to assign variables for PHostingForm: Unable to get hardquota state: Unable to add the user (panzernl), invalid parameter is (-1): (2245) The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.")


how to fix?
 
You've got custom password policy configured.

To disable password checking you need to go

Start > Administrative Tolls > Local Security Policy > Expand Account Polices > Expand Password Policy > Double click on `Password must meet complexity requirements` > Disable.

Then the problem will gone.
 
The fact we're told to turn off password complexity so that Plesk is able to work if people add users with insufficiently complex passwords is pathetic.
Plesk should be fixed to respond correctly to user creation errors.
Also if a user creation fails, it should rollback the addition of the domain entry into the DNS configuration, which you otherwise have to manually remove before re-attempting to create the user with a correct password complexity.
Plesk should be accomodating ALL industry standard security mechanisms.
 
Back
Top