This guide provides solutions to common issues you may encounter with the Wazuh dashboard, along with diagnostic procedures and troubleshooting steps.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/wazuh/wazuh-dashboard-plugins/llms.txt
Use this file to discover all available pages before exploring further.
Common Error Messages
Filter Could Not Be Created
Error Message:cluster.name in the alerts case or wazuh.cluster.name in the inventories data) cannot be created because the required information is not available. The required data to create the filter is stored in the clusterInfo cookie in the client browser.
Cause: The cookie is not set or the server API information could not be obtained.
Solutions:
- Verify a server API is selected in the selector of the dashboard header
- Ensure the server API is online and reachable:
- Check the server API configuration in
opensearch_dashboards.yml:
-
Confirm the
clusterInfocookie is set in the browser:- Open browser developer tools (F12)
- Navigate to Application/Storage > Cookies
- Check for
clusterInfocookie
- Clear browser cookies and cache, then refresh and reselect the API
Index Pattern Not Found
Error Message:-
Check if the index pattern exists:
- Navigate to Dashboard Management > Index Patterns
- Look for the specified index pattern ID or title
-
Create the index pattern if missing:
- Go to Dashboard Management > Index Patterns
- Click Create index pattern
- Enter the pattern name (e.g.,
wazuh-events*) - Select the time field (
timestamp) - Click Create
- Verify matching indices exist:
-
If no matching indices exist, check:
- Data collection is enabled on agents
- Filebeat/Logstash is running and configured correctly
- Indexer is receiving data
- Review server and indexer logs for ingestion issues
-
Run Health Check to recreate default index patterns:
- Navigate to Management > Health Check
- Click Check to regenerate missing resources
Server API Not Available
Error Message:- Server API host is not reachable from the dashboard host
- Network problem (firewall, routing issue)
- Server API is down or stopped
- Wrong server API host configuration (URL, port, or credentials)
- Ensure the server API is running:
- Verify API is responding:
- Check network connectivity:
- Review firewall rules:
- Verify API configuration in dashboard:
- Check API credentials:
- Review API logs on the manager:
No Server API Selected
Error Message:currentApi cookie in the browser.
Cause: The currentApi cookie is not set or has a falsy value.
Solutions:
- Select a server API using the selector in the dashboard header
-
Verify server API is configured:
- Navigate to Server APIs management
- Ensure at least one API is configured and reachable
-
Check browser cookies:
- Open developer tools (F12)
- Navigate to Application/Storage > Cookies
- Verify
currentApicookie exists
- Clear browser cookies and cache, then refresh and select an API
-
Verify API configuration in
opensearch_dashboards.yml:
Connection Issues
Dashboard Cannot Connect to Indexer
Symptoms:- Dashboard fails to start
- Error: “Unable to connect to OpenSearch”
- Saved objects not loading
- Verify indexer is running:
- Check indexer connection settings in
opensearch_dashboards.yml:
- Verify SSL certificates:
- Review dashboard logs:
- Check network connectivity between dashboard and indexer
Dashboard Cannot Connect to Wazuh API
Symptoms:- “Wazuh API is not reachable” message
- Agent information not loading
- Health check fails on API connection
- Verify manager is running:
- Test API manually:
- Check API configuration in dashboard:
- Verify API credentials:
- Check firewall rules (see Server API Not Available section)
- Review API logs:
Service Issues
Dashboard Service Fails to Start
Symptoms:- Service fails immediately after starting
- Service shows as “failed” status
- Check service status:
- Review service logs:
- Check dashboard logs:
- Verify configuration syntax:
- Check file permissions:
- Verify port availability:
- Check disk space:
Dashboard Service Crashes
Symptoms:- Service starts but crashes shortly after
- Intermittent service failures
- Monitor logs in real-time:
- Check for memory issues:
- Increase Node.js memory limit:
- Check for plugin conflicts:
- Review system resources:
Authentication and Authorization Issues
Login Failures
Symptoms:- Unable to log in to dashboard
- “Invalid credentials” errors
- Verify credentials with direct indexer access:
- Check authentication configuration:
- Reset user password if needed (on indexer):
- Check security plugin configuration on indexer
Permission Denied Errors
Symptoms:- Actions fail with permission errors
- “Insufficient permissions” messages
-
Verify user roles in OpenSearch Dashboards:
- Navigate to Security > Roles
- Check user’s assigned roles
- Review API user permissions:
- Check RBAC configuration for API access
- Verify run_as setting in API configuration:
Data and Display Issues
No Data Displayed
Symptoms:- Dashboards show “No results found”
- Event tables are empty
- Visualizations show no data
-
Check time range:
- Expand time range to include expected data
- Verify data exists in the selected time period
- Verify indices exist and contain data:
-
Check index pattern:
- Verify correct index pattern is selected
- Refresh index pattern field list
- Recreate index pattern if necessary
-
Review applied filters:
- Clear all filters and retry
- Check for conflicting filters
- Verify agent is sending data:
Visualizations Not Loading
Symptoms:- Visualizations show errors or fail to render
- Dashboards partially load
- Check browser console for JavaScript errors (F12)
- Clear browser cache and reload
- Verify index pattern is valid and has data
- Check visualization queries for syntax errors
- Review dashboard logs:
- Regenerate visualizations through Health Check
Saved Objects Missing
Symptoms:- Dashboards or visualizations disappeared
- Recently created objects not found
- Check tenant/space selection (if using multi-tenancy)
-
Search for objects:
- Navigate to Dashboard Management > Saved Objects
- Search by name or type
- Import from backup if available
- Check indexer for saved objects:
- Run Health Check to recreate default objects
Performance Issues
Slow Dashboard Performance
Symptoms:- Dashboard loads slowly
- Queries take a long time
- UI is unresponsive
- Reduce time range for queries
- Apply filters before loading data
- Check system resources:
- Optimize indexer:
- Review slow queries:
- Increase dashboard timeout:
- Clear browser cache and restart browser
High Memory Usage
Symptoms:- Dashboard consumes excessive memory
- System becomes slow
- Out of memory errors
- Check memory usage:
- Increase Node.js memory:
- Restart dashboard service:
- Close unnecessary visualizations
- Reduce concurrent queries
Plugin Issues
Plugin Errors
Symptoms:- Plugin fails to load
- Plugin-specific features not working
- List installed plugins:
- Check plugin compatibility:
- Remove and reinstall plugin:
- Clear optimization cache:
- Check plugin logs in dashboard logs
Upgrade and Migration Issues
Upgrade Failures
Symptoms:- Package upgrade fails
- Service fails after upgrade
- Check package manager logs:
- Verify package integrity:
- Review upgrade logs
- Check for outdated plugins (see Plugin Issues)
- Restore from backup if necessary
Migration Issues
Symptoms:- Configuration not working after migration
- Features missing after migration
- Review migration guide for breaking changes
-
Check configuration migration:
- Verify settings moved from
wazuh.ymltoopensearch_dashboards.yml - Update index patterns
- Review deprecated settings
- Verify settings moved from
- Run Health Check to recreate resources
- Import saved objects from backup
Diagnostic Commands
Collect System Information
Export Logs for Support
Getting Help
Community Support
- Community forum: https://groups.google.com/g/wazuh
- GitHub issues: https://github.com/wazuh/wazuh-dashboard-plugins/issues
- Documentation: https://documentation.wazuh.com/
Reporting Issues
When reporting issues, include:- Wazuh version (dashboard, manager, indexer)
- Operating system and version
- Error messages (complete and unedited)
- Relevant logs (sanitized for sensitive data)
- Steps to reproduce the issue
- Expected vs actual behavior
- Recent changes (upgrades, configuration changes)