How To Install Linux, Nginx, MySQL, PHP (LEMP stack) on Debian 9

Published on September 13, 2018
How To Install Linux, Nginx, MySQL, PHP (LEMP stack) on Debian 9
Not using Debian 9?Choose a different version or distribution.
Debian 9


The LEMP software stack is a group of software that can be used to serve dynamic web pages and web applications. This is an acronym that describes a Linux operating system, with an Nginx web server. The backend data is stored in the MySQL database and the dynamic processing is handled by PHP.

In this guide, you’ll install a LEMP stack on a Debian server using the packages provided by the operating system.


To complete this guide, you will need a Debian 9 server with a non-root user with sudo privileges. You can set up a user with these privileges in our Initial Server Setup with Debian 9 guide.

Step 1 — Installing the Nginx Web Server

In order to display web pages to our site visitors, we are going to employ Nginx, a modern, efficient web server.

All of the software we will be using for this procedure will come directly from Debian’s default package repositories. This means we can use the apt package management suite to complete the installation.

Since this is our first time using apt for this session, we should start off by updating our local package index. We can then install the server:

  1. sudo apt update
  2. sudo apt install nginx

On Debian 9, Nginx is configured to start running upon installation.

If you have the ufw firewall running, you will need to allow connections to Nginx. You should enable the most restrictive profile that will still allow the traffic you want. Since we haven’t configured SSL for our server yet, in this guide, we will only need to allow traffic on port 80.

You can enable this by typing:

  1. sudo ufw allow 'Nginx HTTP'

You can verify the change by typing:

  1. sudo ufw status

You should see HTTP traffic allowed in the displayed output:

Status: active To Action From -- ------ ---- OpenSSH ALLOW Anywhere Nginx HTTP ALLOW Anywhere OpenSSH (v6) ALLOW Anywhere (v6) Nginx HTTP (v6) ALLOW Anywhere (v6)

Now, test if the server is up and running by accessing your server’s domain name or public IP address in your web browser. If you do not have a domain name pointed at your server and you do not know your server’s public IP address, you can find it by typing one of the following into your terminal:

  1. ip addr show eth0 | grep inet | awk '{ print $2; }' | sed 's/\/.*$//'

This will print out a few IP addresses. You can try each of them in turn in your web browser.

Type one of the addresses that you receive in your web browser. It should take you to Nginx’s default landing page:


Nginx default page

If you see the above page, you have successfully installed Nginx.

Step 2 — Installing MySQL to Manage Site Data

Now that we have a web server, we need to install MySQL, a database management system, to store and manage the data for our site.

You can install this easily by typing:

  1. sudo apt install mysql-server

Note: In Debian 9 a community fork of the MySQL project – MariaDB – is packaged as the default MySQL variant. While, MariaDB works well in most cases, if you need features found only in Oracle’s MySQL, you can install and use packages from a repository maintained by the MySQL developers. To install the official MySQL server, use our tutorial How To Install the Latest MySQL on Debian 9.

The MySQL database software is now installed, but its configuration is not complete.

To secure the installation, we can run a security script that will ask whether we want to modify some insecure defaults. Begin the script by typing:

  1. sudo mysql_secure_installation

You will be asked to enter the password for the MySQL root account. We haven’t set this yet, so just hit ENTER. Then you’ll be asked you if you want to set that password. You should type y then set a root password.

For the rest of the questions the script asks, you should press y, followed by the ENTER key at each prompt. This will remove some anonymous users and the test database, disable remote root logins, and load these new rules so that MySQL immediately respects the changes you have made.

At this point, your database system is now set up and secured. Let’s set up PHP.

Step 3 — Installing PHP for Processing

We now have Nginx installed to serve our pages and MySQL installed to store and manage our data. However, we still don’t have anything that can generate dynamic content. That’s where PHP comes in.

Since Nginx does not contain native PHP processing like some other web servers, we will need to install fpm, which stands for “fastCGI process manager”. We will tell Nginx to pass PHP requests to this software for processing. We’ll also install an additional helper package that will allow PHP to communicate with our MySQL database backend. The installation will pull in the necessary PHP core files to make that work.

Then install the php-fpm and php-mysql packages:

  1. sudo apt install php-fpm php-mysql

We now have our PHP components installed. Next we’ll configure Nginx to use them.

Step 4 — Configuring Nginx to Use the PHP Processor

Now we have all of the required components installed. The only configuration change we still need is to tell Nginx to use our PHP processor for dynamic content.

We do this on the server block level (server blocks are similar to Apache’s virtual hosts). We’re going to leave the default Nginx configuration alone and instead create a new configuration file and new web root directory to hold our PHP files. We’ll name the configuration file and the directory after the domain name or hostname that the server should respond to.

First, create a new directory in /var/www to hold the PHP site:

  1. sudo mkdir /var/www/your_domain

Then, open a new configuration file in Nginx’s sites-available directory:

  1. sudo nano /etc/nginx/sites-available/your_domain

This will create a new blank file. Paste in the following bare-bones configuration:

server {
    listen 80;
    listen [::]:80;

    root /var/www/your_domain;
    index index.php index.html index.htm;

    server_name your_domain;

    location / {
        try_files $uri $uri/ =404;

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;

This is a very basic configuration that listens on port 80 and serves files from the web root we just created. It will only respond to requests to the name provided after server_name, and any files ending in .php will be processed by the php-fpm process before Nginx sends the results to the user.

Save and close the file when you’re done customizing it.

Activate your configuration by linking to the config file from Nginx’s sites-enabled directory:

  1. sudo ln -s /etc/nginx/sites-available/your_domain.conf /etc/nginx/sites-enabled/

This will tell Nginx to use the configuration next time it is reloaded. First, test your configuration for syntax errors by typing:

  1. sudo nginx -t

If any errors are reported, go back and recheck your file before continuing.

When you are ready, reload Nginx to make the changes:

  1. sudo systemctl reload nginx

Next we’ll create a file in our new web root directory to test out PHP processing.

Step 5 — Create a PHP File to Test Configuration

Your LEMP stack should now be completely set up. We can test it to validate that Nginx can correctly hand .php files off to our PHP processor.

We can do this by creating a test PHP file in our document root. Open a new file called info.php within your document root in your text editor:

  1. sudo nano /var/www/your_domain/info.php

Type or paste the following lines into the new file. This is valid PHP code that will return information about our server:


When you are finished, save and close the file.

Now, you can visit this page in your web browser by visiting your server’s domain name or public IP address followed by /info.php:


You should see a web page that has been generated by PHP with information about your server:

PHP page info

If you see a page that looks like this, you’ve set up PHP processing with Nginx successfully.

After verifying that Nginx renders the page correctly, it’s best to remove the file you created as it can actually give unauthorized users some hints about your configuration that may help them try to break in.

For now, remove the file by typing:

  1. sudo rm /var/www/html/info.php

You can always regenerate this file if you need it later.


You should now have a LEMP stack configured on your Debian server. This gives you a very flexible foundation for serving web content to your visitors.

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about our products

About the authors

Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Good tutorial, thanks.

There’s a typo in the symlink part. “.conf” shouldn’t be in the file name there, otherwise it will create a symlink to nowhere, as we didn’t use “.conf” in the original sites-available one.

Hi, edit this line your_domain.conf to make it consistent throughout, because it creates confusion. Anyone copy-pasting it would have conflicts. Use your_domain placeholder all through.

sudo ln -s /etc/nginx/sites-available/your_domain.conf /etc/nginx/sites-enabled/

Here i too work removing “conf” in command line

Someone else mentioned it here, I am pretty sure you don’t need the .conf format in sites-enabled. I followed the tutorial and I could not get nginx to read the config file, so I just linked it with no .conf and it worked.

404 Not Found nginx/1.10.3

"This is a very basic configuration that listens on port 80 and serves files from the web root we just created. It will only respond to requests to the name provided after server_name, and any files ending in .php will be processed by the php-fpm process before Nginx sends the results to the user.

Save and close the file when you’re done customizing it."

Everything worked great until I got to this part. “Save and close the file…”

I was not able to do that. Save it or close it. I am looking through nginx info and even things like :x and :wq which may save it, but the console shows the same thing with a list of commands using up arrow and a letter. None of them said save and exit and when I tried any of them, they did nothing anyway… Save and close! It sounds SO easy!

I don’t think I understand it correctly. Trying to set thing up for a gaming system at 7sultans. Almost done, but having some troubles with Node.js. Actually, I did get it, thank to your guide but still… have no clue what that line means.

This comment has been deleted

    Try DigitalOcean for free

    Click below to sign up and get $200 of credit to try our products over 60 days!

    Sign up

    Join the Tech Talk
    Success! Thank you! Please check your email for further details.

    Please complete your information!

    Featured on Community

    Get our biweekly newsletter

    Sign up for Infrastructure as a Newsletter.

    Hollie's Hub for Good

    Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

    Become a contributor

    Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

    Welcome to the developer cloud

    DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

    Learn more
    DigitalOcean Cloud Control Panel