On Wed, Sep 05, 2018 at 06:51:38PM -0400, Frank_Mascarell wrote: Hi there,
> root@BaseVPS-ubuntu1804-django20:~# curl -v https://15.15.15.15/test > * SSL certificate problem: self signed certificate > * Closing connection 0 > curl: (60) SSL certificate problem: self signed certificate Ok, that's useful. It is not the 502 error, but it is something. This is "the client (curl) does not like the fact that the server is presenting a self-signed certificate". One way to tell the client to accept the certificate is to add " -k" to the command line. However, the older nginx log entry... > 2018/09/05 18:20:12 [error] 3975#3975: *52 connect() to > unix:/run/gunicorn.sock failed (111: Connection refused) while connecting to suggests that at that time, nginx was unable to connect to gunicorn. That is usually a configuration (access control) problem outside of nginx's control; if that problem persists, you may want to check the gunicorn config or logs to see what it thinks is happening. > upstream, client: 139.162.116.133, server: 15.15.15.15, request: "GET / > HTTP/1.1", upstream: "http://unix:/run/gunicorn.sock:/";, host: > "15.15.15.15" Good luck with it, f -- Francis Daly [email protected] _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
