LetsEncrypt renewal killed nginx config

locus · Post by **locus** » Tue Jun 06, 2017 1:31 am

I had a site do an automatic renewal at 3AM this morning, what was unexpected was when it updated the nginx config for that domain it added an extra "}" effectively blocking the nginx process from starting.
Anyone else having this issue?

scorp13 · Post by **scorp13** » Tue Jun 06, 2017 2:20 pm

Yes, I encountered a similar floating bug. Sometimes in nginx config, sometimes in apache.
At the moment, I just changed time of the LE update script run, to be more ready in case of an error (or at least not to sleep :))

locus · Post by **locus** » Sat Jun 10, 2017 11:16 pm

Ok, this happened again.
It was an extra closing brace "}" last time, this time a brace was missing.
Doing a web rebuild for this user fixes the issue until a LE renewal takes place.

locus · Post by **locus** » Fri Jun 23, 2017 7:38 am

Having a new line at the end of every template file helped resolve this for me.
I had been adding a number of new templates to support http2 etc.

plutocrat · Post by **plutocrat** » Wed Jun 28, 2017 4:49 am

I think I'm having a similar problem. I posted details to viewtopic.php?f=11&t=14851

Good idea scorp ... have re-scheduled the cron job.

Vesta Control Panel - Forum