• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Unable to reset user password by username

JonathanSmith

New Pleskian
Hi,

I have created a user with the role "WebMaster" on Plesk.
When the user uses "Forgot your password?", he has 2 choices:
Reset password by Email address or by Username.
By Email address, everything is correct and works.
By Username, the email never arrives. In the Plesk "panel" logs, I see the error message "Password reset request for email '' was denied: account is not registered".

I have redone these tests with several accounts and there is always the same problem.

Thanks for your help

Plesk version : 18.0.49 Update #1
OS version : AlmaLinux release 8.7
 
Hi @JonathanSmith, thank you four your post. Sorry to read that you are experiencing issues with this function. This is a known issue [PPPM-13839] that will be fixed in future updates. For now the suggested workaround is to use the email address instead.
 
Back
Top