Wazuh dashboard server is not ready yet when upgrade wazuh 4.8

[Owen Dang]

Dear Team,

After upgrade Wazuh Docker from version 4.7.5 to 4.8.0 got this error "Wazuh dashboard server is not ready yet". Please advise me fix this error.

Thanks

[Damian Alfredo Mangold]

Hi, the error message "Wazuh dashboard server is not ready yet" usually indicates that the Wazuh dashboard is taking longer than expected to start. This can be a temporary issue, but it's often related to insufficient server resources or other environmental factors. Here are some steps to help diagnose and resolve the issue:

• Check Server Resources: Ensure that the server running the Wazuh dashboard has sufficient CPU, memory, and disk space. Inadequate resources can delay the startup process.
  • https://documentation.wazuh.com/current/quickstart.html#requirements
• Check Wazuh Logs:
  • Wazuh indexer:
    cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i -E "error|warn"
  • Wazuh manager:
    cat /var/log/filebeat/filebeat | grep -i -E "error|warn"
  • Wazuh dashboard:
    journalctl -u wazuh-dashboard
    cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log | grep -i -E "error|warn"
• Service Status: Verify that all necessary Wazuh services are running correctly. You can use the following commands to check the status:
  systemctl status wazuh-manager
  systemctl status wazuh-dashboard
  systemctl status wazuh-indexer
  systemctl status filebeat
  filebeat test output

Another common problem. Wazuh-indexer may timeout when starting the service and Wazuh-dashboard may not start. This can happen if the service does not start in the time Linux expects it to. We can extend this time with the following steps:

• Execute # systemctl edit wazuh-indexer and add the following lines:
  [Service]
  TimeoutStartSec=180
• Save the file and execute:
  systemctl daemon-reload
  systemctl restart wazuh-indexer
  systemctl restart wazuh-dashboard

Please try these steps and let us know if the issue persists. We are here to assist you further. (edited) 

[RAYHAN ZHARFAN AL GHIFARI]

Hello, my wazuh dashboard 4.8.0 have the same error 

"Wazuh dashboard server is not ready yet"

and after  checking the wazuh logs this is the output. Please help

[Damian Alfredo Mangold]

Hi, RAYHAN ZHARFAN AL GHIFARI

The error message you are seeing in the wazuh-cluster.log file indicates an authentication failure for the Kibana server from the IP address "127.0.0.1:59034". Here are some possible solutions to fix this issue:

1. Check Wazuh server and Wazuh Kibana plugin versions: This error can occur if there is a mismatch between the Wazuh server and the Wazuh Kibana plugin versions.

2. Make sure that both the Wazuh server and the Wazuh Kibana plugin are running the same major and minor versions.

3. Update credentials and configuration: It may be necessary to change the credentials and configuration in the wazuh.yml file. Update the credentials with the correct username and password in the configuration file.

4. Restart Kibana and Elasticsearch: Try restarting both Kibana and Elasticsearch to see if it resolves the authentication issue.

Here more informations about Kibana plugin troubleshooting: https://documentation.wazuh.com/current/user-manual/elasticsearch/troubleshooting.html



If these suggestions do not help resolve your issue, we kindly ask you to create a new inquiry in one of the community channels. This will allow us to follow up on your problem more effectively and ensure that each thread has a specific focus.