"Password hash should be a 41-digit hexadecimal number" when changing virtual server password

Hi,

When attempting to change the password for an existing virtual server that is configured to keep the MySQL user password and virtual server user passwords in sync (the default behavior), I get the following error when trying to save the virtual server:

Password hash should be a 41-digit hexadecimal number.

I can create new virtual servers just fine and do not receive this error when I do so, but changing the password of any existing virtual server always fails with the above message.

I am running Virtualmin 6.07 Pro on an up-to-date CentOS 7 server running MariaDB 10.2.27. The password hashing format (as set in Webmin > Servers > MySQL Database Server > Module Config) is set to Default. I just started noticing this issue today though I haven't really had to change passwords for existing virtual servers in a while so maybe it existed before today.

How can I resolve this problem? Thanks!

Status: 
Active

Comments

We're just about to release Virtualmin 6.08 which should fix this issue.

Excellent, I'm glad to hear that and am looking forward to the release. Do you perhaps have an ETA for when we should expect the release? Also I know other forum posts regarding this error talked about using MariaDB 10.3 and 10.4 and how Virtualmin 6.08 would fix this problem for those releases; will it work with MariaDB 10.2 as well?

JEMEDIA thsi your site , and one virtualmin box?

Then maybe not solved. https://blog.jemediacorp.com/ Error establishing a database connection

6.08 update is out now i see , does this solve your probs?

If not so you can ask and give JAMIE / Support to have a look, maybe they can try/test with some updated parts of virtualmin. Sorry that i 'm breaking in here. ;)

Jfro,

Thanks for your comment; I just saw the release announcement and we're upgrading to Virtualmin 6.08 now. Also, we actually run a Virtualmin cluster with hundreds of virtual servers/Websites on it, with https://www.jemediacorp.com being our main site. You're welcome to explore our business if you'd like on our Website.

I'll report back when I have tested the new Virtualmin release and confirmed that it fixes this issue.