First Nginx configuration - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the server to listen on port 80.

Nginx

server {
    listen [1];
}

Drag options to blanks, or click blank then click option'

A22

B443

C8080

D80

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 443 which is for HTTPS, not HTTP.

Using port 22 which is for SSH, not web traffic.

The listen directive tells Nginx which port to listen on. Port 80 is the default for HTTP.

2fill in blank

medium

Complete the code to set the root directory for the website files.

Nginx

server {
    root [1];
}

Drag options to blanks, or click blank then click option'

A/var/log/nginx

B/etc/nginx

C/var/www/html

D/home/user

Attempts:

3 left

💡 Hint

Common Mistakes

Using /var/log/nginx which is for logs, not website files.

Using /etc/nginx which is for configuration files.

The root directive sets the folder where Nginx looks for website files. /var/www/html is the common default.

3fill in blank

hard

Fix the error in the location block to serve all requests with index.html.

Nginx

location / {
    try_files [1] =404;
}

Drag options to blanks, or click blank then click option'

A$uri/index.htm

B$uri $uri/ index.html

Cindex.html

D$uri/index.html

Attempts:

3 left

💡 Hint

Common Mistakes

Using only one file name without trying the URI first.

Using incorrect file extensions like .htm instead of .html.

The try_files directive tries the listed files in order. $uri $uri/ index.html tries the requested URI, then URI as a folder, then index.html.

4fill in blank

hard

Fill both blanks to create a server block that listens on port 8080 and serves files from /usr/share/nginx/html.

Nginx

server {
    listen [1];
    root [2];
}

Drag options to blanks, or click blank then click option'

A8080

B/var/www/html

C/usr/share/nginx/html

D80

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 80 instead of 8080 as requested.

Using the wrong root directory.

Port 8080 is often used for testing or alternative HTTP ports. The root directory /usr/share/nginx/html is a common location for Nginx website files.

5fill in blank

hard

Fill all three blanks to create a location block that serves static files and sets the index file to index.html.

Nginx

location /static/ {
    root [1];
    index [2];
    autoindex [3];
}

Drag options to blanks, or click blank then click option'

A/var/www

Bindex.html

Con

Doff

Attempts:

3 left

💡 Hint

Common Mistakes

Setting autoindex to 'on' which shows directory contents.

Using wrong root path.

The root directive sets the base folder for static files. index sets the default file to serve. autoindex off disables directory listing for security.

Practice

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