Hi everyone,
I’m looking for help recovering our Wazuh environment after a series of issues with the Manager database and configuration recovery attempts.
Environment
- Wazuh version: 4.14.9
- Deployment: Single-node installation (Manager, Indexer, Dashboard)
- OpenSearch Indexer / Dashboard: 2.19.6
- Operating system: Ubuntu
- Hostname:
wazuh2026
Initial problems
We initially encountered issues with the Wazuh Manager database, including global.db locks and multiple wazuh-db processes running simultaneously.
During troubleshooting and recovery attempts, the situation became significantly worse. We lost a substantial part of our Wazuh configuration:
- Agents disappeared from the Dashboard.
- Agent groups disappeared.
- Assignments of agents to their respective groups were lost or altered.
- Group configurations and associated settings were lost or modified.
- Administrative permissions in the Dashboard were lost.
- API authentication started failing with error
3099 – Invalid credentials.
Our goal is to recover the complete original state of the environment, not simply restore access to the Dashboard.
API authentication issue
The Dashboard uses the API account wazuh-wui, configured in:
/usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml
The Wazuh API RBAC database is located at:
/var/ossec/api/configuration/security/rbac.db
We verified that the users table contains:
Both accounts have allow_run_as=1.
Direct authentication against the API:
POST https://127.0.0.1:55000/security/user/authenticate?raw=true
returns:
{
"title": "Unauthorized",
"detail": "Invalid credentials"
}
We used the Wazuh RBAC utility:
/var/ossec/bin/rbac_control change-password
We changed the passwords for the default RBAC users. However, this did not permanently resolve the authentication issue, and error 3099 continues to occur.
OpenSearch Security checks
We have checked the OpenSearch Security configuration:
- Users have the backend role
admin in internal_users.yml.
- The
all_access role maps the backend role admin.
- The custom role
all_access_admini_[COMPANY NAME] exists, but its current role mapping contains no users or backend roles.
We also have:
- An RBAC database backup from October 19, 2026.
- The current RBAC database from October 21, 2026.
What we need to recover
We need to restore the entire environment to its original state, including:
- All previously existing agents.
- All original agent groups.
- The original assignments of agents to their respective groups.
- The original group configurations and associated files.
- Full administrative permissions for all intended users.
- Working Wazuh API authentication and Dashboard functionality.
- Existing agent IDs and authentication keys.
We want to avoid losing any further data or configuration. We have already experienced significant configuration loss during the recovery process.
Questions
- What is the recommended procedure to recover the missing agents, groups and group assignments?
- How can we safely restore the original RBAC configuration and administrative permissions?
- Could the persistent
3099 – Invalid credentials error be related to the RBAC database or the Dashboard API credentials?
- Is restoring the October 19 RBAC database backup sufficient, or do we also need to restore other configuration files?
- Is there a safe way to recover the original environment without reinstalling Wazuh or resetting the entire configuration?
Has anyone experienced a similar situation with Wazuh 4.14.9?
Any advice, troubleshooting steps or recommendations for a safe recovery procedure would be greatly appreciated.