Hey Arham,
Thanks for using Wazuh!
Normally this is resolved by disabling the telemetry in Kibana.
telemetry.enabled: false into the /etc/kibana/kibana.yml file.systemctl restart kibana and try again from a new private (incognito) web page.Let me know if this helped,
John.-
Hello,
Sorry for the delay. When you say that you can’t access Wazuh you mean the WazuhApp in Kibana? Is Kibana UI working? You can check Kibana status and errors with this:
systemctl status kibana --no-pagerjournalctl -u kibana --no-pager | grep -Ei "error|warn|fail|cause"If there’s something wrong with Kibana, could be Elasticsearch is not working ok. To check if Elasticsearch is working, use this:
systemctl status elasticsearch --no-pagercurl -k -u USER:PASSWORD -XGET "https://ELASTIC-IP:9200/_cluster/health?pretty=true"To check if Wazuh is working, use this (in the server):
systemctl status wazuh-manager --no-pager/var/ossec/bin/wazuh-control statusTo check the WazuhAPI, use this:
TOKEN=$(curl -u wazuh-wui:wazuh-wui -k -X GET "https://MANAGER-IP:55000/security/user/authenticate?raw=true")curl -k -X GET "https://MANAGER-IP:55000/?pretty=true" -H "Authorization: Bearer $TOKEN"This new issue doesn’t seem to be related to the initial one.
Let me know the status.
John.-