Wazuh dashboard error after new installation

[Barro Sériba]

Hello Team,

After installing wazuh, I am getting error from the dashboard.

Can you help on this please. 

I cleared the browser and used another one, but the error is still there.

Can you please support?

Version: 2.19.3

Build: 414102

Error: Internal Server Error

    at fetch_Fetch.fetchResponse (https://192.168.101.10/414102/bundles/core/core.entry.js:15:412167)

    at async interceptResponse (https://192.168.101.10  /414102/bundles/core/core.entry.js:15:407040)

    at async https://192.168.101.10  /414102/bundles/core/core.entry.js:15:409874

[Lucio Donda]

Hi there!

To properly help you on solving this issue I'll need more information, something like:
where are you seeing that error? what type of installation did you use ? If this is a fresh start, are the other programs working as expected, this is, manager, indexer and dashboard up and running?
Here's a simple start for Installation options -> https://documentation.wazuh.com/current/installation-guide/index.html 

Besides that we have a troubleshooting guide -> https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/troubleshooting.html
If none of the options there are matching your case, sharing the filtered log files might help us finding the root of the issue.

[Lucio Donda]

When you answer this mail make sure to click on the "reply to all", this way all the users from the community will have access to the process.
I'll paste your answer here to continue:

```
Hello Lucio.

Thank you for your feedback.

After the login process on the dashboard, the error page displays. The error began just around 30 minutes after the installation. I used quickstart installation process.

Just after the installation it was OK, but after sometime, the error occured.

I followed the links but the issue is still present.

If I check the ressource , the /var/lib/wazuh-indexer  storage is 100% use, 0 available space.

Thank you for your support
```

In the quick start installation there's a chart for storage needed

Are you sure that you system matches those limits? 
where you able to check the logs related to indexer / dashboard to make sure that the limited storage is generating this error? 

The path you named holds the information of the alerts and some cleanup can be done there, but if that's happening after 30 minutes It wouldn't be a final solution. How many agents are you registering?