Re: "statusCode": 500, "error": "Internal Server Error",

[Santiago Padilla Alvarez]

Hi,

Assuming you have an All-in-one environment, the first thing would be to check that the command:

/usr/share/wazuh-indexer/plugins/opensearch-security/tools/wazuh-passwords-tool.sh --api --change-all --admin-user wazuh --admin-password wazuh

to change passwords has been running correctly, did you get the output with the password changes?

You can restart the components with the following commands:
systemctl restart wazuh-manager
systemctl restart wazuh-indexer
systemctl restart wazuh-dashboard
systemctl restart filebeat

In case all of the above is correct and you are still getting the error, let's check the logs to see what is going on by checking the following:

journalctl -u wazuh-dashboard.service
filebeat test output
systemctl status wazuh-indexer

Hopefully with these steps you can figure out exactly what is going on,
any news let us know!
Best regards!

On Friday, August 9, 2024 at 1:16:06 PM UTC+2 Dominik Górniak wrote:

After positive "off-line WAZUH instalation " I I did the last stage of the installation: "Securing your Wazuh installation - Distributed deployment" with instruction from site "https://documentation.wazuh.com/current/deployment-options/offline-installation.html".

Even if you follow the instructions several times, you always get the same Wazuh-Dashboard error:{
    "statusCode": 500,
    "error": "Internal Server Error",
    "message": "An internal server error occurred."
}

[Santiago Padilla Alvarez]

Hi,

the first steps seem correct but the last step I see is step 3:

echo <ADMIN_PASSWORD> | filebeat keystore add password --stdin --force

after that have you done step 4 of restarting filebeat?
with systemctl restart filebeat

Once you have done that you have to continue with steps 5, 6 and 7 at the end of the this documentation

Have you been able to do all 7 steps without any problem?

I look forward to hearing from you, regards!

On Friday, August 9, 2024 at 1:56:30 PM UTC+2 Dominik Górniak wrote:

My Wazuh instalation  is "1-Node instalation" with structure Wazuh Indexer (Serwer-1, IP 192.168.131.200) Wazuh Manger (Serwer-2, IP 192.168.131.201), Wazuh Dashboard (Serwer-2, IP 192.168.131.201). Serwers Operating Systems  are Ubuntu 24.04 LTS Serwer.
https://groups.google.com/g/wazuh/c/tOHFILyvpHc

piątek, 9 sierpnia 2024 o 13:54:11 UTC+2 Dominik Górniak napisał(a):

All steps i describe  on www site:  https://github.com/wazuh/wazuh/discussions/25120

[Adam Nowak]

As you wrote earlier, in order for the Wazuh 1-Node to start after password protection, you need to - reset all modules in a specific order:

systemctl restart wazuh-manager
systemctl restart wazuh-indexer
systemctl restart wazuh-dashboard
systemctl restart filebeat

Thank you very much for helping me diagnose and solve the problem. Best regards and have a nice weekend.