In Step 1 of this series, I took you through the initial steps of setting up and securing a virtual server on Ubuntu 22.04. In this chapter I will guide you through the process of setting up Nginx, PHP-FPM, and MySQL—which on Linux is more commonly known as a LEMP stack—that will form the foundations of a working web application and server.
Before moving on with this tutorial, you will need to open a new SSH connection to the server, if you haven’t already:
huypham:~$ ssh [email protected]
Welcome to Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-41-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
System information as of Thu May 02 10:30:02 BST 2022
System load: 0.0 Processes: 112
Usage of /: 44.2% of 4.67GB Users logged in: 0
Memory usage: 18% IPv4 address for ens4: ***.***.***.***
Swap usage: 0%
Last login: Thu May 02 10:19:37 2022 from ***.***.***.***
ashley@pluto:~$
Installing Nginx
Nginx has become the most popular web server software used on Linux servers, so it makes sense to use it rather than Apache. Although the official Ubuntu package repository includes Nginx packages, they’re often very outdated. Instead, I like to use the package repository maintained by Ondřej Surý that includes the latest Nginx stable packages.
First, add the repository and update the package lists:
sudo add-apt-repository ppa:ondrej/nginx -y
sudo apt updateThere may now be some packages that can be upgraded, let’s do that now:
sudo apt dist-upgrade -yThen install Nginx:
sudo apt install nginx -yOnce complete, you can confirm that Nginx has been installed with the following command:
nginx -vhuypham@pluto:~$ nginx -v
nginx version: nginx/1.22.0Additionally, when visiting the Fully Qualified Domain Name (FQDN) pointing to your server’s IP address in the browser, you should see an Nginx welcome page.
Now that Nginx has successfully been installed it’s time to perform some basic configuration. Out-of-the-box Nginx is pretty well optimized, but there are a few basic adjustments to make. However, before opening the configuration file, you need to determine your server’s CPU core count and the open file limit.
Enter the following command to get the number of CPU cores your server has available. Take note of the number as we’ll use it in a minute:
grep processor /proc/cpuinfo | wc -lRun the following to get your server’s open file limit and take note, we’ll need it as well:
ulimit -nNext, open the Nginx configuration file, which can be found at /etc/nginx/nginx.conf:
sudo nano /etc/nginx/nginx.confuser www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 768;
# multi_accept on;
}
http {
##
# Basic Settings
##
I’m not going to list every configuration directive but I am going to briefly mention those that you should change.
Start by setting the user to the username that you’re currently logged in with. This will make managing file permissions much easier in the future, but this is only acceptable security-wise when running a single user access server.
The worker_processes directive determines how many workers to spawn per server. The general rule of thumb is to set this to the number of CPU cores your server has available. In my case, this is 1.
The events block contains two directives, the first worker_connections should be set to your server’s open file limit. This tells Nginx how many simultaneous connections can be opened by each worker_process. Therefore, if you have two CPU cores and an open file limit of 1024, your server can handle 2048 connections per second. However, the number of connections doesn’t directly equate to the number of users that can be handled by the server, as the majority of web pages and browsers open at least two connections per request. The multi_accept directive should be uncommented and set to on. This informs each worker_process to accept all new connections at a time, opposed to accepting one new connection at a time.
Moving down the file you will see the http block. The first directive to add is keepalive_timeout. The keepalive_timeout determines how many seconds a connection to the client should be kept open before it’s closed by Nginx. This directive should be lowered, as you don’t want idle connections sitting there for up to 75 seconds if they can be utilized by new clients. I have set mine to 15. You can add this directive just above the sendfile on; directive:
http {
##
# Basic Settings
##
keepalive_timeout 15;
sendfile on;
For security reasons, you should uncomment the server_tokens directive and ensure it is set to off. This will disable emitting the Nginx version number in error messages and response headers.
Underneath server_tokens add the client_max_body_size directive and set this to the maximum upload size you require in the WordPress Media Library. I chose a value of 64m.
Further down the http block, you will see a section dedicated to gzip compression. By default, gzip is enabled but you should tweak these values further for better handling of static files. First, you should uncomment the gzip_proxied directive and set it to any, which will ensure all proxied request responses are gzipped. Secondly, you should uncomment the gzip_comp_level and set it to a value of 5. This controls the compression level of a response and can have a value in the range of 1 – 9. Be careful not to set this value too high, as it can have a negative impact on CPU usage. Finally, you should uncomment the gzip_types directive, leaving the default values in place. This will ensure that JavaScript, CSS, and other file types are gzipped in addition to the HTML file type.
That’s the basic Nginx configuration dealt with. Hit CTRL + X followed by Y to save the changes.
In order for Nginx to correctly serve PHP, you also need to ensure the fastcgi_param SCRIPT_FILENAME directive is set. Otherwise, you will receive a blank, white screen when accessing any PHP scripts. Open the fastcgi_params file:
sudo nano /etc/nginx/fastcgi_paramsEnsure the following directive exists, if not add it to the file:
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;To save the fastcgi_params file, hit CTRL + X followed by Y.
You must restart Nginx for the changes to take effect. Before doing so, ensure that the configuration files contain no errors by issuing the following command:
sudo nginx -tIf everything looks OK, go ahead and restart Nginx:
sudo service nginx restarthuypham@pluto:~$ sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
huypham@pluto:~$ sudo service nginx restart
* Restarting nginx [ OK ]
huypham@pluto:~$Install PHP 8.2 and PHP-FPM
Just as with Nginx, the official Ubuntu package repository does contain PHP packages. However, they are not the most up-to-date. Again, I use one maintained by Ondřej Surý for installing PHP. Add the repository and update the package lists as you did for Nginx:
sudo add-apt-repository ppa:ondrej/php -y
sudo apt updateThen install PHP 8.0, as well as all the PHP packages you will require:
sudo apt install php8.2-fpm php8.2-common php8.2-mysql \
php8.2-xml php8.2-xmlrpc php8.2-curl php8.2-gd \
php8.2-imagick php8.2-cli php8.2-dev php8.2-imap \
php8.2-mbstring php8.2-opcache php8.2-redis \
php8.2-soap php8.2-zip -yYou’ll notice php-fpm in the list of packages being installed. FastCGI Process Manager (FPM) is an alternative PHP FastCGI implementation with some additional features that plays really well with Nginx. It’s the recommended process manager to use when installing PHP with Nginx.
After the installation has completed, test PHP and confirm that it has been installed correctly:
php-fpm8.2 -vhuypham@pluto:~$ php-fpm8.2 -v
PHP 8.2.18 (fpm-fcgi) (built: Apr 11 2024 20:37:35)
Copyright (c) The PHP Group
Zend Engine v4.2.18, Copyright (c) Zend Technologies
with Zend OPcache v8.2.18, Copyright (c), by Zend TechnologiesConfigure PHP 8.2 and PHP-FPM
Once Nginx and PHP are installed you need to configure the user and group that the service will run under. As mentioned in the series introduction, this setup does not provide security isolation between sites by configuring PHP pools, so we will run a single PHP pool under your user account.
Open the default pool configuration file:
sudo nano /etc/php/8.2/fpm/pool.d/www.conf<br>Change the following lines, replacing www-data with your username:
user = www-data
group = www-data
listen.owner = www-data
listen.group = www-dataNext, you should adjust your php.ini file to increase the WordPress maximum upload size. Both this and the client_max_body_size directive within Nginx must be changed for the new maximum upload limit to take effect. Open your php.ini file:
sudo nano /etc/php/8.2/fpm/php.iniChange the following lines to match the value you assigned to the client_max_body_size directive when configuring Nginx:
upload_max_filesize = 64M
post_max_size = 64MHit CTRL + X and Y to save the configuration. Before restarting PHP, check that the configuration file syntax is correct:
sudo php-fpm8.2 -thuypham@pluto:~$ sudo php-fpm8.2 -t
[03-May-2024 15:59:39] NOTICE: configuration file /etc/php/8.2/fpm/php-fpm.conf test is successful
If the configuration test was successful, restart PHP using the following command:
sudo service php8.2-fpm restartNow that Nginx and PHP have been installed, you can confirm that they are both running under the correct user by issuing the htop command:
htopIf you hit SHIFT + M, the output will be arranged by memory usage which should bring the nginx and php-fpm8.0 processes into view. You should notice a few occurrences of both nginx and php-fpm.
Both processes will have one instance running under the root user. This is the main process that spawns each worker. The remainder should be running under the username you specified.
top - 08:55:43 up 29 min, 1 user, load average: 0.00, 0.00, 0.00
Tasks: 97 total, 1 running, 94 sleeping, 2 stopped, 0 zombie
%Cpu(s): 0.0 us, 6.2 sy, 0.0 ni, 93.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 981.2 total, 528.4 free, 129.4 used, 323.4 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 700.2 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
676 root 20 0 241232 35892 29620 S 0.0 3.6 0:00.11 php-fpm8.0
680 root 20 0 630404 28408 15544 S 0.0 2.8 0:00.58 snapd
675 root 20 0 29272 17952 10292 S 0.0 1.8 0:00.04 networkd-dispat
341 root 19 -1 51464 13312 12308 S 0.0 1.3 0:00.11 systemd-journal
760 ashley 20 0 241608 12916 6616 S 0.0 1.3 0:00.00 php-fpm8.0
761 ashley 20 0 241608 12916 6616 S 0.0 1.3 0:00.00 php-fpm8.0
888 root 20 0 13796 8916 7472 S 0.0 0.9 0:00.00 sshd
863 root 20 0 12176 7408 6484 S 0.0 0.7 0:00.00 sshd
566 systemd+ 20 0 90228 6056 5292 S 0.0 0.6 0:00.03 systemd-timesyn
998 ubuntu 20 0 13928 5992 4528 S 0.0 0.6 0:00.45 sshd
1096 ashley 20 0 58988 5596 3756 S 0.0 0.6 0:00.00 nginx
If not, go back and check the configuration, and ensure that you have restarted both the Nginx and PHP-FPM services.
Test Nginx and PHP
To check that Nginx and PHP are working together properly, enable PHP in the default Nginx site configuration and create a PHP info file to view in your browser. You are welcome to skip this step, but it’s often handy to check that PHP files can be correctly processed by the Nginx web server.
First, you need to uncomment a section in the default Nginx site configuration which was created when you installed Nginx:
sudo nano /etc/nginx/sites-available/defaultFind the section which controls the PHP scripts.
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/run/php/php8.2-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}
As we’re using php-fpm, we can change that section to look like this:
# pass PHP scripts to FastCGI server
location ~ \.php$ {
include snippets/fastcgi-php.conf;
# With php-fpm (or other unix sockets):
fastcgi_pass unix:/run/php/php8.2-fpm.sock;
}Save the file by using CTRL + X followed by Y. Then, as before, test to make sure the configuration file was edited correctly.
sudo nginx -tIf everything looks okay, go ahead and restart Nginx:
sudo service nginx restartNext, create an info.php file in the default web root, which is /var/www/html.
cd /var/www/html
sudo nano info.phpAdd the following PHP code to that info.php file, and save it by using the same CTRL + X, Y combination.
<?php
phpinfo();
?>Lastly, because you set the user directive in your nginx.conf file to the user you’re currently logged in with, give that user permissions on the info.php file.
sudo chown www-data info.phpNow, if you visit the info.php file in your browser, using the FQDN you set up in chapter 1, you should see the PHP info screen, which means Nginx can process PHP files correctly.
Once you’ve tested this, you can go ahead and delete the info.php file.
sudo rm /var/www/html/info.phpCatch-All Server Block
Currently, when you visit the server’s FQDN in a web browser you will see the Nginx welcome page. However, this usually isn’t the desired behavior. It would be better if the server returned an empty response for unknown domain names.
Begin by removing the following two default site configuration files:
sudo rm /etc/nginx/sites-available/default
sudo rm /etc/nginx/sites-enabled/defaultNow you need to add a catch-all block to the Nginx configuration. Edit the nginx.conf file:
sudo nano /etc/nginx/nginx.confTowards the bottom of the file you’ll find a line that reads:
include /etc/nginx/sites-enabled/*;Underneath that, add the following block:
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name _;
return 444;
}Hit CTRL + X followed by Y to save the changes and then test the Nginx configuration:
sudo nginx -tIf everything looks good, restart Nginx:
sudo service nginx restartNow when you visit the FQDN you should receive an error:
Here’s my final nginx.conf file, after applying all of the above changes. I have removed the mail block, as this isn’t something that’s commonly used.
user ashley;
worker_processes 1;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 1024;
multi_accept on;
}
http {
##
# Basic Settings
##
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 15;
types_hash_max_size 2048;
server_tokens off;
client_max_body_size 64m;
# server_names_hash_bucket_size 64;
# server_name_in_redirect off;
include /etc/nginx/mime.types;
default_type application/octet-stream;
##
# SSL Settings
##
ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;
##
# Logging Settings
##
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
##
# Gzip Settings
##
gzip on;
# gzip_vary on;
gzip_proxied any;
gzip_comp_level 5;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;
##
# Virtual Host Configs
##
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name _;
return 444;
}
}
Installing WP-CLI
If you have never used WP-CLI before, it’s a command-line tool for managing WordPress installations, and greatly simplifies the process of downloading and installing WordPress (plus many other tasks).
Navigate to your home directory:
cd ~/Using cURL, download WP-CLI:
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.pharYou can then check that it works by issuing:
php wp-cli.phar --infoThe command should output information about your current PHP version and a few other details.
To access the command-line tool by simply typing wp, you need to move it into your server’s PATH and ensure that it has execute permissions:
chmod +x wp-cli.phar
sudo mv wp-cli.phar /usr/local/bin/wpYou can now access the WP-CLI tool by typing wp.
NAME
wp
DESCRIPTION
Manage WordPress through the command-line.
SYNOPSIS
wp
SUBCOMMANDS
cache Adds, removes, fetches, and flushes the WP Object Cache object.
cap Adds, removes, and lists capabilities of a user role.
cli Reviews current WP-CLI info, checks for updates, or views defined aliases.
comment Creates, updates, deletes, and moderates comments.
config Generates and reads the wp-config.php file.
core Downloads, installs, updates, and manages a WordPress installation.
Installing MySQL (MariaDB)
To install MariaDB, issue the following command:
apt install mariadb-serverYou can secure MariaDB once it’s installed. Luckily, there’s a built-in script that will prompt you to change a few insecure defaults. However, you’ll first need to change the root user’s authentication method, because by default on Ubuntu installations the root user is not configured to connect using a password. Without the change, it will cause the script to fail and lead to a recursive loop which you can only get out of by closing your terminal window.
Now we can safely run the security script:
sudo mysql_secure_installationFollow the instructions and answer the questions. You’ll enter the password that you just set. Here are my answers:
huypham@pluto:~$ sudo mysql_secure_installation
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
haven't set the root password yet, you should just press enter here.
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password or using the unix_socket ensures that nobody
can log into the MariaDB root user without the proper authorisation.
You already have your root account protected, so you can safely answer 'n'.
Switch to unix_socket authentication [Y/n]
Enabled successfully!
Reloading privilege tables..
... Success!
You already have your root account protected, so you can safely answer 'n'.
Change the root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n]
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
That’s all for this step. In the next step I will guide you through the process of setting up your first WordPress site and how to manage multiple WordPress installs.