dashboard 302

[yueqi77]

Describe the bug

Clicking on the dashboard function brings up the upload screen instead

To Reproduce
Steps to reproduce the behavior:

1. EMBArk installation (default mode/docker-mode)
2. Start EMBArk: sudo ./run-server.sh -a
3. Scan a firmware
4. End of firmware scan，Click on the dashboard function (maybe you don't need to perform the firmware scanning task yet, after the installation is completed, you can directly open the web end to click on the dashboard function, because I only went to the dashboard to check the firmware scanning task when it was completed, and realized that it would jump to the upload interface)
5. See error

Expected behavior
Clicking on the dashboard function takes you to the dashboard screen and not to any other function.

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu 22.04.3 LTS

Additional context

Request 302 for dashboard goes to upload, which config file should I give this to and what is the path to that file? How do I change it to make it work? Can you give me some pointers on these issues? Thank you very much!

[BenediktMKuehne]

I implemented a redirect in the case there is no finished firmware analysis yet, since the dashboard would be empty anyway.
I'll look into adding a message on redirect to make that more transparent.

[BenediktMKuehne]

How does your report-page look like when you try the link? Are there finished results?

[yueqi77]

Ohhhh, I see, because I see the logs say that the scanning has been completed, and this is a screenshot of the logs below

Well, when the dashboard jumps all the way to upload, it reports that it's always loading, so it's only when it's in the finished state that the dashboard gets content, right?But now it seems to have failed, I've re-hung a scanning scanning task, how long before the logs show that it's completed how long will the report here be in a completed state?

run_sever.sh just keeps having a warnings.warn message here, does this message cause anything substantial? For example, does it cause the status on the report side to keep loading?

[yueqi77]

I didn't bother with this message anymore when I installed it and went straight to run_sever.sh, will this affect normal use? I won't be able to deal with this (loudly crying face)

[BenediktMKuehne]

Ohhhh, I see, because I see the logs say that the scanning has been completed, and this is a screenshot of the logs below

Well, when the dashboard jumps all the way to upload, it reports that it's always loading, so it's only when it's in the finished state that the dashboard gets content, right?But now it seems to have failed, I've re-hung a scanning scanning task, how long before the logs show that it's completed how long will the report here be in a completed state?

run_sever.sh just keeps having a warnings.warn message here, does this message cause anything substantial? For example, does it cause the status on the report side to keep loading?

I'm seeing the same issue on one of my test-systems this morning, not sure what's going on yet, will keep you updated on that.

[BenediktMKuehne]

I didn't bother with this message anymore when I installed it and went straight to run_sever.sh, will this affect normal use? I won't be able to deal with this (loudly crying face)

Not sure what's going on, but the mysql db docker container or the docker interface it's on appears to not work
maybe sudo docker-compose down && sudo docker-compose up or a sudo systemctl restart docker might help.
the config seems to be fine

[yueqi77]

Ohhhh, I see, because I see the logs say that the scanning has been completed, and this is a screenshot of the logs below
Well, when the dashboard jumps all the way to upload, it reports that it's always loading, so it's only when it's in the finished state that the dashboard gets content, right?But now it seems to have failed, I've re-hung a scanning scanning task, how long before the logs show that it's completed how long will the report here be in a completed state?
run_sever.sh just keeps having a warnings.warn message here, does this message cause anything substantial? For example, does it cause the status on the report side to keep loading?

I'm seeing the same issue on one of my test-systems this morning, not sure what's going on yet, will keep you updated on that.

Okay, thank you very much!

[yueqi77]

I didn't bother with this message anymore when I installed it and went straight to run_sever.sh, will this affect normal use? I won't be able to deal with this (loudly crying face)

Not sure what's going on, but the mysql db docker container or the docker interface it's on appears to not work maybe sudo docker-compose down && sudo docker-compose up or a sudo systemctl restart docker might help. the config seems to be fine

Right now it seems that only the report status side is problematic because it keeps loading, maybe it takes time, I'm waiting for more than 1 hour without a new status update like failed or completed, I'll try the command you posted and restart again!

[BenediktMKuehne]

Testing a fix right now