• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Potential bug - Password length - Plesk 10.1

L

Laakness

Guest
I ran into this issue yesterd/today while troubleshooting why one of my users continually was creating a subscription that could not be deleted. I found the thread on how to manually remove a site from Plesk but they would recreate it and the same issue would occur again and I believe I've found the cause.

It seems that there is a 14 character limit on the password set for the ftp user that gets created by default with each subscription.

This is Plesk 10.1 running on Windows Server 2008R2 x64.

User would login as their reseller account and create a new subscription. During the creation they would specify the domain, shared IP, and all the other default settings. The user was pasting in a 17 character password. The site would create successfully but when you would click on the subscription I noticed that there was no system username associated with the account. Any other changes to the site resulted in all sorts of query errors, etc. This required me to remove the site manually.

I then recreated the site with an easy password not knowing at the time that was the issue and the site created fine. I then had the user login and reset their system user's password and every time they pasted it in I got some sql error stating the password couldn't be blank but it would display the password in the error message.

We kept changing the password and incrementing the character count until we got to 15 where the error occurred again.

Not sure if anyone can replicate this but all you would have to do is create a subscription and then try changing the password to something over 14 characters.

I don't think the same data processing logic is being performed on the password field during site creation as it is when you try to change it later.

Hope this helps someone besides me.
 
Update:

Here is the message that is displayed when trying to set the password to a value larger than 14 characters.

Error: Account->update() failed: Some fields are empty or contain an improper value. ('password' = '111111111111111')
 
Back
Top