6.2.2 -> 6.2.4 upgrade - Can't log into frontend

[GilchristT]

Folks

As per the title I've run an upgrade from 6.2.2 to 6.2.4 and now I can't login to the management console. Every attempt gets "Incorrect user name or password or account is temporarily blocked."

My users are all LDAP integrated and I've checked the passwords many times. I also get the same error when trying to connect as Admin.

I see multiple posts about the change from MD5 to BCrypt but that doesn't seem to be applicable in this case. However, I've also tried resetting the Admin password as detailed https://www.zabbix.com/documentation...ssword-hashing but still get the same error logging in with Admin/zabbix

I'm running on Debian 11 with Postgres 14 on the local box.

Zabbix seems to be running as I'm seeing log entries created and I'm getting alerts via the MS Teams connector.

I've been through the zabbix_server.log file, the apache2 logs and the php logs and none are showing any errors or any failed login attempts. I've tried changing the Zabbix logging level to 4 (debugging) but I think there is still nothing relevant although I could be missing something, it's VERY noisy, I'd hate to see 'extended debugging' :-)

Any help appreciated

[bbcorp]

Hi @GilchristT,
I've done the same upgrade and now I can't log into the web interface too.

Does anyone have found a fix for this?

Thanks,

[otheus]

Experiencing something similar with Zabbix 5.0. Changed LDAP bind account & password. Now cannot login. Will update...

[GilchristT]

How I ended up sorting it was to disable LDAP authentication in the database.

The exact steps to do so depend on the type of database you're using but basically you want to set the column 'authentication_type' to 0 in the 'config' table of the database.

If you search the forums for authentication_type you'll find various guides on how to do it.

From my point of view, the confusing thing is that none of my LDAP side servers or accounts changed. I've no idea what the upgrade did to those settings within Zabbix