Mismatch between website and server's password hash

[willrun4fun]

I just upgraded to the latest beta today and this is showing up as an alert at the top under a red shield:

Mismatch between website and server's password hash

[Bruce_B · Accepted solution]

We've been able to reproduce a scenario where if you had a Lansweeper 5.x installation with multiple servers, then updated to 6.0 (not 6063), and then updated to 6.0.0.63, you get switched from the old encryption method (without encryption.txt) to the new encryption method. This switch causes password hash errors until all servers are updated and encryption.txt is copied over from the server you updated first to all other Lansweeper servers. In some cases passwords need to be re-entered after this action so they can be re-encrypted.

We're investigating a solution for this so this issue doesn't occur during future Lansweeper updates for installations that went through this scenario (5.x->6.x->6.0.0.63). Do note though that if you're already on 6.0.0.63 and you're experiencing password hash issues, that you will only need to resolve them once, and a future update should not cause this issue to recur.

Our apologies for any inconvenience caused.

[oagtexas]

Same here. Went from 6.0.0.51 to 6.0.0.63 and got hit with all kinds of hash errors. Copying the Encryption file between servers did not help, in fact that file doesn't even seem to exist until after the upgrade (directory was empty on 6.0.0.51.) Manually fixing everything now. Very bad update.

[AdmJLovejoy]

Looks like the Encryption.txt is different on all the scan servers after the upgrade. Copying from web server to all scan servers appears to fix the issue.

First time seeing this issue.

Thanks Bruce

[Bruce_B]

You can follow the instructions in this article to fix password hash errors.

If you have multiple Lansweeper servers all connecting to the same database, do update all of them to version 6.0.0.63 before following the article.

[AdmJLovejoy]

Upgraded to v6063 today and now get this same error. Please advise.

[Michael_V]

This is only a "visual" issue, everything should work as normal.
We will fix this in the next beta.

[ckilmer75]

I've gotten the same error after updating today. My site seems to be working as normal though, other than stating that error.

[tcchit]

Getting the same thing here after updating to v6009.