Keepalive connections in Nginx - Mini Project: Build & Apply

Configuring Keepalive Connections in Nginx

📖 Scenario: You are managing a web server using Nginx. To improve performance and reduce latency, you want to enable keepalive connections between Nginx and the backend servers. This allows Nginx to reuse TCP connections for multiple requests instead of opening a new connection each time.

🎯 Goal: Configure Nginx to use keepalive connections with a backend server by setting up an upstream block and enabling keepalive connections with a specific number of idle connections.

📋 What You'll Learn

Create an upstream block named backend with one server at 127.0.0.1:8080

Add a keepalive directive inside the upstream block with the value 16

Configure the server block to proxy requests to the backend upstream

Print the final Nginx configuration snippet

💡 Why This Matters

🌍 Real World

Keepalive connections reduce the time and resources needed to open new TCP connections, improving web server performance and user experience.

💼 Career

Understanding and configuring keepalive connections is essential for DevOps engineers managing web servers and optimizing application delivery.

1

Create the upstream block

Create an upstream block called backend with one server at 127.0.0.1:8080.

Nginx

# Your code here

Hint

The upstream block groups backend servers. Use upstream backend { ... } and add the server inside.

2

Add keepalive directive

Inside the backend upstream block, add the keepalive 16; directive to allow 16 idle keepalive connections.

Nginx

upstream backend {
    server 127.0.0.1:8080;
    # Your code here
}

Hint

The keepalive directive sets how many idle connections Nginx keeps open to reuse.

3

Configure server block to proxy requests

Create a server block that listens on port 80 and proxies all requests to the backend upstream using proxy_pass http://backend; inside the location / block.

Nginx

upstream backend {
    server 127.0.0.1:8080;
    keepalive 16;
}

# Your code here

Hint

The server block listens on port 80 and forwards requests to the upstream backend using proxy_pass.

4

Print the final Nginx configuration

Print the complete Nginx configuration including the upstream backend block with keepalive 16; and the server block proxying requests to backend.

Nginx

upstream backend {
    server 127.0.0.1:8080;
    keepalive 16;
}

server {
    listen 80;

    location / {
        proxy_pass http://backend;
    }
}

# Your code here

Hint

Use a print statement to display the full configuration exactly as written.

Practice

1. What is the main benefit of using keepalive connections in nginx?

easy

A. They disable caching on the server.

B. They close connections immediately after each request.

C. They increase the number of open connections indefinitely.

D. They reuse the same connection for multiple requests, improving speed.

Solution

1. Step 1: Understand what keepalive connections do

   Keepalive connections allow the same connection to be reused for multiple requests instead of opening a new one each time.

2. Step 2: Identify the benefit of reusing connections

   Reusing connections reduces the time and resources needed to establish new connections, thus improving speed and reducing server load.

3. Final Answer:

   They reuse the same connection for multiple requests, improving speed. -> Option D

4. Quick Check:

   Keepalive = reuse connection for speed [OK]

Hint: Keepalive means reuse connection to speed up requests [OK]

Common Mistakes:

• Thinking keepalive closes connections immediately
• Believing keepalive increases open connections endlessly
• Confusing keepalive with caching

2. Which of the following is the correct syntax to set the keepalive timeout to 30 seconds in nginx?

easy

A. keepalive_timeout 30s

B. keepalive_timeout 30;

C. keepalive_timeout: 30s;

D. keepalive_timeout = 30;

Solution

1. Step 1: Recall nginx directive syntax

   Nginx directives use the format: directive_name value; without equal signs or colons.

2. Step 2: Check the correct value format for time

   Timeout values in nginx can be specified as numbers (seconds) without units or with units like 's'. Both are accepted, but the common practice is just a number for seconds.

3. Final Answer:

   keepalive_timeout 30; -> Option B

4. Quick Check:

   Directive syntax = name value; no '=' or ':' [OK]

Hint: Nginx directives use 'name value;' syntax without '=' [OK]

Common Mistakes:

• Using '=' sign in directive
• Adding colon ':' after directive name
• Adding units like 's' unnecessarily

3. Given this nginx configuration snippet:

keepalive_timeout 10;
keepalive_requests 100;

What happens after 100 requests on the same keepalive connection?

medium

A. The connection is closed and a new one is opened for the next request.

B. The connection stays open indefinitely.

C. The server resets the timeout to 10 seconds again.

D. The connection is closed immediately after the first request.

Solution

1. Step 1: Understand keepalive_requests directive

   This directive limits how many requests can be sent over one keepalive connection before it closes.

2. Step 2: Apply the limit of 100 requests

   After 100 requests, nginx closes the connection and opens a new one for the next request to avoid stale connections.

3. Final Answer:

   The connection is closed and a new one is opened for the next request. -> Option A

4. Quick Check:

   keepalive_requests = max requests per connection [OK]

Hint: keepalive_requests limits requests per connection [OK]

Common Mistakes:

• Thinking connection stays open forever
• Confusing timeout with request count
• Assuming connection closes after first request

4. You set keepalive_timeout 20; but clients report connections close too quickly. Which is the likely mistake?

medium

A. The keepalive_requests is set to 1, closing after one request.

B. The timeout value is too low for client needs.

C. You forgot to reload nginx after changing config.

D. The server is running an old nginx version without keepalive support.

Solution

1. Step 1: Check common reasons for config changes not applying

   If nginx is not reloaded or restarted after config changes, old settings remain active.

2. Step 2: Confirm reload necessity

   After changing keepalive_timeout, nginx must be reloaded with nginx -s reload or restarted to apply changes.

3. Final Answer:

   You forgot to reload nginx after changing config. -> Option C

4. Quick Check:

   Config changes need reload to apply [OK]

Hint: Reload nginx after config changes to apply them [OK]

Common Mistakes:

• Assuming timeout value alone fixes issue
• Ignoring need to reload nginx
• Blaming nginx version without checking

5. You want to optimize nginx for many short requests by keeping connections alive but closing them after 15 seconds or 50 requests, whichever comes first. Which configuration is correct?

hard

A. keepalive_timeout 15;\nkeepalive_requests 50;

B. keepalive_timeout 50;\nkeepalive_requests 15;

C. keepalive_timeout 15s;\nkeepalive_requests 50s;

D. keepalive_timeout 15s;\nkeepalive_requests 50; keepalive_disable none;

Solution

1. Step 1: Set keepalive_timeout to 15 seconds

   This controls how long a connection stays open waiting for new requests.

2. Step 2: Set keepalive_requests to 50

   This limits the number of requests per connection before closing it.

3. Step 3: Verify correct syntax and values

   keepalive_timeout 15;\nkeepalive_requests 50; uses correct syntax and values matching the requirement: 15 seconds timeout and 50 requests limit.

4. Final Answer:

   keepalive_timeout 15;\nkeepalive_requests 50; -> Option A

5. Quick Check:

   Timeout 15 + Requests 50 = correct config [OK]

Hint: Timeout sets seconds, requests sets max requests per connection [OK]

Common Mistakes:

• Swapping timeout and requests values
• Adding units to keepalive_requests
• Using invalid directives like keepalive_disable