🛠️ Fixing Wazuh Dashboard Migration Loops

🛠️ Fixing Wazuh Dashboard Migration Loops

If you are seeing the "Wazuh dashboard server is not ready yet" message repeatedly, you are likely stuck in a migration lock. Follow these steps in exact order to break the loop permanently.

Step 1: Stop the Dashboard Service

First, we must halt the service to ensure no active processes are attempting to write to the index.

sudo systemctl stop wazuh-dashboard

Step 2: Clear the Stuck Index

This command removes the "half-finished" or corrupted index that is triggeringcausing the migration lock.

Note: This removes UI configurations but preserves your security alert data.

curl -k -u admin:'3z+Sw?zNjtTCgbvu*UBizozk4HtSkec6' -X DELETE https://localhost:9200/.kibana*

Step 3: Start the Dashboard and InitializeWAIT

Restart the service to begin the fresh index recreation process.

sudo systemctl start wazuh-dashboard

⚠️ The "5-Minute Rule"

Do not refresh your browser for at least 5 minutes.

The dashboard must rebuild dozens of internal visualizations and patterns. If you refresh the page or interrupt the service during this window, the migration lock will return, and you will have to start overrestart from Step 1.