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.
Let's encrypt autorenew problem
Let's encrypt autorenew problem
I'm using proxy_pass with SSL Letsencrypt (auto renew) api.domain.com.nginx.ssl.conf with 2 configurations like this, port 8888 i have a Java Spring Boot application:
location / {
proxy_pass http://134.209.170.XXX:8888;
location @fallback {
proxy_pass http://134.209.170.XXX:8888;
This works fine with the redirect request from api.domain.com.... to the spring boot app but i dont know why this configuration is losed and changed to https with different port #####, i think this occurs when my letsencrypt certbot renew the certificate, is there any way to avoid this change to default values ? or other way to avoid manual configuration each certain time.
Thanks a lot
location / {
proxy_pass http://134.209.170.XXX:8888;
location @fallback {
proxy_pass http://134.209.170.XXX:8888;
This works fine with the redirect request from api.domain.com.... to the spring boot app but i dont know why this configuration is losed and changed to https with different port #####, i think this occurs when my letsencrypt certbot renew the certificate, is there any way to avoid this change to default values ? or other way to avoid manual configuration each certain time.
Thanks a lot
Re: Let's encrypt autorenew problem
May be can help some .well-know location, something separete one from app?
Re: Let's encrypt autorenew problem
I don't understand the posible solution
Re: Let's encrypt autorenew problem
Something like this for your domain config :
root folder may be changed
Code: Select all
location /.well-known {
root /var/www/html;
}