Nginx Config Generator — Reverse Proxy Guide 2026

✓ Last tested: June 2026 · Verified against Nginx 1.24+

1. Field Notes: The Infinite Redirect Loop

Early in my DevOps journey, I was tasked with migrating a monolithic Python application to a new VPS. I set up Nginx to handle SSL termination (HTTPS) and proxy requests back to the Python app running on HTTP (port 5000).

Immediately upon deploying, the site went down with an ERR_TOO_MANY_REDIRECTS error.

I checked the app—it was fine. I checked Cloudflare—it was fine. The culprit was my Nginx config. I forgot to pass the X-Forwarded-Proto header. The Python app thought it was being accessed via HTTP, so it sent a 301 redirect back to HTTPS. Nginx caught the HTTPS request, proxied it via HTTP, and the loop began.

A single missing line in nginx.conf took down production. This is why I use configuration generators today.

---

2. Nginx Config File Structure — Explained

Nginx configuration is built on a context tree.

1. Main Context: Global settings like worker_processes.
2. Events Context: Connection handling (e.g., worker_connections 1024).
3. HTTP Context: Defines settings for all web traffic (Gzip, logging formats).
4. Server Context: Defines a specific website/domain (Virtual Host).
5. Location Context: Defines how to handle specific URL paths (e.g., /api vs /images).

---

3. Common Nginx Setups — Generated Configs

1. The Reverse Proxy (Node.js / Python / Go)

This is the most common use case. Nginx handles the public internet and proxies traffic to an app running locally on port 3000.

server {
    listen 80;
    server_name myapp.com;

    location / {
        proxy_pass http://127.0.0.1:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

2. The Static React / Vue / SPA Server

If you have a compiled frontend, Nginx serves the files directly. The critical part here is try_files to allow client-side React Router to work without hitting a 404.

server {
    listen 80;
    server_name myfrontend.com;
    root /var/www/html/build;
    index index.html;

    location / {
        try_files $uri $uri/ /index.html;
    }
}

---

4. Nginx Performance Tuning — worker_processes and gzip

By default, Nginx is fast, but it can be faster.

• worker_processes auto; — Tells Nginx to spawn one worker per CPU core.
• gzip on; — Compresses text-based responses (HTML, CSS, JS) before sending them over the network. Always ensure gzip_types includes application/json for API responses.

---

5. Common Nginx Config Errors and Fixes

• Error: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
  • Fix: Apache or another process is running on port 80. Run sudo netstat -tulpn | grep :80 to find it and kill it.
• Error: 413 Request Entity Too Large
  • Fix: You are trying to upload a file larger than the default 1MB limit. Add client_max_body_size 50M; to your server block.

---

Need to deploy a server without wrestling with syntax errors? Use our free Nginx Config Generator to build highly optimized, secure configuration files visually →

---

External Sources

• Nginx Official Documentation: Reverse Proxy
• Mozilla Web Security Guidelines for Web Servers

---

Abu Sufyan · Full-stack developer · Founder of WebToolkit Pro Github

Last updated: June 2026