The API connections could be down or inaccessible

1,162 views
Skip to first unread message

Aiman

unread,
Sep 11, 2024, 11:37:40 PM9/11/24
to Wazuh | Mailing List
Hi, good morning! 

Recently I have upgraded Wazuh Indexer, Wazuh Manager, and Wazuh Dashboard from 4.8.2 to 4.9.0-2. I followed the steps on the Wazuh Documentation User Manual on Wazuh Upgrade ( Wazuh central components - Upgrade guide · Wazuh documentation ). 

I am able to login to the Wazuh Dashboard but I get these errors:
  • 3099 - ERROR3099 - Invalid credentials
  • Invalid credentials

Screenshot 2024-09-12 110915.png

I have clicked on "Troubleshooting", and followed the suggestion and I see the wazuh-manager is working perfectly fine, the status is green.

Screenshot 2024-09-12 111109.png
 WhatsApp Image 2024-09-12 at 11.13.56_704fdcc7.jpg


Stuti Gupta

unread,
Sep 12, 2024, 2:23:48 AM9/12/24
to Wazuh | Mailing List

Hi  Aiman

This error is mainly due to an invalid credential in the Wazuh dashboard wazuh.yml configuration, where the wazuh-wui user configuration is set.

You can find this configuration at the end of the file in: /usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml

On a basic installation, without changing passwords, you should see something like:

hosts: - default: url: https://localhost port: 55000 username: wazuh-wui password: wazuh-wui run_as: false

This configuration has been obtained from the Wazuh OVA 4.7.4, it is possible that depending on your type of deployment, the password is different, for example, in a deployment through the installation assistant, the passwords are randomized for each user, you can find those passwords in a tar.gz file generated in the same directory where the wazuh-install.sh script has been executed.

Please make sure that the password used is correct, I will be able to give you more concrete steps if you provide more information about your environment and type of deployment.

Hope this helps

Desmond Afreh Obeng

unread,
Oct 7, 2024, 7:53:07 AM10/7/24
to Wazuh | Mailing List
I am experiencing this same API connection issue..  What could  be the cause of this .. Thank you
Reply all
Reply to author
Forward
0 new messages