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.
Force-HTTPS templates - HTTP/HTTPS ports are not getting placed in the Config
-
- Posts: 1
- Joined: Sat Oct 07, 2017 10:47 pm
Force-HTTPS templates - HTTP/HTTPS ports are not getting placed in the Config
when setting the Force-HTTPS templates in NGINX/PHP-FPM, after a restart NGINX won't startup, as HTTP/HTTPS ports are not getting placed in the Config
nginx: [emerg] invalid port in "1.1.1.1:"
server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
location / {
rewrite ^(.*) https://%domain_idn%$1 permanent;
}
include %home%/%user%/conf/web/*nginx.%domain_idn%.conf_letsencrypt;
}
seems %proxy_port% is not placing the port numbers... both stpl and tpl
nginx: [emerg] invalid port in "1.1.1.1:"
server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
location / {
rewrite ^(.*) https://%domain_idn%$1 permanent;
}
include %home%/%user%/conf/web/*nginx.%domain_idn%.conf_letsencrypt;
}
seems %proxy_port% is not placing the port numbers... both stpl and tpl