HelioHost Wiki - User contributions [en]

VPS Nodejs

2026-03-12T09:56:12Z

Allo: /* Getting Started */

== Getting Started ==

[[File:vpsnode1.jpg|500px|right]]

In https://heliohost.org/chat/, say you are getting a VPS and would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with PayPal, you may also ask for an alternate payment link.

You should get an email listing your dedicated IP, port, and other info for logging in. You will need an SFTP client such as [https://filezilla-project.org/ FileZilla] to upload files, as well as an SSH client. I personally use and prefer https://termius.com/, because I like the terminal and it doesn't weirdly close for no reason. I also use NMM File Manager from the [https://play.google.com/store/apps/details?id=in.mfile&pli=1 Google Play Store] for editing the files of the server.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

chmod 755 is supposed to work and give only the owner of the file permission to mess with it. But the /src folder is deep in the server and owned by root instead of normal accounts and I couldn't log in as root on nmm that I know of. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

If you can't get to the files, you may need to enter in terminal:

<code>sed -i 's/internal-sftp-server.*/internal-sftp/' /etc/ssh/sshd_config</code>

<code>systemctl restart ssh</code>

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions. It may be handy to know that <code>sudo chmod 777 -R directory</code>, with directory being your target directory, applies the permission to everything in that folder. Tho beware doing that to deeper folders than just your node project. i just did it to /etc and it blew up my whole vps.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

{{Info|You could edit this file to change the entrypoint from app.js to something else like server.js}}

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

{{Info|to run multiple domains, make a template for each. Have your second node project use port 3001 instead of 3000. You would then repeat the steps of touching, chmodding, and editing the three node3000 files, but this time call them node3001 and change the ports mentioned in them from 3000 to 3001. Then, as the template on your second node project, you would select node3001 instead of node3000.}}

[https://wiki.helionet.org/VPS_Domain here]'s what i did next; setting up custom domains.

VPS Nodejs

2025-10-07T19:36:28Z

Allo:

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

chmod 755 is supposed to work and give only the owner of the file permission to mess with it. But the /src folder is deep in the server and owned by root instead of normal accounts and I couldn't log in as root on nmm that I know of. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

If you can't get to the files, you may need to enter in terminal:

<code>sed -i 's/internal-sftp-server.*/internal-sftp/' /etc/ssh/sshd_config</code>

<code>systemctl restart ssh</code>

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions. It may be handy to know that <code>sudo chmod 777 -R directory</code>, with directory being your target directory, applies the permission to everything in that folder. Tho beware doing that to deeper folders than just your node project. i just did it to /etc and it blew up my whole vps.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

{{Info|You could edit this file to change the entrypoint from app.js to something else like server.js}}

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

{{Info|to run multiple domains, make a template for each. Have your second node project use port 3001 instead of 3000. You would then repeat the steps of touching, chmodding, and editing the three node3000 files, but this time call them node3001 and change the ports mentioned in them from 3000 to 3001. Then, as the template on your second node project, you would select node3001 instead of node3000.}}

[https://wiki.helionet.org/VPS_Domain here]'s what i did next; setting up custom domains.

VPS Nodejs

2025-10-07T18:35:38Z

Allo: /* Terminal Stuff */

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

chmod 755 is supposed to work and give only the owner of the file permission to mess with it. But the /src folder is deep in the server and owned by root instead of normal accounts and I couldn't log in as root on nmm that I know of. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

If you can't get to the files, you may need to enter in terminal:

<code>sed -i 's/internal-sftp-server.*/internal-sftp/' /etc/ssh/sshd_config</code>

<code>systemctl restart ssh</code>

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions. It may be handy to know that <code>sudo chmod 777 -R directory</code>, with directory being your target directory, applies the permission to everything in that folder. Tho beware doing that to deeper folders than just your node project. i just did it to /etc and it blew up my whole vps.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

[[File:vpsnode7.jpg]]

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

[https://wiki.helionet.org/VPS_Domain here]'s what i did next; setting up custom domains.

VPS Nodejs

2025-10-07T18:26:49Z

Allo: /* sftp file editing */

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

If you can't get to the files, you may need to enter in terminal:

<code>sed -i 's/internal-sftp-server.*/internal-sftp/' /etc/ssh/sshd_config</code>

<code>systemctl restart ssh</code>

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions. It may be handy to know that <code>sudo chmod 777 -R directory</code>, with directory being your target directory, applies the permission to everything in that folder. Tho beware doing that to deeper folders than just your node project. i just did it to /etc and it blew up my whole vps.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

[[File:vpsnode7.jpg]]

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

[https://wiki.helionet.org/VPS_Domain here]'s what i did next; setting up custom domains.

VPS Nodejs

2025-10-07T18:26:13Z

Allo:

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

If you can't get to the files, you may need to enter in terminal:
<code>sed -i 's/internal-sftp-server.*/internal-sftp/' /etc/ssh/sshd_config</code>
<code>systemctl restart ssh</code>

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions. It may be handy to know that <code>sudo chmod 777 -R directory</code>, with directory being your target directory, applies the permission to everything in that folder. Tho beware doing that to deeper folders than just your node project. i just did it to /etc and it blew up my whole vps.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

[[File:vpsnode7.jpg]]

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

[https://wiki.helionet.org/VPS_Domain here]'s what i did next; setting up custom domains.

VPS Domain

2025-10-06T22:08:28Z

Allo:

Here are two options for domains.

== Setting up Custom Domain via Namecheap ==
Essentially, for namecheap, just follow [https://wiki.helionet.org/Namecheap_DNS_Records this] tutorial and be sure to ask an admin (tell them your domain) to set up your dns if you are using heliohost nameservers. That's really all you need to do.

== Setting up Custom Domain via Cloudflare ==
[[File:customdomain3.jpg]]
First lets set the DNS. Go to the DNS option on the dashboard and then to Records.
[[File:customdomain5.jpg]]
Grab that ipv4 ip from your heliohost email and make an <code>a</code> set to it. Do the same with the ipv6 and <code>aaaa</code>. Also feel free to make a cname telling the internets that the www form of your site also links to it.
[[File:customdomain4.jpg]]
Now in to the hestia control panel go to users, find the user which you have as owner of this domain and hit <code>edit settings</code>.
[[File:customdomain6.jpg]]
Go to advanced settings and change the nameservers to the ones provided by cloudflare like I did here.
[[File:customdomain1.jpg]]
Now back to cloudflare to SSL.
[[File:customdomain2.jpg]]
Set it to Full(Strict) which is apparently the supersecure way.
Now in your hestia control panel, you can go to the user that owns the site, to the site, to the site options, and check SSL and Obtain Your Own.
[[File:Vpsnode3.jpg]]
And with that, your domain should be connected and secure.
{{Info|it may show a warning next to the url for the namecheap site because you are selfcreating your SSL. At least it isn't a real security risk}}

VPS Domain

2025-10-06T22:07:27Z

Allo: /* Setting up Custom Domain via Cloudflare */

== dont look yet im building this page ==
== Setting up Custom Domain via Namecheap ==
Essentially, for namecheap, just follow [https://wiki.helionet.org/Namecheap_DNS_Records this] tutorial and be sure to ask an admin (tell them your domain) to set up your dns if you are using heliohost nameservers. That's really all you need to do.

== Setting up Custom Domain via Cloudflare ==
[[File:customdomain3.jpg]]
First lets set the DNS. Go to the DNS option on the dashboard and then to Records.
[[File:customdomain5.jpg]]
Grab that ipv4 ip from your heliohost email and make an <code>a</code> set to it. Do the same with the ipv6 and <code>aaaa</code>. Also feel free to make a cname telling the internets that the www form of your site also links to it.
[[File:customdomain4.jpg]]
Now in to the hestia control panel go to users, find the user which you have as owner of this domain and hit <code>edit settings</code>.
[[File:customdomain6.jpg]]
Go to advanced settings and change the nameservers to the ones provided by cloudflare like I did here.
[[File:customdomain1.jpg]]
Now back to cloudflare to SSL.
[[File:customdomain2.jpg]]
Set it to Full(Strict) which is apparently the supersecure way.
Now in your hestia control panel, you can go to the user that owns the site, to the site, to the site options, and check SSL and Obtain Your Own.
[[File:Vpsnode3.jpg]]
And with that, your domain should be connected and secure.
{{Info|it may show a warning next to the url for the namecheap site because you are selfcreating your SSL. At least it isn't a real security risk}}

VPS Domain

2025-10-06T22:03:18Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T22:01:59Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T22:00:30Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T21:59:35Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T21:58:53Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T21:57:00Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T21:55:53Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T21:52:55Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Nodejs

2025-10-06T21:50:44Z

Allo:

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions. It may be handy to know that <code>sudo chmod 777 -R directory</code>, with directory being your target directory, applies the permission to everything in that folder. Tho beware doing that to deeper folders than just your node project. i just did it to /etc and it blew up my whole vps.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

[[File:vpsnode7.jpg]]

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

[https://wiki.helionet.org/VPS_Domain here]'s what i did next; setting up custom domains.

File:Customdomain5.jpg

2025-10-06T21:48:56Z

Allo: Allo uploaded a new version of File:Customdomain5.jpg

VPS Domain

2025-10-06T21:47:13Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T21:46:43Z

Allo:

File:Customdomain6.jpg

2025-10-06T21:43:19Z

Allo:

File:Customdomain4.jpg

2025-10-06T21:42:42Z

Allo:

File:Customdomain5.jpg

2025-10-06T21:41:59Z

Allo:

File:Customdomain3.jpg

2025-10-06T21:41:02Z

Allo:

File:Customdomain2.jpg

2025-10-06T21:40:28Z

Allo:

File:Customdomain1.jpg

2025-10-06T21:39:37Z

Allo:

VPS Nodejs

2025-10-06T21:11:36Z

Allo: /* sftp file editing */

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions. It may be handy to know that <code>sudo chmod 777 -R directory</code>, with directory being your target directory, applies the permission to everything in that folder. Tho beware doing that to deeper folders than just your node project. i just did it to /etc and it blew up my whole vps.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

[[File:vpsnode7.jpg]]

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

VPS Domain

2025-10-06T19:53:01Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T19:50:12Z

Allo: /* Setting up Custom Domain via Cloudflare */

VPS Domain

2025-10-06T19:46:23Z

Allo: /* Setting up Custom Domain via Namecheap */

Tutorials

2025-10-06T19:42:52Z

Allo: Undo revision 2105 by Allo (talk)

== Video Tutorials ==



All video tutorials are hosted on the [https://www.youtube.com/@HelioHostYT HelioHost YouTube channel].

If you enjoy the videos we post, please subscribe to our channel. As a small non-profit funded by donations, we don't have a huge budget to afford paid advertising. The more free advertising we get from word of mouth recommendations, social media likes, and channel subscriptions goes a long way towards helping us find more users and continuing to grow. Even if you can't [https://heliohost.org/donate/ donate], supporting our content is one of the great ways you can [[:How_You_Can_Help | help us for free]].

* [https://youtu.be/Vq-cKnQGevU Caddy Webserver on HelioHost]
* [https://youtu.be/Fgmzvrtu7sA Creating a Modded Minecraft Server]
* [https://youtu.be/JAXDD7VYHUk How to create a Minecraft Server]
* [https://youtu.be/qXp6pw_aV0w How to issue a Google Trust Services Certificate]
* [https://youtu.be/IbUi2gcLbuA Installing MariaDB & PHP on a HelioHost VPS]
* [https://youtu.be/zHwWs7Tt2zc Installing NGINX on a HelioHost VPS]
* [https://youtu.be/-9Q9SAONgtM Hosting a Discord Bot with HelioHost]
* [https://youtu.be/Ak2yI8w-mew Hosting a Node.js site with HelioHost]
* [https://youtu.be/taTIjYTidcU Getting Started with a HelioHost VPS]

== Written Tutorials ==



* [[:Astro|Astro]]

* [[:Configuring_Environment|Configuring the Environment]]

* [[:Discord_Bot|Discord Bot]]

* [[:Django|Django Tutorials]]
** [[:Django_on_HelioHost|Django on HelioHost]]
** [[:Converting_an_Existing_Django_App|Converting an Existing Django App to work on HelioHost]]

* [[:DNS_Record_Management|DNS Record Management Tutorials]]
** [[:HelioHost_DNS_Records|HelioHost DNS Records]]
*** [[:Google_Site_Verification|Google Site Verification]]
*** [[:Manage_HelioHost_DNS|Manage HelioHost DNS]]
** [[:External_DNS_Hosting|External DNS Hosting]]
*** [[:Cloudflare_DNS_Records|Cloudflare DNS Record Management]]
*** [[:Namecheap_DNS_Records|Namecheap DNS Record Management]]

* [[:Flask|Flask]]

* [[:Gatsby|Gatsby]]

* [[:Golang|Golang as CGI]]

* [[:Node.js|Node.js Tutorials]]
** [[:Node.js|Node.js]]
** [[:Express|Express.js]]
** [[:Next.js|Next.js]]

* [[:Perl|Perl]]

* [[:Plesk Tutorials|Plesk Tutorials]]
** [[:View_Error_Logs|View Error Logs in Plesk]]
** [[:Account_Backups|Account Backups]]
** [[:Create_Website|Creating a Website]]
** [[:GitHub_Webhooks|Update Your Website with GitHub Webhooks and Plesk]]
** [[:Cron_Jobs|Cron Jobs]]
** [[:Password_Protect_a_Directory|Password Protect a Directory in Plesk]]
** [[:Custom_Error_Pages|Creating Custom Error Pages]]

* [[:Python|Python]]

* [[:Ruby_on_Rails|Ruby on Rails]]

* [[:VPS|VPS Tutorials]]
** [[:NGINX|NGINX]]
** [[:VPS_WordPress|Installing WordPress on a VPS running Hestia Control Panel]]
** [[:VPS_Email|Setting Up Email on a VPS running Hestia Control Panel]]
** [[:VPS_Nodejs|Node.js from start to Hello World on a VPS running Hestia Control Panel]]
** [[:VPS_Domain|Using a custom domain on VPS]]

== Tutorial Suggestions ==

Please let us know if there is a specific topic that you think would be good for our growing collection of tutorial videos and written guides. You can post your suggestions in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum].

[[Category:Tutorials]]

Tutorials

2025-10-06T19:38:49Z

Allo: /* Written Tutorials */

== Video Tutorials ==



All video tutorials are hosted on the [https://www.youtube.com/@HelioHostYT HelioHost YouTube channel].

If you enjoy the videos we post, please subscribe to our channel. As a small non-profit funded by donations, we don't have a huge budget to afford paid advertising. The more free advertising we get from word of mouth recommendations, social media likes, and channel subscriptions goes a long way towards helping us find more users and continuing to grow. Even if you can't [https://heliohost.org/donate/ donate], supporting our content is one of the great ways you can [[:How_You_Can_Help | help us for free]].

* [https://youtu.be/Vq-cKnQGevU Caddy Webserver on HelioHost]
* [https://youtu.be/Fgmzvrtu7sA Creating a Modded Minecraft Server]
* [https://youtu.be/JAXDD7VYHUk How to create a Minecraft Server]
* [https://youtu.be/qXp6pw_aV0w How to issue a Google Trust Services Certificate]
* [https://youtu.be/IbUi2gcLbuA Installing MariaDB & PHP on a HelioHost VPS]
* [https://youtu.be/zHwWs7Tt2zc Installing NGINX on a HelioHost VPS]
* [https://youtu.be/-9Q9SAONgtM Hosting a Discord Bot with HelioHost]
* [https://youtu.be/Ak2yI8w-mew Hosting a Node.js site with HelioHost]
* [https://youtu.be/taTIjYTidcU Getting Started with a HelioHost VPS]

== Written Tutorials ==



* [[:Astro|Astro]]

* [[:Configuring_Environment|Configuring the Environment]]

* [[:Discord_Bot|Discord Bot]]

* [[:Django|Django Tutorials]]
** [[:Django_on_HelioHost|Django on HelioHost]]
** [[:Converting_an_Existing_Django_App|Converting an Existing Django App to work on HelioHost]]

* [[:DNS_Record_Management|DNS Record Management Tutorials]]
** [[:HelioHost_DNS_Records|HelioHost DNS Records]]
*** [[:Google_Site_Verification|Google Site Verification]]
*** [[:Manage_HelioHost_DNS|Manage HelioHost DNS]]
** [[:External_DNS_Hosting|External DNS Hosting]]
*** [[:Cloudflare_DNS_Records|Cloudflare DNS Record Management]]
*** [[:Namecheap_DNS_Records|Namecheap DNS Record Management]]

* [[:Flask|Flask]]

* [[:Gatsby|Gatsby]]

* [[:Golang|Golang as CGI]]

* [[:Node.js|Node.js Tutorials]]
** [[:Node.js|Node.js]]
** [[:Express|Express.js]]
** [[:Next.js|Next.js]]

* [[:Perl|Perl]]

* [[:Plesk Tutorials|Plesk Tutorials]]
** [[:View_Error_Logs|View Error Logs in Plesk]]
** [[:Account_Backups|Account Backups]]
** [[:Create_Website|Creating a Website]]
** [[:GitHub_Webhooks|Update Your Website with GitHub Webhooks and Plesk]]
** [[:Cron_Jobs|Cron Jobs]]
** [[:Password_Protect_a_Directory|Password Protect a Directory in Plesk]]
** [[:Custom_Error_Pages|Creating Custom Error Pages]]

* [[:Python|Python]]

* [[:Ruby_on_Rails|Ruby on Rails]]

* [[:VPS|VPS Tutorials]]
** [[:NGINX|NGINX]]
** [[:VPS_WordPress|Installing WordPress on a VPS running Hestia Control Panel]]
** [[:VPS_Email|Setting Up Email on a VPS running Hestia Control Panel]]
** [[:VPS_Nodejs|Node.js from start to Hello World on a VPS running Hestia Control Panel]]

== Tutorial Suggestions ==

Please let us know if there is a specific topic that you think would be good for our growing collection of tutorial videos and written guides. You can post your suggestions in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum].

[[Category:Tutorials]]

Namecheap DNS Records

2025-10-06T19:37:49Z

Allo:

== Namecheap DNS Record Management ==

HelioHost has an [[:How_You_Can_Help#Use_Our_Affiliate_Links|affiliate agreement]] with [https://heliohost.org/partners/namecheap Namecheap], so if you're in the market for a new domain we highly recommend purchasing it from them.

Using the affiliate banner below to sign up and register your domain will not cost you anything extra, but it helps HelioHost earn a bit of commission for the referral.

[[File:Namecheap.png|link=https://heliohost.org/partners/namecheap]]

{{Info|After checking if your preferred domain name is available, sometimes there will be a '''Promo Code''' to get a lower price for the first year.}}

== Update Namecheap Settings ==

After you've purchased a domain from Namecheap, follow the steps below to set up your DNS:

* Login to your Namecheap account
* Click on '''Domain List''' in the left sidebar menu
* Click on the '''Manage''' button on the right side

[[File:Namecheap-dns-1.png]]

* Select '''Custom DNS''' from the dropdown menu in the '''Nameservers''' section
* Enter the HelioHost nameservers '''ns1.heliohost.org''' and '''ns2.heliohost.org'''
* Click on the '''green checkmark''' to save your settings

[[File:Namecheap-dns-2.png]]

{{Caution|If you are using a VPS, you also need to ask a heliohost admin to set up your DNS.}}

== Wait 24 - 48 hours for DNS Propagation ==

{{Info|DNS records do not propagate immediately. Full DNS propagation can take up to 24 - 48 hours globally in some cases.}}

Follow the steps below to check that your DNS is properly configured:

* Go to [https://dnschecker.org/ dnschecker.org]
* Enter your '''domain name'''
* Select the type of record you want to check (in this case, select '''NS''')
* Click the '''Search''' button

[[File:Namecheap-dns-3.png]]

== Further Support ==

If you get stuck or have any questions, please don't hesitate to post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide your '''username''', '''domain name''', and any '''error message(s)''' received.

Namecheap DNS Records

2025-10-06T19:37:23Z

Allo:

== Namecheap DNS Record Management ==

HelioHost has an [[:How_You_Can_Help#Use_Our_Affiliate_Links|affiliate agreement]] with [https://heliohost.org/partners/namecheap Namecheap], so if you're in the market for a new domain we highly recommend purchasing it from them.

Using the affiliate banner below to sign up and register your domain will not cost you anything extra, but it helps HelioHost earn a bit of commission for the referral.

[[File:Namecheap.png|link=https://heliohost.org/partners/namecheap]]

{{Info|After checking if your preferred domain name is available, sometimes there will be a '''Promo Code''' to get a lower price for the first year.}}

== Update Namecheap Settings ==

After you've purchased a domain from Namecheap, follow the steps below to set up your DNS:

* Login to your Namecheap account
* Click on '''Domain List''' in the left sidebar menu
* Click on the '''Manage''' button on the right side

[[File:Namecheap-dns-1.png]]

* Select '''Custom DNS''' from the dropdown menu in the '''Nameservers''' section
* Enter the HelioHost nameservers '''ns1.heliohost.org''' and '''ns2.heliohost.org'''
* Click on the '''green checkmark''' to save your settings

[[File:Namecheap-dns-2.png]]

{{Caution:If you are using a VPS, you also need to ask a heliohost admin to set up your DNS.}}

== Wait 24 - 48 hours for DNS Propagation ==

{{Info|DNS records do not propagate immediately. Full DNS propagation can take up to 24 - 48 hours globally in some cases.}}

Follow the steps below to check that your DNS is properly configured:

* Go to [https://dnschecker.org/ dnschecker.org]
* Enter your '''domain name'''
* Select the type of record you want to check (in this case, select '''NS''')
* Click the '''Search''' button

[[File:Namecheap-dns-3.png]]

== Further Support ==

If you get stuck or have any questions, please don't hesitate to post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide your '''username''', '''domain name''', and any '''error message(s)''' received.

Namecheap DNS Records

2025-10-06T19:36:43Z

Allo:

== Namecheap DNS Record Management ==

HelioHost has an [[:How_You_Can_Help#Use_Our_Affiliate_Links|affiliate agreement]] with [https://heliohost.org/partners/namecheap Namecheap], so if you're in the market for a new domain we highly recommend purchasing it from them.

Using the affiliate banner below to sign up and register your domain will not cost you anything extra, but it helps HelioHost earn a bit of commission for the referral.

[[File:Namecheap.png|link=https://heliohost.org/partners/namecheap]]

{{Info|After checking if your preferred domain name is available, sometimes there will be a '''Promo Code''' to get a lower price for the first year.}}

== Update Namecheap Settings ==

After you've purchased a domain from Namecheap, follow the steps below to set up your DNS:

* Login to your Namecheap account
* Click on '''Domain List''' in the left sidebar menu
* Click on the '''Manage''' button on the right side

[[File:Namecheap-dns-1.png]]

* Select '''Custom DNS''' from the dropdown menu in the '''Nameservers''' section
* Enter the HelioHost nameservers '''ns1.heliohost.org''' and '''ns2.heliohost.org'''
* Click on the '''green checkmark''' to save your settings

[[File:Namecheap-dns-2.png]]

[[Caution:If you are using a VPS, you also need to ask a heliohost admin to set up your DNS.]]

== Wait 24 - 48 hours for DNS Propagation ==

{{Info|DNS records do not propagate immediately. Full DNS propagation can take up to 24 - 48 hours globally in some cases.}}

Follow the steps below to check that your DNS is properly configured:

* Go to [https://dnschecker.org/ dnschecker.org]
* Enter your '''domain name'''
* Select the type of record you want to check (in this case, select '''NS''')
* Click the '''Search''' button

[[File:Namecheap-dns-3.png]]

== Further Support ==

If you get stuck or have any questions, please don't hesitate to post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide your '''username''', '''domain name''', and any '''error message(s)''' received.

VPS Domain

2025-10-06T19:28:56Z

Allo: /* dont look yet im building this page */

== dont look yet im building this page ==
== Setting up Custom Domain via Namecheap ==
== Setting up Custom Domain via Cloudflare ==

VPS Domain

2025-10-06T19:23:56Z

Allo: Created page with "== dont look yet im building this page =="

== dont look yet im building this page ==

Tutorials

2025-10-06T19:23:27Z

Allo: /* Written Tutorials */

VPS Nodejs

2025-10-06T19:20:31Z

Allo:

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions. It may be handy to know that <code>sudo chmod 777 -R directory</code>, with directory being your target directory, applies the permission to everything in that folder.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

[[File:vpsnode7.jpg]]

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

VPS Nodejs

2025-10-03T03:09:29Z

Allo:

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions; chmod 777ing everything and crying when recursively applying it to everything in a folder doesn't work even though the internet says it should.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

[[File:vpsnode7.jpg]]

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

VPS Nodejs

2025-10-03T03:07:07Z

Allo:

im currently building this page so wait one sec pls. dont look yet!

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions; chmod 777ing everything and crying when recursively applying it to everything in a folder doesn't work even though the internet says it should.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

[[File:vpsnode7.jpg]]

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

File:Vpsnode7.jpg

2025-10-03T03:06:36Z

Allo:

VPS Nodejs

2025-10-03T03:05:45Z

Allo:

im currently building this page so wait one sec pls. dont look yet!

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions; chmod 777ing everything and crying when recursively applying it to everything in a folder doesn't work even though the internet says it should.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
[[File:vpsnode6.jpg]]
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

https://user.uploads.dev/file/bd8fcc6a2462757df4f424472daf878c.jpg

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

File:Vpsnode6.jpg

2025-10-03T03:04:45Z

Allo:

VPS Nodejs

2025-10-03T03:03:29Z

Allo:

im currently building this page so wait one sec pls. dont look yet!

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
[[File:vpsnode5.png]]

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions; chmod 777ing everything and crying when recursively applying it to everything in a folder doesn't work even though the internet says it should.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
https://user.uploads.dev/file/30178d35f063d742c1215e72069269fb.jpg
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

https://user.uploads.dev/file/bd8fcc6a2462757df4f424472daf878c.jpg

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

VPS Nodejs

2025-10-03T03:01:56Z

Allo:

im currently building this page so wait one sec pls. dont look yet!

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

[[File:vpsnode4.jpg]]

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
https://user.uploads.dev/file/fad1b70e9c0d634b1855d0100f105658.png

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions; chmod 777ing everything and crying when recursively applying it to everything in a folder doesn't work even though the internet says it should.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
https://user.uploads.dev/file/30178d35f063d742c1215e72069269fb.jpg
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

https://user.uploads.dev/file/bd8fcc6a2462757df4f424472daf878c.jpg

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

File:Vpsnode4.jpg

2025-10-03T03:01:18Z

Allo:

VPS Nodejs

2025-10-03T03:00:28Z

Allo:

im currently building this page so wait one sec pls. dont look yet!

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

[[File:vpsnode3.jpg]]

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

https://user.uploads.dev/file/b95f4acd8017d1ab19d0d5fbfd807fb4.jpg

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
https://user.uploads.dev/file/fad1b70e9c0d634b1855d0100f105658.png

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions; chmod 777ing everything and crying when recursively applying it to everything in a folder doesn't work even though the internet says it should.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
https://user.uploads.dev/file/30178d35f063d742c1215e72069269fb.jpg
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

https://user.uploads.dev/file/bd8fcc6a2462757df4f424472daf878c.jpg

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

File:Vpsnode3.jpg

2025-10-03T02:59:51Z

Allo:

VPS Nodejs

2025-10-03T02:58:24Z

Allo:

im currently building this page so wait one sec pls. dont look yet!

== Starting Up ==

[[File:vpsnode1.jpg]]

In https://heliohost.org/chat/ say you are getting a VPS and that you would like it to come with Hestia installed on it. Hestia is the control panel we will be using. If you don't want to pay with paypal you may also ask for an alternate payment link.

You should get an email listing your ip, port, and other info for logging in. I did this all on phone so now I'm going to direct you to some android apps, tho there are equivalents for all devices. just search 'sftp' or 'ssh'.

I use https://termius.com/ because i like the terminal and it doesn't weirdly close for no reason. And NMM at https://play.google.com/store/apps/details?id=in.mfile&pli=1 for editing the files of the server since Termius can't do that.

== In to Hestia ==

Before we log in to the apps, let's try logging in to Hestia. In your email see where it says your domain is <code>vps###.heliohost.us</code>? ### refers to your specific number in the email. Add a <code>:8083</code> so the link is <code>vps###.heliohost.us:8083</code> and go to it in your browser. You should find a login page with the username being 'admin' and password being your password. Enter those and you are in the Hestia Control Panel. Explore around it a bit.

Now lets change account setting from nologin to bash, and link our first domain.

To change from nologin to bash, touch the three bars below the top three bars, go to users, and touch the admin user. Go to the bottom where it says Advanced Options, and change nologin to bash.

[[File:vpsnode2.jpg]]

Now lets add a domain so u can have the node site online somewhere. If you ask in support chat they can give you a free heliohost domain to build with.

Touch the 3 bars again and go to Web. Add a new domain with the address and ip. Enable SSL in advanced options. Mine looks like this.

https://user.uploads.dev/file/69c3bd511288969586ad7c3051be65d4.jpg

== Terminal Stuff ==

Now let's open Termius and log in.
I would take screenshots but Termius doesn't let me. Skip the logging in and ai stuff of termius and go straight to Hosts and make a new host. Set the ip to either of the ips from your email. I use the ipv6 one and no idea if there are limitations using the ipv4 one or not. :)

port should already be on 22 correctly and enter username <code>admin</code> and your password.

https://user.uploads.dev/file/b95f4acd8017d1ab19d0d5fbfd807fb4.jpg

You will find terminal stuff is filled with Permissions issues and nearly any command will have to be prefaced with <code>sudo</code>... OR you could just log in as root; so let's do that now. Type and enter <code>sudo su</code>. It will ask for your password. Enter it and afterward you should see you are logged in as root.

Now lets make sure these files are created and give them the correct permissions. These files are used to create a node.js template in Hestia. Enter each of these lines in terminal.

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>touch /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.sh</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.tpl</code>

<code>chmod 777 /usr/local/hestia/data/templates/web/nginx/nodejs3000.stpl</code>

I am a noob and chmod 755 is supposed to work while still restricting some users, but didn't work for me. 777 allows any user to edit the file. This doesn't mean random people on the internet can edit it, but if you are a business that shares the webserver with multiple users each with their own login, each one can edit this file. So I used 777, but feel free to do it correctly instead (if you know how).

== sftp file editing ==

Now lets add in what is supposed to go in each of these files. Start the NMM app and log in with the same info you used with Termius. Then touch your files and go to the lowest level and you should see:
https://user.uploads.dev/file/fad1b70e9c0d634b1855d0100f105658.png

Navigate to the files you touched; they are at <code>/usr/local/hestia/data/templates/web/nginx/</code>.

Copy and paste these in to each file and save. Also, to even see files, you will probably have to deal with permissions; chmod 777ing everything and crying when recursively applying it to everything in a folder doesn't work even though the internet says it should.

Here is the text for nodejs3000.sh:
<pre>#!/bin/bash
user=$1
domain=$2
ip=$3
home=$4
docroot=$5
mkdir "$home/$user/web/$domain/nodeapp"
chown -R $user:$user "$home/$user/web/$domain/nodeapp"
rm "$home/$user/web/$domain/nodeapp/app.sock"
runuser -l $user -c "pm2 start $home/$user/web/$domain/nodeapp/app.js"
sleep 5
chmod 777 "$home/$user/web/$domain/nodeapp/app.sock"</pre>

Here is the text for nodejs3000.tpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;

location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}

location @fallback {
proxy_pass http://127.0.0.1:3000:/$1;
}
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%.conf*;
}</pre>

Here is the text for nodejs3000.stpl:
<pre>server {
listen %ip%:%proxy_port%;
server_name %domain_idn% %alias_idn%;
return 301 https://%domain_idn%$request_uri;
}
server {
listen %ip%:%proxy_ssl_port% http2 ssl;
server_name %domain_idn% %alias_idn%;
ssl_certificate %ssl_pem%;
ssl_certificate_key %ssl_key%;
error_log /var/log/%web_system%/domains/%domain%.error.log error;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types image/svg+xml svg svgz text/plain application/x-javascript text/xml text/css;
gzip_vary on;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /error/ {
alias %home%/%user%/web/%domain%/document_errors/;
}
location @fallback {
proxy_pass https://127.0.0.1:3000:/$1;
}
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/%domain%/nginx.ssl.conf_*;
}</pre>

== finally node stuff ==

At this point you should probably install npm and also pm2 to start the app correctly. i had eaddrinuse errors when starting not using pm2.
so do

<code>apt update && apt install npm -y</code>

<code>npm install pm2 -g</code>

finally we are almost there. Now that those three files are correct, go back in to the hestia control panel, to web, to the domain, to advanced options, and under proxy template select nodejs3000.
https://user.uploads.dev/file/30178d35f063d742c1215e72069269fb.jpg
finally we are to the simple node stuff

in termius use cd to navigate to the directory referenced by the template:
<code>cd /home/admin/web/allo.helioho.st/nodeapp</code>
Use your domain instead of allo.helioho.st.
{{Caution|also people will tell you to make a new user account instead of do it under admin. I didn't tho. I just wanted to complete the process of getting a node site fully online; not delve in to accounts.}}
{{Info|Making my first real site after this tutorial; I started with making a dedicated account for it.}}

now we npm init in that folder to start a node project:
<code>npm init -y</code>

Now here is a starter hello world node file.
<pre>const http = require('http'); // Import the built-in http module

const hostname = "127.0.0.1"
const port = 3000; // Port to listen on

// Create a server instance
const server = http.createServer((req, res) => {
// Set the response header
res.writeHead(200, { 'Content-Type': 'text/plain' });

// Send the response body
res.end('Hello, World!\n');
});

server.on('listening',function(){
console.log('ok, server is running');
});

// Start the server and listen for incoming requests
server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});</pre>

{{Danger|All these places in files that say ip 127.0.0.1 keep them like that. Don't use your own ip. It's supposed to say 127.0.0.1.}}

Open up nmm again and navigate to <code>/home/admin/web/allo.helioho.st/nodeapp</code> and create a file named app.js and paste in the code.

In termius terminal be cd'd in to that folder and type:
<code>pm2 start app.js</code>

Now go to your domain and it should say hello world :)

if you have problems, you could allow node's ports 3000 and 449 through the firewall.

For the firewall, touch the three bars in top right, and go to Server Settings, then Firewall and add an exception.

https://user.uploads.dev/file/bd8fcc6a2462757df4f424472daf878c.jpg

I actually don't know if this is required because what was blocking me turned out to have to do with something other than the firewall, but, while searching for answers, I came across someone who implied opening ports 3000 and 449 was needed. so i did both.

Also I was not able to access my site without a vpn initially and this was solved by communicating clearly on the discord support and Krydos deleting the aaaa records off my vps.

File:Vpsnode2.jpg

2025-10-03T02:57:31Z

Allo: