Problem when reconfiguring Nginx for SSL with self-signed certificate
francis at daoine.org
Thu Sep 6 07:00:14 UTC 2018
On Wed, Sep 05, 2018 at 06:51:38PM -0400, Frank_Mascarell wrote:
> root at BaseVPS-ubuntu1804-django20:~# curl -v https://188.8.131.52/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: 184.108.40.206, server: 220.127.116.11, request: "GET /
> HTTP/1.1", upstream: "http://unix:/run/gunicorn.sock:/", host:
Good luck with it,
Francis Daly francis at daoine.org
More information about the nginx