Closed mitchblank closed 3 years ago
SSL cert is fine, but nginx is returning a 502 error:
curl -v https://projects.gw-computing.net/projects/dfc * Trying 37.59.30.58:443... * Connected to projects.gw-computing.net (37.59.30.58) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /usr/local/etc/openssl@1.1/cert.pem * CApath: /usr/local/etc/openssl@1.1/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN, server accepted to use http/1.1 * Server certificate: * subject: CN=projects.gw-computing.net * start date: Nov 9 18:29:01 2020 GMT * expire date: Feb 7 18:29:01 2021 GMT * subjectAltName: host "projects.gw-computing.net" matched cert's "projects.gw-computing.net" * issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3 * SSL certificate verify ok. > GET /projects/dfc HTTP/1.1 > Host: projects.gw-computing.net > User-Agent: curl/7.74.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 502 Bad Gateway < Server: nginx < Date: Fri, 25 Dec 2020 08:58:45 GMT < Content-Type: text/html; charset=UTF-8 < Content-Length: 150 < Connection: keep-alive < <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx</center> </body> </html>
Thanks for the heads-up, the problem should be resolved now.
SSL cert is fine, but nginx is returning a 502 error: