How to Set Up Nginx on a Ubuntu Server with DigitalOcean
Nginx is one of the most widely used web servers in the world and can be used to host simple websites or also as a reverse proxy, load balancer, mail proxy, and/or HTTP cache system. The software behind Nginx is open-sourced and free.
In this article, we'll walk you through how to configure a brand-new Ubuntu server on DigitalOcean, install and configure Nginx, and replace Nginx's default HTML with our own content.
Plus, we'll provide you with some free DigitalOcean credit for you to play around with at no cost.
Let's get started!
Table of Contents
Step 1 — Set Up & Configure Your Server
Before we can do anything, we need to set up and configure a VPS (Virtual Private Server) in the cloud where we'll run Nginx.
There are a lot of companies that provide this service, but we'll use DigitalOcean. You can use any other VPS service provider you wish, but some of the steps in this tutorial will be slightly different for you.
To start, we need to create an account on DigitalOcean or log in to your existing account.
For a FREE $50 CREDIT FOR 30 DAYS, use this link: https://m.do.co/c/ce20017d8588.
They will ask you for a credit card, but you can cancel anytime before the 30 days ends and not be charged.
Create a New Droplet on DigitalOcean
After logging in or successfully signing up for a new account, open the "Create" drop-down menu and click the "Droplets" link.
On the Create Droplets page, select the Ubuntu operating system. And choose the $5/month plan, which will give us plenty of computing power to start with.
There are a few more options on that page to fill out.
When it comes to the Authentication section, don't set up any SSH keys or create a one-time password. We'll handle that in the next sections.
When you're done selecting options, hit the Create Droplet button.
When the Droplet is fully up and running, the control panel will display it's IP address.
Your server is now up and running!
In the next step, we'll start the configuration process.
To set up our server, you'll need both the IP address of the server and the private key (password) for the
rootuser's account. After creating your droplet, DigitalOcean should have sent you an email with information about your server. You'll need that information for the next steps.
Sometimes their emails take a while to come through, so be patient if you haven't received it yet.
To log into your server, open a terminal (
Ctrl+Alt+Tfor Linux) on your local machine. Once you have a terminal open, use the following command to SSH in as the root user (replace the highlighted word with your server's public IP address):
$ ssh root@server_ip_address
Accept the warning about host authenticity, if it appears, and provide your root password (will be listed in the email from DigitalOcean). If it's your first time logging into the server with a password, you will also be asked to change the root password.
rootuser in a Linux environment has very broad privileges and, for that reason, you are discouraged from using it on a regular basis. This is because very destructive changes (even by accident) can be made while using it.
Therefore, in the next step we are going to create an alternative account with limited scope that will be used for daily work.
Create a New User
Logged in as
root, we can create a new user account that will be used to log in from this point forward. You can create a new user with the following command (substitute the highlighted word with your username):
# adduser bob
You'll be asked some questions starting with the password. Choose a strong password and fill in any of the optional information after that. You can just hit
ENTERrepeatedly to skip the rest of the questions after that.
Give Your New User Root Privileges
You now have a new user account with regular account privileges. But you might occasionally need to do administrative tasks that require root privileges. So, instead of logging out of your normal user and logging back in as the
rootaccount, we can give the normal account the ability to run root privileged commands when you need to by adding
sudobefore each command.
To do this, add your new user to the
root, run the following command to add your user to the
sudogroup (substitute the highlighted word with your username):
# usermod -aG sudo bob
Now your user can run commands with
The next server setup steps help increase the security of your server. They are optional but highly recommended.
Add Public Key Authentication
By setting up public-key authentication for the new user, it will increase our server's security by requiring a private SSH key to login in.
Generate a Key Pair
If you don't already have an SSH key pair, which consists of a public and private key, you need to generate one. If you already have a key that you want to use, skip to the Copy the Public Key step.
To generate a new key pair, enter the following command at the terminal of your LOCAL MACHINE:
You'll receive an output similar to the following:
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/yourusername/.ssh/id_rsa):
ENTERto accept the file name and path.
Next, you'll be prompted to enter a password to secure the newly created key with. You can either create a password or leave it blank. This generates a private key,
id_rsa, and a public key,
id_rsa.pub, in the
.sshdirectory of your home directory.
Copy the Public Key
Now that you have the SSH key pair on our local machine, you need to copy our public key to the server.
Option 1: SSH-Copy-Id
If your local machine has the
ssh-copy-idscript installed, you can use it to install your public key to any user that you have login credentials for. If not, use Option 2 to install the key manually.
Still on your local machine, type the following command (replace the highlighted words with your username and server public IP address):
$ ssh-copy-id bob@server_ip_address
You will be asked for the user's password. Then, your public key will be added to the server user's
.ssh/authorized_keysfile. The corresponding private key can now be used to log into the server.
Option 2: Install the Key Manually
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (
$ cat ~/.ssh/id_rsa.pub
This should print your public SSH key, which should look something like the following:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf firstname.lastname@example.org
Select the public key, and copy it to your clipboard.
To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory.
On the server, as the
rootuser, enter the following command to temporarily switch to the new user (substitute the highlighted word with your username):
# su - bob
Now you will be in your new user's home directory.
Create a new directory called
.sshand restrict its permissions with the following commands:
$ mkdir ~/.ssh
$ chmod 700 ~/.ssh
Now open a file in
authorized_keyswith a text editor. We will use nano to edit the file:
$ nano ~/.ssh/authorized_keys
Now insert your public key (which should be in your clipboard) by pasting it into the editor.
CTRL-Xto exit the file, then
Yto save the changes that you made, then
ENTERto confirm the file name.
Now restrict the permissions of the
authorized_keysfile with this command:
$ chmod 600 ~/.ssh/authorized_keys
Type this command once to return to the
Now your public key is installed, and you can use SSH keys to log in as your user.
Disable Password Authentication
This step will only allow you to log into your server using the SSH key you just created. Only people who possess the private key that pairs with the public key that was installed will get into the server. This increases your server's security by disabling password-only authentication.
Only follow this step if you installed a public key in the last step. Otherwise, you'll lock yourself out of the server.
To disable password authentication, follow these steps:
rootuser or new
sudouser on your server, open the SSH daemon configuration file using the following command:
$ sudo nano /etc/ssh/sshd_config
Find the line that says
PasswordAuthenticationand change its value to
no. It should look like this after the change was made:
Save and close the file using the method:
To reload the SSH daemon and put our changes live, type the following command:
$ sudo systemctl reload sshd
Password authentication is now disabled. Now your server can only be accessed with SSH key authentication.
Test Log In Using SSH Key
On your local machine, log in to your server using the new account that we created. Use the following command (substitute the highlighted words with your username and server IP address):
$ ssh bob@server_ip_address
Once authentication is provided to the server, you will be logged in as your new user.
Basic Firewall Set Up
Ubuntu servers can use the
UFWfirewall to ensure only connections to certain services are allowed. It's a simple process to set up a basic firewall and will improve your server's security.
You can see which applications are
UFWcurrently allows by typing:
$ sudo ufw app list
This should output the following:
We need to make sure the firewall allows SSH connections so that we can log back in next time. To allow these types of connections, type the following command:
$ sudo ufw allow OpenSSH
And then enable the firewall:
$ sudo ufw enable
ENTERto proceed. You can see that SSH connections are still allowed by typing:
$ sudo ufw status
That was the last step in the initial setup for our server.
Step 2 — Install & Configure Nginx
It's time to install Nginx and set up our server to host web content.
Let's get Nginx configured on your server.
Nginx is available in Ubuntu's default repositories, so installation is pretty straightforward.
Run the following commands to update your local
apt packageindex so we have access to the most recent package lists:
$ sudo apt-get update
$ sudo apt-get install nginx
apt-getwill install Nginx along with any other required dependencies.
Adjust the Firewall
Before we can test Nginx, we need to reconfigure our firewall software to allow access to the service. Nginx registers itself as a service with
ufw, our firewall, upon installation. This makes it rather easy to allow Nginx access.
We can list the applications configurations that
ufwknows how to work with by typing:
$ sudo ufw app list
You should get a listing of the application profiles:
$ Available applications:
There are three profiles available for Nginx:
Nginx Full: Opens both port
80(normal, unencrypted web traffic) and port
Nginx Http: Opens only port
80(normal, unencrypted web traffic)
Nginx Https: Opens only port
443(TLS/SSL encrypted traffic)
It's recommended that you enable the most restrictive profile that will still allow the traffic you've configured. Since we haven't configured SSL for our server yet, in this guide, we will only need to allow traffic on port
80. When we setup
SSLEncryption later on, we'll change these settings.
You can enable this by typing:
$ sudo ufw allow 'Nginx HTTP'
You can verify the change with this command:
$ sudo ufw status
Check your Web Server
The Nginx web server should already be up and running.
You can check with the systemd init system to make sure the service is running by typing:
$ systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2016-04-18 16:14:00 EDT; 4min 2s ago
Main PID: 12857 (nginx)
├─12857 nginx: master process /usr/sbin/nginx -g daemon on; master_process on
└─12858 nginx: worker process
You can access the default Nginx landing page to confirm that the software is running properly. You can access this through your server's domain name or IP address.
When you have your server's IP address or domain, enter it into your browser's address bar:
You should see the default Nginx landing page, which should look something like this:
Congratulations! You now have a web server running using Nginx!
Step 3 — Display Some Custom HTML
After following the previous steps, you now have a web server running on your DigitalOcean droplet. Now we can add some custom HTML to display whatever we want instead of the default HTML Nginx displays.
Update Nginx Configuration
By default, Nginx is configured to serve documents out of a directory at
/var/www/html. To have Nginx serve a different site instead, you need to create your own directory within
/var/wwwfor our site. The actual web content will be put in an HTML directory within this directory.
To create this directory (replace the highlighted text with the name of your site or directory):
$ sudo mkdir -p /var/www/example.com/html
-pflag tells mkdir to create any necessary parent directories along the way.
Now that we have the directory, you need to reassign ownership of the web directories to the normal user account. This will let you write to them without
You can use the
$USERenvironmental variable to assign ownership to the account that you're currently signed in on (make sure you're not logged in as
root). This will allow you to easily create or edit the content in this directory:
$ sudo chown -R $USER:$USER /var/www/example.com/html
The permissions of your web roots should be correct already if you have not modified the umask value, but you can make sure by typing:
$ sudo chmod -R 755 /var/www
The directory structure is now configured and you can move on.
Create a Sample Page for your Website
Now that the directory structure is set up, let's create a default page for your website so that it will have something to display.
index.htmlfile in the directory you just created:
$ nano /var/www/example.com/html/index.html
Inside the file, create a really basic HTML file. It will look like this:
<title>Welcome to Example.com!</title>
<h1>Success! The example.com server block is working!</h1>
Save and close the file when you are finished.
Tell Nginx to Serve the New Html File
Now that you have the content created in the new
/var/www/example.com/htmldirectory, you need to tell Nginx to serve that directory instead of the default
/var/www/htmlit's currently using.
To do this, open the default Nginx configuration file with nano:
$ sudo nano /etc/nginx/sites-available/default
You need to change the document
root, specified by the
rootdirective in the file. Change that line so it points to the directory you created for your site:
Everything else can be kept the same. Save and close the file when you are finished.
Next, test to make sure that there are no syntax errors in any of your Nginx files:
$ sudo nginx -t
If no problems were found, restart Nginx to enable your changes:
$ sudo systemctl restart nginx
Nginx should now be serving the new HTML we added.
Test the Results
Now that you are all set up, you should test that your server is functioning correctly. You can do that by visiting your domain in your web browser:
You should see a page with these words:
If the site works, you have successfully configured Nginx.
After working through this article, you now have a Nginx web server up and running in the cloud using DigitalOcean.
Wondering what to do next? We've published some other articles that may be interesting to you:
Thanks for reading and happy coding!