Nginxdevops~30 mins

WebSocket proxying in Nginx - Mini Project: Build & Apply

Choose your learning style10 modes available

Learn Why Deep Visual Try Challenge Project Recall Time

WebSocket Proxying with Nginx

📖 Scenario: You are setting up a web server to forward WebSocket connections from clients to a backend WebSocket server. This is common when you want to use Nginx as a reverse proxy to handle WebSocket traffic securely and efficiently.

🎯 Goal: Configure Nginx to proxy WebSocket connections correctly by setting up the necessary headers and connection upgrade directives.

📋 What You'll Learn

Create a basic Nginx server block listening on port 80

Add a variable for the backend WebSocket server URL

Configure proxy settings to handle WebSocket upgrade headers

Print the final Nginx configuration to verify correctness

💡 Why This Matters

🌍 Real World

WebSocket proxying is used to enable real-time communication in web apps, such as chat apps or live notifications, by forwarding WebSocket traffic through a reverse proxy like Nginx.

💼 Career

Understanding how to configure Nginx for WebSocket proxying is a valuable skill for DevOps engineers and system administrators managing scalable, real-time web services.

Progress0 / 4 steps

Create a basic Nginx server block

Write an Nginx server block that listens on port 80 and has a location /ws/ to proxy requests. Use proxy_pass http://backend_ws_server; inside the location block.

Nginx

server {
    listen 80;
    location /ws/ {
        # Your code here
    }
}

Hint

Start with a server block, add listen 80;, then add a location /ws/ block with proxy_pass http://backend_ws_server;.

Add a variable for the backend WebSocket server URL

Define an upstream block named backend_ws_server with the server address 127.0.0.1:8080 before the server block.

Nginx

upstream backend_ws_server {
    # Your code here
}

server {
    listen 80;
    location /ws/ {
        proxy_pass http://backend_ws_server;
    }
}

Hint

Use upstream backend_ws_server { server 127.0.0.1:8080; } to define the backend server.

Configure proxy settings for WebSocket upgrade

Inside the location /ws/ block, add these directives exactly: proxy_http_version 1.1;, proxy_set_header Upgrade $http_upgrade;, proxy_set_header Connection "upgrade";, and proxy_set_header Host $host;.

Nginx

upstream backend_ws_server {
    server 127.0.0.1:8080;
}

server {
    listen 80;
    location /ws/ {
        proxy_pass http://backend_ws_server;
        # Your code here
    }
}

Hint

These headers are needed to tell Nginx to handle WebSocket upgrades properly.

Print the final Nginx configuration

Write a command to print the contents of the Nginx configuration file /etc/nginx/nginx.conf to verify your setup.

Nginx

upstream backend_ws_server {
    server 127.0.0.1:8080;
}

server {
    listen 80;
    location /ws/ {
        proxy_pass http://backend_ws_server;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
    }
}

# Your code here

Hint

Use cat /etc/nginx/nginx.conf to display the configuration file contents.

Practice

(1/5)

1. What is the main reason to use proxy_set_header Upgrade $http_upgrade; in nginx when proxying WebSocket connections?

easy

A. To tell nginx to allow the connection to switch protocols to WebSocket

B. To set the client's IP address in the header

C. To enable gzip compression for WebSocket data

D. To disable caching for WebSocket requests

5. You want to proxy WebSocket connections through nginx to two backend servers for load balancing. Which configuration snippet correctly supports WebSocket proxying with load balancing?

hard

A. upstream ws_backend { server backend1.example.com; server backend2.example.com; } location /ws/ { proxy_pass http://ws_backend; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "close"; }

B. upstream ws_backend { server backend1.example.com; server backend2.example.com; } location /ws/ { proxy_pass http://ws_backend; proxy_http_version 1.0; proxy_set_header Upgrade websocket; proxy_set_header Connection "keep-alive"; }

C. upstream ws_backend { server backend1.example.com; server backend2.example.com; } location /ws/ { proxy_pass http://ws_backend; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }

D. upstream ws_backend { server backend1.example.com; server backend2.example.com; } location /ws/ { proxy_pass http://ws_backend; proxy_http_version 2.0; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }

Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard

WebSocket proxying in Nginx - Mini Project: Build & Apply

Practice

Solution

Step 1: Understand the Upgrade header role

Step 2: Recognize nginx's proxy_set_header usage

Final Answer:

Quick Check:

Solution

Step 1: Identify required HTTP version for WebSocket

Step 2: Check correct headers for WebSocket

Final Answer:

Quick Check:

Solution

Step 1: Analyze HTTP version and headers

Step 2: Understand nginx behavior with this config

Final Answer:

Quick Check:

Solution

Step 1: Check Connection header value

Step 2: Identify impact of incorrect Connection header

Final Answer:

Quick Check:

Solution

Step 1: Confirm HTTP version and headers for WebSocket

Step 2: Check load balancing setup and header correctness

Final Answer:

Quick Check:

Ready to prove it?