You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have followed your setup guide to a single node Server Instance just like in the docs. The only thi I added was the IP-Address of the Ubuntu 22.04 VM where Wazuh should reside.
After that, the installation went smoothly, and I can use the admin-Password at the end to log into the new dashboard via web browser and HTTPS. Right after that, there's a warning displayed:
the Wazuh API-Details show, that the API has invalid credentials:
INFO: Current API id [default]
INFO: Checking current API id [default]...
INFO: Current API id [default] has some problem: 3002 - Request failed with status code 403
INFO: Getting API hosts...
INFO: API hosts found: 1
INFO: Checking API host id [default]...
INFO: Could not connect to API id [default]: 3099 - ERROR3099 - Limit of login attempts reached. The current IP has been blocked due to a high number of login attempts
INFO: Removed [navigate] cookie
ERROR: No API available to connect
I didn't change these values at any time. The curl-command in the indexer-part worked fine with the password, the output gave at the end of the indexer-installation.
Another error seems to be in the "" section:
INFO: Index pattern id in cookie: yes [wazuh-alerts-*]
INFO: Getting list of valid index patterns...
INFO: Valid index patterns found: 1
INFO: Found default index pattern with title [wazuh-alerts-*]: yes
INFO: Checking the app default pattern exists: id [wazuh-alerts-*]...
INFO: Default pattern with id [wazuh-alerts-*] exists: yes
ACTION: Default pattern id [wazuh-alerts-*] set as default index pattern
INFO: Checking the index pattern id [wazuh-alerts-*] exists...
INFO: Index pattern id exists [wazuh-alerts-*]: yes
INFO: Index pattern id in cookie: yes [wazuh-alerts-*]
INFO: Checking if the index pattern id [wazuh-alerts-*] exists...
INFO: Index pattern id [wazuh-alerts-*] found: yes title [wazuh-alerts-*]
INFO: Checking if exists a template compatible with the index pattern title [wazuh-alerts-*]
INFO: Template found for the selected index-pattern title [wazuh-alerts-*]: yes
INFO: Index pattern id in cookie: [wazuh-alerts-*]
INFO: Getting index pattern data [wazuh-alerts-*]...
INFO: Index pattern data found: [yes]
INFO: Refreshing index pattern fields: title [wazuh-alerts-*], id [wazuh-alerts-*]...
ACTION: Refreshed index pattern fields: title [wazuh-alerts-*], id [wazuh-alerts-*]
INFO: Getting settings...
INFO: Check Wazuh dashboard setting [timeline:max_buckets]: 200000
INFO: App setting [timeline:max_buckets]: 200000
INFO: Settings mismatch [timeline:max_buckets]: no
INFO: Getting settings...
INFO: Check Wazuh dashboard setting [metaFields]: ["_source","_index"]
INFO: App setting [metaFields]: ["_source","_index"]
INFO: Settings mismatch [metaFields]: no
INFO: Getting settings...
INFO: Check Wazuh dashboard setting [timepicker:timeDefaults]: {"from":"now-24h","to":"now"}
INFO: App setting [timepicker:timeDefaults]: "{\"from\":\"now-24h\",\"to\":\"now\"}"
INFO: Settings mismatch [timepicker:timeDefaults]: no
When I click on the button Go to Settings` I see the guide to check the status of the service
And the defined credentials for wazuh-ui, which match the output I saw within the wazuh-install-files.tar file.
I saw these issue popping up already here #2115 and here #2111. At least the last one is way older than the release 4.7.0 I am using right now.
Since I'm not a Developer, rather a sysadmin desperately needing this awesome tool to work, I don't know ow to debug the API with the curl command like suggested here
The text was updated successfully, but these errors were encountered:
I have followed your setup guide to a single node Server Instance just like in the docs. The only thi I added was the IP-Address of the Ubuntu 22.04 VM where Wazuh should reside.
After that, the installation went smoothly, and I can use the admin-Password at the end to log into the new dashboard via web browser and HTTPS. Right after that, there's a warning displayed:
the Wazuh API-Details show, that the API has invalid credentials:
I didn't change these values at any time. The curl-command in the indexer-part worked fine with the password, the output gave at the end of the indexer-installation.
Another error seems to be in the "" section:
When I click on the button
Goto Settings` I see the guide to check the status of the serviceAnd the defined credentials for wazuh-ui, which match the output I saw within the
wazuh-install-files.tarfile.I saw these issue popping up already here #2115 and here #2111. At least the last one is way older than the release 4.7.0 I am using right now.
Since I'm not a Developer, rather a sysadmin desperately needing this awesome tool to work, I don't know ow to debug the API with the curl command like suggested here
The text was updated successfully, but these errors were encountered: