How could updating ssl certs cause node forever to stop?

100 Views Asked by At

I just went through some very strange debugging after running

sudo systemctl stop nginx

sudo /opt/bitnami/letsencrypt/lego --tls --email="..." --domains="..." --path="/opt/bitnami/letsencrypt" renew --days 90

sudo systemctl start nginx

I was getting a 502 error, and many errors of the form

[error] 25208#25208: *1 connect() failed (111: Connection refused) while connecting to upstream, client

I had multiple domains running on this server, but I only updated one of their ssl certs. The other domains were still up, but the one that was updated began erroring out with 502. After endless Google searches, it kept pointing to an IPv6 issue, and changing localhost to 127.0.0.1 in the nginx config, or to a mismatch of ports between nginx and node. It turned out that somehow forever had just stopped, without leaving any indication, e.g. I couldn't find anything from today in ~/.forever. I just want to know if i'm missing anything obvious, this was not the first time that I updated ssl certs, and I did the exact same thing last time without this happening.

0

There are 0 best solutions below