Effectively it was necessary to restart gunicorn every time that I modify the file urls.py so that the changes take effect. I did not know that. I did it like that: $ systemctl daemon-reload $ systemctl restart gunicorn Thanks for the help.by Frank_Mascarell - Nginx Mailing List - English
I've also tried adding "/" and throwing the same error. I have also added to the .conf file: location = / { include proxy_params; proxy_pass http://unix:/run/gunicorn.sock; } before the fragment location / {......} with the same error. This error is very strange. The configuration is very simple, but I can not find the problem.by Frank_Mascarell - Nginx Mailing List - English
I'm testing Nginx with a django application, the requests https://15.15.15.15/admin/ and https://15.15.15.15/inicio/ work correctly, but https://15.15.15.15/ throw error "Not found: The requested URL / was not found on this server. ", And I can not find the error. This is the configuration: server{ #Configuracion SSL listen 443 ssl http2; listen [::]:443 ssl http2;by Frank_Mascarell - Nginx Mailing List - English
Greetings, I think my days of suffering are over. After reading hundreds of logs, I found the problem. An update of Whitenoise to 4.0 where you must change the shape of the configuration, caused that with my old configuration the gunicorn service will throw errors. The rest is all right. http://whitenoise.evans.io/en/stable/django.html#django-middleware Francis Daly thanks for the help. Gooby Frank_Mascarell - Nginx Mailing List - English
root@BaseVPS-ubuntu1804-django20:~# curl -v https://15.15.15.15/test * Trying 15.15.15.15... * TCP_NODELAY set * Connected to 15.15.15.15 (15.15.15.15) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.2 (OUT), TLS handshake, Client hello (1): * TLSby Frank_Mascarell - Nginx Mailing List - English
It has also tried the proxy_passs an http, with the same error. This is like finding a needle in a pocket: stressful and disappointing. root@BaseVPS-ubuntu1804-django20:~# systemctl status gunicorn ● gunicorn.service - gunicorn daemon Loaded: loaded (/etc/systemd/system/gunicorn.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-09-05 20:3by Frank_Mascarell - Nginx Mailing List - English
I have a VPS on Digital Ocean with Ubuntu 18.04, Nginx, Gunicorn, Django, and a test web application, all configured (ufw) to work with http: 80. Everything works perfectly. Tutorial: https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-18-04#configure-nginx-to-proxy-pass-to-gunicorn Now I modify the file /sites-available/LibrosWeb toby Frank_Mascarell - Nginx Mailing List - English