We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
LetsEncrypt renewal killed nginx config
LetsEncrypt renewal killed nginx config
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?
Anyone else having this issue?
Re: LetsEncrypt renewal killed nginx config
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 :))
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 :))
Re: LetsEncrypt renewal killed nginx config
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.
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.
Re: LetsEncrypt renewal killed nginx config
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.
I had been adding a number of new templates to support http2 etc.
Re: LetsEncrypt renewal killed nginx config
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.
Good idea scorp ... have re-scheduled the cron job.