Deploy wazuh-4.3.8.ova "Wazuh dashboard server is not ready yet"

[TungHo]

Dear ALL,

I had deployed the 4.3.8.ova on VMware, i try  to access the link https://X.X.X.X, but show the error "Wazuh dashboard server is not ready yet".

Anyone can help?

TungHo

[Anthony Faruna]

Hello TungHo

Thank you for using Wazuh

The message "Wazuh-Dashboard server is not ready yet" usually appears when you just started or restarted Wazuh-Dashboard.

It can also be produced for one of the following reasons:

• Your service or Wazuh-dashboard has some error that causes it to constantly reboot.
• Your Indexer service is not up or has some error.

If you have just started the Wazuh-Dashboard service, please wait a few minutes and try again. If this is not the case, then you will have to check the status of the Indexer and dashboard services.Check the status service:
  systemctl status wazuh-indexer
  systemctl status wazuh-dashboard

Please check here also to troubleshoot it more: https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/troubleshooting.html

Restart  the services:
  systemctl restart wazuh-indexer
  systemctl restart wazuh-manager
  systemctl restart filebeat.service
  systemctl restart wazuh-dashboard

Please let me know if this steps resolve the issue 

Best Regards 

[Chun Tung Ho]

Dear Anthony,

i had checked the service, only wauh-indexer is stop.

Anthony Faruna <anthony...@wazuh.com> 於 2022年10月8日 週六 凌晨3:17寫道：

--
You received this message because you are subscribed to a topic in the Google Groups "Wazuh mailing list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/wazuh/DN5SlzUg9zk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to wazuh+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wazuh/0cecc3e5-cb6f-44be-a681-0add04843208n%40googlegroups.com.

[Chun Tung Ho]

Dear ALL,

Anyone can help?

TungHo

Chun Tung Ho <tung...@gmail.com> 於 2022年10月8日 週六 凌晨3:34寫道：

[Anthony Faruna]

Hello Chun

Please apologies for the delay in response, I was not available when you sent your last reply 

Please can you try starting the Wazuh indexer service with systemctl restart wazuh-indexer

 

Also please share output of the  systemctl status wazuh-indexer command 

Best Regards

[Chun Tung Ho]

Dear Anthony,

thanks for your follow-up, i had fixed the problem by using the command "sudo systemctl restart wazuh-indexer".

TungHo

Anthony Faruna <anthony...@wazuh.com> 於 2022年10月11日 週二 凌晨4:54寫道：

[Anthony Faruna]

Hello Chun

It's really great to know the issue has been resolved 

Thanks so much for your patience 

Best Regards

[Abdulaziz Aljaberi]

Dear All, 

i have the same problem accessing WAZUH, i run the commands for restarting the services as below

Restart  the services:
  systemctl restart wazuh-indexer
  systemctl restart wazuh-manager
  systemctl restart filebeat.service
  systemctl restart wazuh-dashboard

for the first time it worked, the second time i got the issue, i had a new problem occurred as per the below 

Failed to restart wazuh-indexer.service: The name org.freedesktop.policykit1 was not provided by any .service files
see system logs and 'systemctl status wazuh-indexer.services' for details 

can you please help how to solve this issue, really appreciate your help.