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.
Vesta letsencrypt cert update broke nginx.ssl config
Vesta letsencrypt cert update broke nginx.ssl config
After cron job for letsencrypt updating my ssl nginx conf was totally broken. most part of config dissappeared, it seems like it was backed to original state but with some syntax mistakes. (was missing ";" in some part of code). Is it some problem with regexp in vesta script? And why when cert is being renewed nginx conf files are touched? Shouldn't only cert files be updated?
Re: Vesta letsencrypt cert update broke nginx.ssl config
Faced absolutely the same issue couple of days ago after updating Vesta to 0.9.8-22.
My nginx and apache configs were split by domains.
My hard times were doubled by the fact that Vesta backup for some reason does not back up domain-specific configs (domain.com.nginx.ssl.conf and domain.com.httpd.ssl.conf) and I had to restore them from scratch.
I have disabled v-update-letsencrypt-ssl Cron job but what to do further?
How can this issue be avoided further and how to make backup consider domain configs?
Had no such problems with 0.9.8-20 by the way.
My nginx and apache configs were split by domains.
My hard times were doubled by the fact that Vesta backup for some reason does not back up domain-specific configs (domain.com.nginx.ssl.conf and domain.com.httpd.ssl.conf) and I had to restore them from scratch.
I have disabled v-update-letsencrypt-ssl Cron job but what to do further?
How can this issue be avoided further and how to make backup consider domain configs?
Had no such problems with 0.9.8-20 by the way.
Re: Vesta letsencrypt cert update broke nginx.ssl config
R21 and R22 were only security fixes, I think there was let's encrypt affected change.
Do NOT edit directly the conf files inside of /home/user/conf directory, they are not premanent. If you need to change something create a new template in /usr/local/vesta/data/templates/web/.x-loading wrote: ↑Mon Jul 16, 2018 6:34 amMy nginx and apache configs were split by domains.
My hard times were doubled by the fact that Vesta backup for some reason does not back up domain-specific configs (domain.com.nginx.ssl.conf and domain.com.httpd.ssl.conf) and I had to restore them from scratch.
Check your teamplates, enable the cronjob again and maybe create new ssl certs (untick ssl -> save, tick ssl+let's encrypt -> save).
Don't change the conf files, create new templates.