Output
Output will appear here
Click in the output to select all text
Nginx Reverse Proxy Config Generator
Related tools
Featured
Dockerfile Generator
Generate a starter Dockerfile for Node.js, Python, Go, or a static site, with a configurable base image, port, and start command.
Dockerfile generatorDocker generator
Featured
CSP Header Generator
Build a Content-Security-Policy header from per-directive source lists (default-src, script-src, style-src, img-src, and more).
Csp header generatorContent security policy generator
Featured
Gitignore Generator
Generate a .gitignore file by combining language and editor presets (Node, Python, Java, macOS, VS Code, and more).
Gitignore generatorGitignore
This Nginx Config Generator produces a working server block that reverse-proxies requests to a local app — the config most people copy-paste when putting Nginx in front of a Node, Python, or other backend process. Enter your domain and the port your app listens on, optionally include SSL certificate directives (for use with Let's Encrypt/Certbot paths) and a www subdomain, and get a complete, correctly indented config block with the standard proxy headers (X-Forwarded-For, X-Forwarded-Proto, WebSocket upgrade support) already included. It's meant as a solid starting point to drop into /etc/nginx/sites-available/. Everything runs in your browser; nothing about your server is uploaded. Scroll down to configure your options.
Features
- Generates a complete Nginx server block
- Includes standard proxy headers and WebSocket upgrade support
- Optional SSL certificate directives (Let's Encrypt path convention)
- Optional www subdomain inclusion
- One-click copy or download
Why use this nginx reverse proxy config generator?
- Faster than assembling a proxy config from memory
- Avoids missing critical proxy headers
- Fully private — nothing about your setup is uploaded
- Free with unlimited use
Frequently asked questions
Do I need to edit anything before using this config?
Update the SSL certificate paths if you enabled SSL (they assume a standard Let's Encrypt/Certbot layout), and verify the backend port matches where your app actually listens.
Where do I put this file?
Typically in /etc/nginx/sites-available/yourdomain.conf, then symlinked into /etc/nginx/sites-enabled/ and reloaded with `nginx -s reload`.
Why are the proxy headers included?
They forward the original client IP, protocol, and host to your backend app, and the Upgrade/Connection headers allow WebSocket connections to pass through the proxy correctly.
Does this set up SSL certificates for me?
No, it only adds the directives pointing to certificate files; you still need to obtain certificates separately, e.g. via Certbot.
Can I use this for load balancing multiple backends?
This generates a single-backend proxy_pass block; for load balancing you'd extend it with an nginx `upstream` block listing multiple servers.