New Nginx template not run node.js app
Posted: Thu Jun 17, 2021 6:54 pm
Hi,
I'm new with Vesta, and I'm trying to run node.js application. But the main problem that there is no any tutorials how to run node.js applications on Vesta cp.
I find out that I have to create a Nginx template, so I created template and added to domain, but nothing happen and I still can't see my application...
Where is my mistakes?
My templates files content:
.tpl file
.stpl file
I'm new with Vesta, and I'm trying to run node.js application. But the main problem that there is no any tutorials how to run node.js applications on Vesta cp.
I find out that I have to create a Nginx template, so I created template and added to domain, but nothing happen and I still can't see my application...
Where is my mistakes?
My templates files content:
.tpl file
Code: Select all
server {
#listen %ip%:%proxy_port%;
listen 194.5.157.109:8086;
#server_name %domain_idn% %alias_idn%;
server_name web.com;
location / {
proxy_pass http://194.5.157.109:8086;
rewrite ^(.*) https://%domain_idn%$1 permanent;
}
include %home%/%user%/conf/web/*nginx.%domain_idn%.conf_letsencrypt;
}
Code: Select all
server {
listen %ip%:%proxy_ssl_port%;
server_name %domain_idn% %alias_idn%;
ssl on;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
location / {
proxy_pass https://%ip%:%web_ssl_port%;
location ~* ^.+\.(%proxy_extentions%)$ {
root %sdocroot%;
access_log /var/log/%web_system%/domains/%domain%.log combined;
access_log /var/log/%web_system%/domains/%domain%.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://%ip%:%web_ssl_port%;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include %home%/%user%/conf/web/*nginx.%domain_idn%.conf_letsencrypt;
include %home%/%user%/conf/web/s%proxy_system%.%domain%.conf*;
}