Wazuh dashboard server is not ready yet

[Idan Abramovich]

Hi all , 

Need your help please.

I've used the official guide to install Wazuh.The machine is based on GCP vm (ubuntu server )

When I try to access the dashboard from the external IP and that's message I get.

Please your help?

[Carlos Ezequiel Bordon]

Hello Idan, can you tell me what type of installation you are trying to perform? Distributed or All-In-One?
What documentation are you following for that installation?Regarding the error you are receiving, this usually occurs when Wazuh dashboard is not being able to connect with Wazuh indexer, so you should check:
- Wazuh indexer is up
- Validate possible errors in the Wazuh indexer logs: cat /var/log/wazuh-indexer/wazuh-cluster.log
- Check that you have correctly configured the certificates in the different components of the stack: https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/step-by-step.html#certificates-creation
- Verify that the Wazuh dashboard configuration file has the correct Wazuh indexer IP (in case they are on different nodes):
 /etc/wazuh-dashboard/opensearch_dashboards.yml:
    opensearch.hosts: https://<wazuh-indexer-ip>:9200
- If the components are in different nodes, validate that you have connectivity between the Wazuh dashboard node and the Wazuh indexer node:
    curl -v telnet://<wazuh-indexer-ip>:9200

I await your comments to be able to give you more precise help.

[Nik Andreevich]

Hello everybody. I'v got same error with wazuh 4.3.6 deployed in docker. 

My wazuh is run behind nginx. I add network in docker-compose.yml file and create 2 networks: External for dashboard and nginx, Internal for dashboard, indexer and manager.

If I add manager to external network I got another error "too_many_redirects"
How to configure wazuh behind nginx reverse-proxy? 

Thanks!

среда, 22 июня 2022 г. в 16:29:16 UTC+3, carlos...@wazuh.com:

[Juan Carlos Tello]

Hello Nik,

As my colleague Carlos mentioned, the "Wazuh dashboard server is not ready yet" is observed when your browser can reach the Wazuh Dashboard (formerly Kibana) but the Dashboard cannot reach the Indexer (formerly Elasticsearch).

Since they are in an internal network, communication should not be an issue. If this is an all-in-one setup done using the official containers, the wazuh-dashboard container is configured to communicate with the wazuh.indexer as shown here: https://github.com/wazuh/wazuh-docker/blob/v4.3.6/single-node/config/wazuh_dashboard/opensearch_dashboards.yml#L3

I recommend verifying connectivity to the Wazuh Indexer API both from inside the Indexer container and the Dashboard container to determine whether the issue is within the Indexer container or a network issue.

Finally, if you want to use NGINX, it used to be that the WUI did not have free-to-use authentication, so we provided this documentation on how to configure an nginx reverse-proxy for the web interface which you may find useful: https://documentation.wazuh.com/3.13/installation-guide/installing-elastic-stack/protect-installation/kibana_ssl.html and in fact you may find the official containers from that version using nginx: https://github.com/wazuh/wazuh-docker/blob/v3.13.4_7.9.2/nginx/config/entrypoint.sh

Let us know if there's any other question we can help with.

Best Regards,

Juan C. Tello

--
You received this message because you are subscribed to the Google Groups "Wazuh mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wazuh/a7a78b47-6ec0-4f4d-a17c-6e4be050f9cen%40googlegroups.com.