wazuh dashboard server is not ready yet

ELiv 2025

3 min read 06-03-2025

The Wazuh dashboard is a crucial component for visualizing and managing your security monitoring. When you encounter the "Wazuh dashboard server is not ready" error, it can be frustrating. This article will guide you through troubleshooting this issue and getting your Wazuh dashboard back online. We'll cover common causes, step-by-step solutions, and preventative measures.

Understanding the "Wazuh Dashboard Server Not Ready" Error

This error message indicates that the Wazuh API, responsible for communication between the Wazuh manager and the dashboard, is not functioning correctly. This prevents the dashboard from accessing necessary data, resulting in an inability to load. Several factors can contribute to this problem.

Common Causes of the Wazuh Dashboard Server Not Ready Error

API Issues: The most frequent cause is a problem with the Wazuh API itself. This could range from simple configuration errors to more complex software bugs.
Network Connectivity: Ensure the Wazuh manager and dashboard can communicate seamlessly. Firewall rules, network segmentation, or DNS issues can disrupt this communication.
Database Problems: The Wazuh API relies on a database (typically PostgreSQL or MySQL) to store and retrieve data. Database errors, connectivity problems, or insufficient resources can lead to the error.
Wazuh Manager Issues: Problems with the Wazuh manager itself, such as incorrect configuration or a failing service, can prevent the API from functioning correctly.
Resource Exhaustion: If the Wazuh server is overloaded with events or lacks sufficient resources (CPU, memory, disk space), the API may become unresponsive.

Troubleshooting Steps: Resolving the "Wazuh Dashboard Server Not Ready" Error

Let's move on to practical solutions. Remember to check the Wazuh logs (/var/ossec/logs/ on Linux) for more detailed error messages that can pinpoint the problem.

1. Check Wazuh Manager Status

First, ensure the Wazuh manager is running correctly. Use the following commands (on Linux):

systemctl status wazuh-manager

If the service isn't running, start it:

systemctl start wazuh-manager

If it's running but showing errors, investigate those errors within the Wazuh logs.

2. Verify API Connectivity

The Wazuh API usually runs on port 55000. You can use tools like telnet or netcat to test connectivity:

telnet <wazuh-manager-ip> 55000

A successful connection should show a blank screen. If it fails, check your firewall rules to ensure port 55000 is open for inbound traffic to the Wazuh manager.

3. Database Integrity Check

If you're using PostgreSQL, check the database server status and connection. Run commands like psql -U wazuh (replace wazuh with your Wazuh database user) to check for connectivity. Examine the PostgreSQL logs for errors.

4. Resource Monitoring

Check the Wazuh manager's CPU, memory, and disk space usage. High resource utilization can hinder the API's performance. Use tools like top or htop (Linux) to monitor resource consumption. If necessary, consider upgrading your hardware or optimizing Wazuh configuration to reduce resource usage.

5. Wazuh Configuration Review

Carefully review your Wazuh manager and dashboard configurations (/var/ossec/etc/wazuh/wazuh.conf and the dashboard's configuration file, typically located within the dashboard installation directory). Look for any syntax errors, incorrect paths, or misconfigurations that could be impacting the API.

6. Restart Services

After making any configuration changes or resolving other issues, restart both the Wazuh manager and the Wazuh dashboard services. This ensures the changes take effect.

7. Reinstall or Upgrade

If the problem persists, consider reinstalling the Wazuh manager and dashboard. Also check for updates, as a newer version might contain fixes for known issues.

Preventative Measures

Regular Backups: Maintain regular backups of your Wazuh configuration and database. This enables quick restoration in case of issues.
Resource Planning: Allocate sufficient resources (CPU, memory, disk space) to your Wazuh server from the outset.
Monitoring: Continuously monitor the Wazuh manager and dashboard's health using appropriate tools. Early detection of problems is key.
Regular Updates: Stay up-to-date with Wazuh updates to benefit from bug fixes and performance improvements.

By systematically following these steps and implementing preventative measures, you'll significantly improve your chances of quickly resolving the "Wazuh dashboard server is not ready" error and maintaining a smoothly functioning security monitoring system. Remember to consult the official Wazuh documentation for more in-depth information and troubleshooting tips.