wazuh-dashboard-plugins icon indicating copy to clipboard operation
wazuh-dashboard-plugins copied to clipboard

Could not connect to API id [default]: 3099 - ERROR3099 - Wazuh not ready yet ||| Could not connect to API id [wazuhapi]: 3099 - ERROR3099 - Invalid credentials

Open Maverick-07 opened this issue 2 years ago • 3 comments

Having the above errors while opening the wazuh manager Please help me

image image

Maverick-07 avatar Jun 05 '22 09:06 Maverick-07

The error state the credentials to access the API are invalid. How did you install Wazuh? Did you use the official documentation guides, the installation assistant or the step-by-step guide? Did you change the default configuration? Can you check the API following this documentation?

gdiazlo avatar Jun 06 '22 08:06 gdiazlo

I am also getting the above error for any modification to the ossec.conf file with the provided script for office365. Here is the addition I am trying to add so far:

<wodle name="command">
  <disabled>no</disabled>
  <command>/var/ossec/etc/scripts/office_365.py --contentType Audit.Exchange Audit.SharePoint DLP.All Audit.General Audit.AzureActiveDirectory --hours 24 --tenantId #### --clientId #### --clientSecret ####</command>
  <interval>24h</interval>
  <ignore_output>yes</ignore_output>
  <run_on_start>yes</run_on_start>
  <timeout>0</timeout>
</wodle>

Here is the guide: https://wazuh.com/blog/monitor-office-365-with-wazuh/

iceman3k avatar Jun 24 '22 21:06 iceman3k

Hello, Thank you for using Wazuh! Could you please confirm what Wazuh version and Elastic Stack are you using? On the other hand, please check the following things: Check all the services are running: systemctl status wazuh-manager (In the wazuh server) systemctl status filebeat (In the wazuh server) systemctl status elastisearch (In the Elasticsearchserver) systemctl status kibana (In the kibana server) Check that you haven’t ran out of space on the Wazuh manager and Elasticsearch. Check the file /usr/share/kibana/data/wazuh/config/wazuh.yml has the contents similar to this:

hosts:
  - default:
     url: https://<your wazuh server ip or localhost if is an all in one>
     port: 55000
     username: wazuh-wui
     password: wazuh-wui
     run_as: false

Aditionally you can do this: Stop the Kibana service : systemctl stop kibana Remove wazuh-registry.json file : rm /usr/share/kibana/data/wazuh/config/wazuh-registry.json Restart the Kibana service so the file will be re-created : systemctl restart kibana Remove the browser cache (cookies, local storage, etc...) Try to access Kibana again Let me know if this is helpful and of any details, Cheers, Matias From Wazuh team.

matiasmoreno876 avatar Jul 04 '22 13:07 matiasmoreno876

Closed due to inactivity.

AlexRuiz7 avatar Oct 26 '22 09:10 AlexRuiz7