The following users lack valid password hashes

Apps and Virtualization
1

“The following users lack valid password hashes. This may occur if the TrueNAS configuration was restored without the secret seed and may be fixed by resetting the user password through the TrueNAS UI or API: docker”

Just upgraded to 25.04.1 and got this error message.

I have never given docker a password - its a built in user - so whilst I could give docker a password as the message suggests - anyone know what the implications of this are?

2

If you look at the title of the alert it should read:

title = "SMB user is missing required password hash"

This means you have a user configured as an SMB user without a valid SMB password hash (meaning you either restored without the secret seed or somehow created the user as an SMB users at some point when it shouldn’t have been created as such. Perhaps change the user so that it’s not an SMB user.

3

It doesn’t actually say that

image
image504×321 11.1 KB

or the email
image
image1955×209 6.77 KB

It looks as though the upgrade ticked the SMB User field in the built in docker user (GID 999) which I have now unticked.

I think I am going to need to reboot to test the “fix”

Given that this hasn’t happened to any other user (so far) this looks like an upgrade issue

4

Can you verify that it was unticked before upgrade? I don’t see any likely candidates for a db migration that could cause that behavior.

5

I will boot 25.04.0 in a few minutes and check. I can state that I have never adjusted the user and that the error never occurred before

6

The alert wasn’t working properly in 25.04.0 and it’s alerting on a new error condition that we’re checking for in 25.04. It’s entirely possible this user has always been misconfigured.

7

Regardless, the error message could easily be improved by pointing at “the following SMB users” rather than “the follwing users”

1 Like
8

Given that - then yes its possible.

After a reboot with 25.04.0 - the docker user was also an SMB user. It looks as though it was probably always an SMB user. I assume a very minor bug as I never set the user up in the first place and can’t see myself editing this by mistake.

Has anyone else got the same “issue”? Or is it just me?

9

Yeah, that’s an error on my part. For some reason I thought the UI providing more details than simply the alert text. As far as typos go, that’s one way to know it’s not LLM output :slight_smile:

1 Like
10 
    text = (
        "One or more SMB users do not have valid SMB password hashes. This can happen if the the TrueNAS configuration "
        "was restored without the secret seed. This can also happen if an SMB user was created with an empty password "
        "in an older version of TrueNAS. To correct this, do one of these steps: reset the user password in the TrueNAS "
        "UI or API, disable SMB access for the user. Affected users: %(entries)s"
    )

Is that error message sufficiently clear?

11

UI or API, or disable SMB access for the user. would be most clear.

3 Likes
12

An unordered list would be good, but that may not be doable in the alert.
If not possible, adding that well placed “or” is a good alternative.

1 Like