Bird
Raised Fist0
Nginxdevops~5 mins

First Nginx configuration - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
Nginx is a web server that helps deliver websites to users. This configuration sets up a simple website so your server can respond to web requests.
When you want to serve a basic website from your server.
When you need to test if Nginx is installed and working correctly.
When you want to learn how to configure a web server step-by-step.
When you want to serve static files like HTML or images.
When you want to listen on a specific port for web traffic.
Config File - nginx.conf
nginx.conf
events {}
http {
    server {
        listen 8080;
        server_name localhost;

        location / {
            root /usr/share/nginx/html;
            index index.html;
        }
    }
}

This file tells Nginx to listen on port 8080 for web requests.

The server block defines how to handle requests.

The location / block serves files from /usr/share/nginx/html, starting with index.html.

Commands
Start Nginx using the custom configuration file in the current directory.
Terminal
sudo nginx -c $(pwd)/nginx.conf
Expected OutputExpected
No output (command runs silently)
→
-c - Specify the path to the configuration file.
Check if Nginx is serving the default page on port 8080.
Terminal
curl http://localhost:8080
Expected OutputExpected
<!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> </head> <body> <h1>Welcome to nginx!</h1> </body> </html>
Stop the Nginx server after testing to free the port.
Terminal
sudo nginx -s quit
Expected OutputExpected
No output (command runs silently)
→
-s quit - Send the quit signal to the Nginx process.
Key Concept

If you remember nothing else from this pattern, remember: the nginx.conf file controls how Nginx listens and serves files.

Common Mistakes
Not specifying the full path to the custom nginx.conf file when starting Nginx.
Nginx will use the default config and ignore your custom settings.
Use the -c flag with the full or relative path to your nginx.conf file.
Trying to access Nginx on port 80 when it is configured to listen on port 8080.
The browser or curl will not connect because Nginx is not listening on port 80.
Use the correct port number in the URL, like http://localhost:8080.
Not stopping Nginx after testing, causing port conflicts later.
The port remains in use and starting Nginx again will fail.
Run 'sudo nginx -s quit' to cleanly stop the server.
Summary
Create an nginx.conf file to tell Nginx which port to listen on and where to find website files.
Start Nginx with the custom config using 'sudo nginx -c nginx.conf'.
Test the server response with 'curl http://localhost:8080'.
Stop Nginx after testing with 'sudo nginx -s quit'.

Practice

(1/5)
1. What is the purpose of the server block in an Nginx configuration?
easy
A. To start the Nginx service
B. To define settings for a specific website or domain
C. To specify the operating system
D. To install Nginx modules

Solution

  1. Step 1: Understand Nginx configuration structure

    Nginx uses server blocks to group settings for each website or domain it serves.

  2. Step 2: Identify the role of server block

    The server block tells Nginx how to handle requests for a particular site, including ports and root folder.

  3. Final Answer:

    To define settings for a specific website or domain -> Option B

  4. Quick Check:

    server block = website settings [OK]
Hint: Remember: server block = one website config [OK]
Common Mistakes:
  • Confusing server block with service start command
  • Thinking server block installs software
  • Mixing server block with OS settings
2. Which of the following is the correct syntax to listen on port 80 in an Nginx server block?
easy
A. listen: 80
B. listen = 80;
C. listen 80;
D. port 80;

Solution

  1. Step 1: Recall Nginx directive syntax

    Nginx directives end with a semicolon and use space-separated key and value.

  2. Step 2: Check the correct listen syntax

    The correct way to specify port 80 is listen 80; without equals or colon.

  3. Final Answer:

    listen 80; -> Option C

  4. Quick Check:

    listen 80; = correct syntax [OK]
Hint: Nginx directives end with semicolon, no equals sign [OK]
Common Mistakes:
  • Using equals sign (=) in directives
  • Using colon (:) instead of space
  • Omitting semicolon at end
3. Given this Nginx configuration snippet, what is the root folder for the website? 
server {
    listen 80;
    root /var/www/html;
    index index.html;
}
medium
A. /home/user
B. /etc/nginx
C. /usr/share/nginx
D. /var/www/html

Solution

  1. Step 1: Locate the root directive

    The root directive sets the folder where website files are served from.

  2. Step 2: Read the root path value

    Here, root /var/www/html; means the website files are in /var/www/html.

  3. Final Answer:

    /var/www/html -> Option D

  4. Quick Check:

    root folder = /var/www/html [OK]
Hint: Look for root directive to find website folder [OK]
Common Mistakes:
  • Confusing root with index directive
  • Assuming default folder without checking config
  • Mixing root with Nginx installation folders
4. Identify the error in this Nginx configuration snippet: 
server {
    listen 80
    root /var/www/html;
    index index.html;
}
medium
A. Missing semicolon after listen 80
B. Wrong root path
C. index directive should be index.htm
D. listen directive should be inside location block

Solution

  1. Step 1: Check syntax of each directive

    Each directive must end with a semicolon in Nginx configuration.

  2. Step 2: Identify missing semicolon

    The line listen 80 is missing a semicolon at the end.

  3. Final Answer:

    Missing semicolon after listen 80 -> Option A

  4. Quick Check:

    Every directive ends with ; [OK]
Hint: Check every line ends with semicolon [OK]
Common Mistakes:
  • Forgetting semicolon after directives
  • Placing listen inside location block incorrectly
  • Changing root path without reason
5. You want to serve a website on port 8080 with files located in /home/user/site and the main page named home.html. Which Nginx server block is correct?
hard
A. server { listen 8080; root /home/user/site; index home.html; }
B. server { listen 80; root /home/user/site; index home.html; }
C. server { listen 8080; root /var/www/html; index index.html; }
D. server { listen 8080; root /home/user/site; index index.html; }

Solution

  1. Step 1: Match the listen port

    The question requires port 8080, so listen 8080; is needed.

  2. Step 2: Match root and index directives

    Root must be /home/user/site and index must be home.html as given.

  3. Final Answer:

    server { listen 8080; root /home/user/site; index home.html; } -> Option A

  4. Quick Check:

    Port 8080 + correct root + correct index = server { listen 8080; root /home/user/site; index home.html; } [OK]
Hint: Match all three: listen, root, index exactly [OK]
Common Mistakes:
  • Using default port 80 instead of 8080
  • Wrong root folder path
  • Wrong index file name