Thanks for the logs! A couple of checks that could get us closer to identifying the issue:
Try the API directly with the new user (bypasses the Dashboard)
On the Wazuh server, please run:
curl -sk -u '<NEW_USER>':'<NEW_PASSWORD>' \
https://localhost:55000/security/user/authenticate?prettyIf you get a 200 with a token, the user/credentials are valid in the API and the issue should be on the Dashboard side.
If you get a 401, the issue is with the user at the API level (password/activation).
Make sure the Dashboard is pointing to the API you are testing.
Check for this config file: /usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml
The hosts section must define one or more data sources identified by name (e.g., wazuh-test, wazuh-prod). If the data source isn’t identified properly, the login flow may end up with an empty dataSourceId.
Have a look here:
https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/settings.html#hosts
Let me know if this helps.
Kind regards,
On Thursday, October 16, 2025 at 5:55:03 PM UTC-3 Michael Tibbs wrote: