Open d4n13l4 opened 6 years ago
that is for cuckoo-mod check this
cuckoo web --nginx
upstream _uwsgi_cuckoo_web {
server unix:/run/uwsgi/app/cuckoo-web/socket;
}
server {
listen localhost:8000;
# Cuckoo Web Interface
location / {
client_max_body_size 1G;
proxy_redirect off;
proxy_set_header X-Forwarded-Proto $scheme;
uwsgi_pass _uwsgi_cuckoo_web;
include uwsgi_params;
}
}
╰─± cuckoo web --uwsgi
[uwsgi]
plugins = python
module = cuckoo.web.web.wsgi
uid = X
gid = X
static-map = /static=/usr/local/lib/python2.7/dist-packages/cuckoo/web/static
# If you're getting errors about the PYTHON_EGG_CACHE, then
# uncomment the following line and add some path that is
# writable from the defined user.
# env = PYTHON_EGG_CACHE=
env = CUCKOO_APP=web
env = CUCKOO_CWD=/home/X/.cuckoo
yes I have both like that
I just tried again and now I got this error "You're accessing the development server over HTTPS, but it only supports HTTP."
from my searches this is a django error but I couldn't find where to change the secure_ssl_direct setting, any hints? @doomedraven @RicoVZ
did you try acceso it on http not https? for start to see fi that works?
same problem here, have Cuckoo working perfectly over HTTP but when using HTTPS I get from cuckoo webserver: You're accessing the development server over HTTPS, but it only supports HTTP.
any ideas?
Hi @ThisIsNotMalware,
Our Cuckoo Sandbox is SSL with Let's Encrypt, try here: https://cuckoo.hanyajasa.com/ Do you want it to?
Hey @ryanbekabe
Thanks for sharing, I'll take a look at Let's Encrypt, was trying to do something like this: https://www.digitalocean.com/community/tutorials/how-to-create-a-self-signed-ssl-certificate-for-nginx-in-ubuntu-16-04
But may not work, no idea.
Edit**
Ive managed to make it work, and have my SSL enabled, but, when I try to submit a sample via SSL the connection will close, any idea?
Hi @ThisIsNotMalware,
Same to me, when upload via SSL, Submit button not working. But SSL from cuckoo.cert.ee working normal. I don't know why.
Update @ryanbekabe I see Cuckoo trying to RST, ACK to port 80. There should be a way to change this to port 443 to make it work over SSL
@ThisIsNotMalware Here same issues: https://github.com/cuckoosandbox/cuckoo/issues/1397 And my web now works for uploading via SSL: https://cuckoo.hanyajasa.com/ Here my stuff: https://github.com/ryanbekabe/cuckoostuff/blob/master/apache_https_sll.conf
SSLEngine on
RequestHeader set X-Forwarded-Proto https
Hi guys, how do you run the cuckoo web interface through https? I just did all the steps described above, but when I run cuckoo web -H IP_address
it says the port is already in use. I know cuckoo runs on port 8000, so just change it in the cukoo-web file.
Here is my setup. please help
# server { listen 8000 default_server; server_name x.x.x.x; return 301 https://$server_name$request_uri; }
server {
# SSL configuration
listen 443 ssl http2 default_server;
listen [::]:443 ssl http2 default_server;
include snippets/self-signed.conf;
include snippets/ssl-params.conf;
i just resolve it :)
My issue is:
I'm trying to make the webserver run with HTTPS, I've installed ngnix as this post suggested https://infosecspeakeasy.org/t/howto-build-a-cuckoo-sandbox/27 my cuckoo file for it is the same except I don't have the # Host the upstream legacy API part nginx is running but when I run cuckoo webserver command it still takes me to HTTP
From what I read there is nothing else to change in the configuration but maybe I'm missing something. Do I have to change the way I'm running the web server? I'm using cuckoo web runserver linux_ip:8080
My Cuckoo version and operating system are:
Linux host 16.04 Windows 7 guest Cuckoo version 2.0.5
/etc/nginx/sites-available/cuckoo