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.
SSL update problem
SSL update problem
Hello!
This is my very first topic! :)
I have a problem with SSL update (v-update-letsencrypt-ssl).
When cron job runs v-update-letsencrypt-ssl command, for all https domain redirect to domain.tld/login (VestCP login) page, but http works fine.
Vesta CP: v0.9.8-23
Ubuntu 18.04
nginx+apache
This is my very first topic! :)
I have a problem with SSL update (v-update-letsencrypt-ssl).
When cron job runs v-update-letsencrypt-ssl command, for all https domain redirect to domain.tld/login (VestCP login) page, but http works fine.
Vesta CP: v0.9.8-23
Ubuntu 18.04
nginx+apache
Re: SSL update problem
Can you check your apache config files in ~/conf/web/domain.tlf.apache.ssl.conf ?
If you don't know what to do please paste it here.
If you don't know what to do please paste it here.
Re: SSL update problem
Thank you!
In ~/conf/web/domain.tlf.apache.ssl.conf:
<VirtualHost IP:PORT>
Port was wrong, it was my custom Vesta CP login port and not 8443.
In domain.tld.nginx.ssl.conf:
location / {
proxy_pass https://IP:PORT ----- Wrong Port, it was my custom Vesta CP login port...
}
location @fallback {
proxy_pass https://IP:PORT ----- Wrong Port, it was my custom Vesta CP login port...
}
I corrected it to port 8443, now all working fine, but when I add a new domain or make an ssl update, it will be added with the wrong port.
Why use it my custom Vesta CP login port insted of 8443?
I checked nginx template file (/usr/local/vesta/data/templates/web/nginx/default.stpl) there is a variable "web_ssl_port". Where can I set this variable, because it is wrong, it is my custom Vesta CP port instead of 8443.