HelioHost Wiki - User contributions [en]

Charlie

2025-12-31T03:30:09Z

Unknown025: Minor grammar change.

== Charlie ==

Charlie is a physical server that was purchased in December 2010 and originally hosted [[:Cody|Cody]] and [[:Johnny|Johnny]]. In 2016 when [[:Eddie|Eddie]] was purchased [[:Cody|Cody]] was moved to [[:Eddie|Eddie]] so [[:Johnny|Johnny]] could have all of the resources of Charlie to himself. When [[:Sparkie|Sparkie]] was purchased in 2019 [[:Johnny|Johnny]] was moved off of Charlie as well. He is equipped with a Core 2 Quad Q9550 CPU, 8 GB of memory, and runs [https://en.wikipedia.org/wiki/VMware_ESXi VMware ESXi]. Charlie has been empty since December 2025, and is next in line to be retired.

VPS Nodejs

2025-10-07T20:47:57Z

Unknown025: Minor formatting and grammar changes.

== 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, 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 Domain

2025-10-07T03:30:36Z

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

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 administrator (tell them your domain) to set up your DNS if you are using HelioHost's nameservers. That's really all you need to do.

== Setting up Custom Domain via Cloudflare ==
[[File:customdomain3.jpg|500px|right]]
First, let's configure DNS. Go to the DNS option on the dashboard and then to Records.
[[File:customdomain5.jpg|500px|right]]
Grab the IPv4 address from your HelioHost email and create an <code>A</code> record. Do the same with the IPv6 address and <code>AAAA</code> record. Also, feel free to make a CNAME record (which will allow <code>www</code> to redirect to your main site).
[[File:customdomain4.jpg|500px|right]]
Now, on to the Hestia control panel. Go to Users, find the user which is the owner of this domain, and click <code>edit settings</code>.
[[File:customdomain6.jpg|500px|right]]
Go to Advanced Settings and change the nameservers to the ones provided by Cloudflare (like I did here).
[[File:customdomain1.jpg|500px|right]]
Now, back to Cloudflare, find the SSL settings.
[[File:customdomain2.jpg|500px|right]]
Set SSL to <code>Full (Strict)</code>, which is Cloudflare's recommendation for security.
Back 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|500px|right]]
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 self-creating your SSL. At least it isn't a real security risk.}}

VPS Domain

2025-10-07T03:20:35Z

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

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 administrator (tell them your domain) to set up your DNS if you are using HelioHost's nameservers. That's really all you need to do.

== Setting up Custom Domain via Cloudflare ==
[[File:customdomain3.jpg]]
First, let's configure DNS. Go to the DNS option on the dashboard and then to Records.
[[File:customdomain5.jpg]]
Grab the IPv4 address from your HelioHost email and create an <code>A</code> record. Do the same with the IPv6 address and <code>AAAA</code> record. Also, feel free to make a CNAME record (which will allow <code>www</code> to redirect to your main site).
[[File:customdomain4.jpg]]
Now, on to the Hestia control panel. Go to Users, find the user which is the owner of this domain, and click <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, find the SSL settings.
[[File:customdomain2.jpg]]
Set SSL to <code>Full (Strict)</code>, which is Cloudflare's recommendation for security.
Back 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 self-creating your SSL. At least it isn't a real security risk.}}

VPS Domain

2025-10-07T03:12:35Z

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

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 administrator (tell them your domain) to set up your DNS if you are using HelioHost's 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}}

NGINX

2024-10-31T01:20:23Z

Unknown025: /* Getting Started */

= NGINX =

= Preface =

NGINX is described as a "web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache".
In practice, it's a powerful alternative to Apache, as it's more memory efficient. While configuring NGINX may seem a
little foreign if coming from Apache's <code>.htaccess</code> override based system, there's a lot to enjoy.

= Getting Started =

While NGINX can be installed on a variety of systems, we'll focus on Ubuntu. As with most installations, it's highly
recommended to update your system beforehand, using <code>sudo apt update && sudo apt upgrade</code>.

{{Danger|
Using <code>sudo</code> is equivalent to running a command with root/administrative privileges! While
this tutorial relies heavily on its usage, most normal commands '''should not''' be run with the <code>sudo</code> prefix, as that's
a surefire way to potentially cause irreversible damage to your system configuration.
}}

With our system up-to-date, we can now run <code>sudo apt install nginx</code>. This command will install and configure a default
installation of NGINX, which means we should be able to access our VPS from a web browser...as soon as we configure our
firewall.

Using "UFW" (Universal Fire Wall), we can see using <code>sudo ufw app list</code> that NGINX has added three new profiles for us
to choose from ('Nginx Full', 'Nginx HTTP', 'Nginx HTTPS'). For our purposes, we'll enable 'Nginx Full'
using <code>sudo ufw allow 'Nginx Full'</code>. *Now* we should be able to see our VPS from a web browser, using
either <code>http://[Dedicated IPv4]</code> or <code>http://vps#.heliohost.us</code>, and see the default NGINX landing page.

= Configuring NGINX =

= Creating a new content directory =

While being able to see the default NGINX page is great, it's time to configure NGINX's "server blocks", which will
allow us to define how NGINX behaves on a "per-domain" basis. Let's start by creating a new directory for our web
content, using `sudo mkdir -p /var/www/[domain name]/html` (replace "[domain name]" with your own). In this case, `-p`
is used to create any missing parent directories, while `sudo` is used as the `/var` directory is system-protected.

Now, we can make our life easier by changing the owner and permissions of our new folder, so we won't have to repeatedly
use `sudo` permissions to access our own content. Using `sudo chown -R $USER:$USER /var/www/[domain name]/html`, we
can "change owner" to our current user (`-R` applies the command recursively to all the contents, if applicable). We
also need to set the directory's permissions, using `sudo chmod -R 755 /var/www/[domain name]` (chmod means "change
mode", while 755 is the numerical representation of "read and execute access for everyone, write access for the owner").

Any file we save in this new directory will be served using NGINX. As a simple test, we'll create a simple HTML file as
follows:

<pre>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Home</title>
</head>
<body>
<h1>My NGINX Config is Working!</h1>
<p>Pat yourself on the back, for a job well done.</p>
</body>
</html>
</pre>

= Creating a server block =

For every domain that is associated with your VPS, you'll want to create an NGINX configuration file, known as a "server
block", located in `/etc/nginx/sites-available`. For example, we'll create one for our VPS
with `sudo vi /etc/nginx/sites-available/[domain name]` (no file ending like ".txt" or ".json", only your domain name).
For a brief Vim tutorial, see [here](#using-vim). Enter "insert" mode using "i", and paste the following default code
block:

<pre>
server {
listen 80;
listen [::]:80;

root /var/www/[domain name]/html;
index index.html index.htm index.nginx-debian.html;

server_name yourdomain.com;

location / {
try_files $uri $uri/ =404;
}
}
</pre>

Once again, __make sure to edit all the references to match your own domain name__. Once you're finished, press "ESC",
followed by `:wq`. If you get an error saying "This file is readonly", make sure you are editing the file with `sudo`
permissions.

Now you may have noticed we created this configuration file in `sites-available`, '''not''' `sites-enabled`. Let's rectify
that, using a symbolic link (which is, in layman's terms, a shortcut for the system to find the original file in another
path). Using `sudo ln -s /etc/nginx/sites-available/[domain name] /etc/nginx/sites-enabled/`, we can accomplish that
task.

An easy way to check if everything's configured correctly, is to use `sudo nginx -t`, which will validate your NGINX
configuration.

To update our changes, we can use `sudo systemctl nginx restart`, which will restart NGINX.

Congratulations, you should now see your HTML page served from your VPS to your browser!

= Adding SSL =

No website is complete (or secure) without SSL! As everyone else, we'll use [https://letsencrypt.org/ Let's Encrypt] to achieve this.

First, we'll need to install Certbot, which is a commandline utility for automating the process.
Run `sudo apt install certbot python3-certbot-nginx` ('''not the same as the Apache version'''), which will install Certbot and its dependencies.

Now we can get a certificate. Run `sudo certbot --nginx -d yourdomain.com`, and follow the on-screen instructions to complete the process. Make sure you enabled SSL using UFW!

Your website will now be secure with SSL, and your SSL certificate will be automatically renewed every three months.

= Using Vim =

Vim is the default text editor for most Unix based systems. While it's a ubiquitous program, it's infamous for being
hard to learn, especially since saving or exiting is not as intuitive as other comparable programs. However, using it
may not be as hard as it seems.

To edit a file, use `vi file.txt`, which will open the Vim interface. If you supply a nonexistent filename, Vim will
create a file instead.

To enter "insert" mode, press "i". This will allow you to edit the current file, instead of running commands inside Vim.
To exit "insert" mode, press "ESC".

To save a file, make sure you are not in "insert" mode, before entering `:wq` (which will '''write''', '''quit'''). If you
want to exit without saving your changes, enter `:q!`, which will '''force quit'''.

NGINX

2024-10-31T01:18:36Z

Unknown025: /* Preface */

= NGINX =

= Preface =

NGINX is described as a "web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache".
In practice, it's a powerful alternative to Apache, as it's more memory efficient. While configuring NGINX may seem a
little foreign if coming from Apache's <code>.htaccess</code> override based system, there's a lot to enjoy.

= Getting Started =

While NGINX can be installed on a variety of systems, we'll focus on Ubuntu. As with most installations, it's highly
recommended to update your system beforehand, using `sudo apt update && sudo apt upgrade`.

{{Danger|
Using `sudo` is equivalent to running a command with root/administrative privileges! While
this tutorial relies heavily on its usage, most normal commands '''should not''' be run with the `sudo` prefix, as that's
a surefire way to potentially cause irreversible damage to your system configuration.
}}

With our system up-to-date, we can now run `sudo apt install nginx`. This command will install and configure a default
installation of NGINX, which means we should be able to access our VPS from a web browser...as soon as we configure our
firewall.

Using "UFW" (Universal Fire Wall), we can see using `sudo ufw app list` that NGINX has added three new profiles for us
to choose from ('Nginx Full', 'Nginx HTTP', 'Nginx HTTPS'). For our purposes, we'll enable 'Nginx Full'
using `sudo ufw allow 'Nginx Full'`. *Now* we should be able to see our VPS from a web browser, using
either `http://[Dedicated IPv4]` or `http://vps#.heliohost.us`, and see the default NGINX landing page.

= Configuring NGINX =

= Creating a new content directory =

While being able to see the default NGINX page is great, it's time to configure NGINX's "server blocks", which will
allow us to define how NGINX behaves on a "per-domain" basis. Let's start by creating a new directory for our web
content, using `sudo mkdir -p /var/www/[domain name]/html` (replace "[domain name]" with your own). In this case, `-p`
is used to create any missing parent directories, while `sudo` is used as the `/var` directory is system-protected.

Now, we can make our life easier by changing the owner and permissions of our new folder, so we won't have to repeatedly
use `sudo` permissions to access our own content. Using `sudo chown -R $USER:$USER /var/www/[domain name]/html`, we
can "change owner" to our current user (`-R` applies the command recursively to all the contents, if applicable). We
also need to set the directory's permissions, using `sudo chmod -R 755 /var/www/[domain name]` (chmod means "change
mode", while 755 is the numerical representation of "read and execute access for everyone, write access for the owner").

Any file we save in this new directory will be served using NGINX. As a simple test, we'll create a simple HTML file as
follows:

<pre>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Home</title>
</head>
<body>
<h1>My NGINX Config is Working!</h1>
<p>Pat yourself on the back, for a job well done.</p>
</body>
</html>
</pre>

= Creating a server block =

For every domain that is associated with your VPS, you'll want to create an NGINX configuration file, known as a "server
block", located in `/etc/nginx/sites-available`. For example, we'll create one for our VPS
with `sudo vi /etc/nginx/sites-available/[domain name]` (no file ending like ".txt" or ".json", only your domain name).
For a brief Vim tutorial, see [here](#using-vim). Enter "insert" mode using "i", and paste the following default code
block:

<pre>
server {
listen 80;
listen [::]:80;

root /var/www/[domain name]/html;
index index.html index.htm index.nginx-debian.html;

server_name yourdomain.com;

location / {
try_files $uri $uri/ =404;
}
}
</pre>

Once again, __make sure to edit all the references to match your own domain name__. Once you're finished, press "ESC",
followed by `:wq`. If you get an error saying "This file is readonly", make sure you are editing the file with `sudo`
permissions.

Now you may have noticed we created this configuration file in `sites-available`, '''not''' `sites-enabled`. Let's rectify
that, using a symbolic link (which is, in layman's terms, a shortcut for the system to find the original file in another
path). Using `sudo ln -s /etc/nginx/sites-available/[domain name] /etc/nginx/sites-enabled/`, we can accomplish that
task.

An easy way to check if everything's configured correctly, is to use `sudo nginx -t`, which will validate your NGINX
configuration.

To update our changes, we can use `sudo systemctl nginx restart`, which will restart NGINX.

Congratulations, you should now see your HTML page served from your VPS to your browser!

= Adding SSL =

No website is complete (or secure) without SSL! As everyone else, we'll use [https://letsencrypt.org/ Let's Encrypt] to achieve this.

First, we'll need to install Certbot, which is a commandline utility for automating the process.
Run `sudo apt install certbot python3-certbot-nginx` ('''not the same as the Apache version'''), which will install Certbot and its dependencies.

Now we can get a certificate. Run `sudo certbot --nginx -d yourdomain.com`, and follow the on-screen instructions to complete the process. Make sure you enabled SSL using UFW!

Your website will now be secure with SSL, and your SSL certificate will be automatically renewed every three months.

= Using Vim =

Vim is the default text editor for most Unix based systems. While it's a ubiquitous program, it's infamous for being
hard to learn, especially since saving or exiting is not as intuitive as other comparable programs. However, using it
may not be as hard as it seems.

To edit a file, use `vi file.txt`, which will open the Vim interface. If you supply a nonexistent filename, Vim will
create a file instead.

To enter "insert" mode, press "i". This will allow you to edit the current file, instead of running commands inside Vim.
To exit "insert" mode, press "ESC".

To save a file, make sure you are not in "insert" mode, before entering `:wq` (which will '''write''', '''quit'''). If you
want to exit without saving your changes, enter `:q!`, which will '''force quit'''.