I recently installed Checkmk 2.4.0p7 and created a new site. The web login with the default user cmkadmin does not work.
Here’s what I’ve checked so far:
The user cmkadmin exists
In cached_profile.mk, 'locked': False is set
I’ve reset the password multiple times using cmk-passwd cmkadmin → no effect
There is no automation.secret file in the user folder
Restarted the site multiple times using omd restart
Tried different browsers and incognito mode
Still, I always get the same error message when trying to log in:
Login failed for username: cmkadmin (existing: Yes, locked: No, failed logins until locked: 0)
I’ve already searched the forum and tried all common suggestions (resetting password, checking user lock state, clearing browser cache, etc.), but nothing has worked so far.
Could this be a bug in the current version or am I missing a step after site creation?
I’d appreciate any help!
I’m also impacted by this. Seems to be broken. Even when essentially copy pasting the exact command out of the docs, after clearing the volume, no password is shown, and like OP resetting the password seems to have no impact.
┌[14:36:43] [azelphur☮azelphur-server]-(~/Docker/check_mk)-[master*]-
└> docker stop monitoring
monitoring
┌[14:36:56] [azelphur☮azelphur-server]-(~/Docker/check_mk)-[master*]-
└> docker container rm monitoring
monitoring
┌[14:36:59] [azelphur☮azelphur-server]-(~/Docker/check_mk)-[master*]-
└> docker volume rm monitoring
monitoring
┌[14:37:04] [azelphur☮azelphur-server]-(~/Docker/check_mk)-[master*]-
└> docker container run -it -p 8085:5000 -p 8110:8000 \
--tmpfs /opt/omd/sites/cmk/tmp:uid=1000,gid=1000 \
-v monitoring:/omd/sites --name monitoring -v /etc/localtime:/etc/localtime:ro \
--restart always checkmk/check-mk-raw:2.4.0-latest
### CREATING SITE 'cmk'
Adding /opt/omd/sites/cmk/tmp to /etc/fstab.
Going to set TMPFS to off.
Updating core configuration...
Generating configuration for core (type nagios)...
Precompiling host checks...OK
Executing post-create script "01_create-sample-config.py"...OK
Executing post-create script "02_cmk-compute-api-spec"...OK
Executing post-create script "03_message-broker-certs"...OK
Skipping Apache restart.
WARNING: You have to execute 'omd update-apache-config cmk' as root to update and apply the configuration of the system apache.
WARNING: You have to execute 'omd update-apache-config cmk' as root to update and apply the configuration of the system apache.
### STARTING XINETD
* Starting internet superserver xinetd [ OK ]
### STARTING SITE
Starting agent-receiver...OK
Starting mkeventd...OK
Starting rrdcached...OK
Starting redis...OK
Starting npcd...OK
Starting automation-helper...OK
Starting ui-job-scheduler...OK
Starting nagios...OK
Starting apache...OK
Starting crontab...OK
### STARTING CRON
### CONTAINER STARTED
I would strongly discourage to use daily builds for any other things than testing.
Is this problem also happen on your system with release builds?
But for the problem i checked with the current daily build and had no problem to set the cmkadmin password to something.
I would strongly discourage to use daily builds for any other things than testing.
My post was using check-mk-raw:2.4.0-latest, which is what the documentation says to use - so there may be a documentation problem here, if we are not supposed to use that version.
The “latest” tag points not to a daily build only patch releases.
In your case the latest should install p07.
Then yea, it’s broken in 2.4.0-latest, as per my post above, you can copy and paste what I did and you should be able to replicate the issue, if you run the exact commands above, the username/password are not logged and thus we have no way to login as we do not have credentials. If you also run the same commands but use the 2.4.0-2025.07.04 tag, it works and correctly logs the credentials.
I resolved it for myself by downgrading to 2.4.0-2025.07.04, then it does log the password. I’m then able to upgrade to 2.4.0-latest and login. So for me the problem is resolved, but it does seem like it’s broken in the release version.
I’m also running into this issue. Some of the suggested workarounds “htpasswd -m ~/etc/htpasswd cmkadmin” did not work as the htpasswd file did not even exist. I tried with “-c” to create it, but no joy so far. It created the file, but login continued to fail even with a restart of the container.