search

cert-ee / cuckoo3

Cuckoo3 is a Python 3 open source automated malware analysis system.
https://cuckoo-hatch.cert.ee
European Union Public License 1.2
636 stars 82 forks source link

502 Bad Gateway nginx/1.18.0 (Ubuntu) when accessing port 8080 for web after running new install.sh #163

Closed OzzyKampha closed 1 month ago

OzzyKampha commented 1 month ago

Describe the bug 502 Bad Gateway nginx/1.18.0 (Ubuntu) when accessing port 8080 for web

tried curl localhost:8080, same error, bot ngnx and uwsgi service running

To Reproduce run the install.sh on new ubuntu. Try to access web gui, error

Expected behavior The web gui should come up

My Cuckoo version and operating system are:: Cuckoo 3.0.1, Ubuntu 22.04

The log, error, files etc can be found at:

cert-ee-raidar commented 1 month ago

@OzzyKampha Thank you for submitting the bug. Did you run the Quickstart script from the README.md provided link? You mention install.sh script, which is still the old one. What does your nginx error.log say?

OzzyKampha commented 1 month ago

Sorry about that, yes i ran the new quickstart script.

38933#38933: *1 connect() failed (111: Unknown error) while connecting to upstream, client: 127.0.0.1, server: , request: "GET / HTTP/1.1", upstream: "uwsgi://127.0.0.1:9090", host: "localhost:8080"

OzzyKampha commented 1 month ago

I saw that the uwsgi service had exited

cert-ee-raidar commented 1 month ago

Did you get it to work now or still problems with uWSGI? What was the cause of the exit? We did a lot of testing and never came across uWSGI errors. Would be great to know a bit more.

OzzyKampha commented 1 month ago

I got it working, had to restart the service

cert-ee-raidar commented 1 month ago

Good to hear! If you want, you can share extra details. If not, I will close this issue as resolved.

cert-ee-raidar commented 1 month ago

There was a bug in the Quickstart where the uwsgi service was not restarted after enabling the Cuckoo application after symlinking. It should be fixed now.