Error: 3002 - Request failed with status code 400
101 views
Skip to first unread message
Adam Nowak
Aug 20, 2024, 6:23:31 AM8/20/24
to Wazuh | Mailing List
After removing logs folders ("archives, alerts) to new partition I have error in WAZUH-DASHBOARD- Error: 3002 - Request failed with status code 400:
"Error: Error: 3002 - Request failed with status code 400
at WzRequest.genericReq (https://192.168.131.201/48104/bundles/plugin/wazuh/wazuh.plugin.js:1:126595)
at async WzAuthentication.login (https://192.168.131.201/48104/bundles/plugin/wazuh/wazuh.plugin.js:1:164474)
at async refresh (https://192.168.131.201/48104/bundles/plugin/wazuh/wazuh.plugin.js:1:164799)"
My Wazuh instalation is "1-Node instalation" with structure Wazuh Indexer (Server-1, IP 192.168.131.200) Wazuh Manger (Server-2, IP 192.168.131.201), Wazuh Dashboard (Server-2, IP 192.168.131.201). Servers Operating Systems are Ubuntu 24.04 LTS Serwer.
https://groups.google.com/g/wazuh/c/tOHFILyvpHc
https://groups.google.com/g/wazuh/c/tOHFILyvpHc
Mohamed El Amine Gaoudi
Aug 20, 2024, 3:51:47 PM8/20/24
to Wazuh | Mailing List
Hello Adam,
The error code 3002 and the associated message suggest that this could be an authentication issue rather than just a problem with the logs or file paths. Let me try to replicate this error and get back to you ASAP. In the mean time, As a first approach, try clearing your browser cache and cookies or logging in from an incognito window. If the problem persists, check if all the Wazuh services are up and running:
systemctl status wazuh-manager
systemctl status filebeat
systemctl status wazuh-indexer
systemctl status wazuh-dashboard
Check if Filebeat is working as expected by performing a test output:
filebeat test output
If the Wazuh API is running, try to fetch data using the CLI from the Wazuh dashboard server:
Replace the placeholders with your API IP address and Username and password:
curl -k -X GET "https://<api_url>:55000/" -H "Authorization: Bearer $(curl -u <api_user>:<api_password> -k -X POST 'https://<api_url>:55000/security/user/authenticate?raw=true')"
"wazuh-wui:wazuh-wui" are the default credentials.
Lastly share the logs of your dashboard :
grep -i -E "err|warn" cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log
The error code 3002 and the associated message suggest that this could be an authentication issue rather than just a problem with the logs or file paths. Let me try to replicate this error and get back to you ASAP. In the mean time, As a first approach, try clearing your browser cache and cookies or logging in from an incognito window. If the problem persists, check if all the Wazuh services are up and running:
systemctl status wazuh-manager
systemctl status filebeat
systemctl status wazuh-indexer
systemctl status wazuh-dashboard
Check if Filebeat is working as expected by performing a test output:
filebeat test output
If the Wazuh API is running, try to fetch data using the CLI from the Wazuh dashboard server:
Replace the placeholders with your API IP address and Username and password:
curl -k -X GET "https://<api_url>:55000/" -H "Authorization: Bearer $(curl -u <api_user>:<api_password> -k -X POST 'https://<api_url>:55000/security/user/authenticate?raw=true')"
"wazuh-wui:wazuh-wui" are the default credentials.
Lastly share the logs of your dashboard :
grep -i -E "err|warn" cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log
Reply all
Reply to author
Forward
0 new messages