Linux & System Administration Tools

Nginx Reverse Proxy Generator

Generate an Nginx reverse proxy configuration with backend host/port, proxy headers, and optional WebSocket support.

Enter your domain and backend host/port - this tool generates a reverse proxy server block with the standard headers most backend apps expect.

Domain

Backend Host

Backend Port

Enable WebSocket support (adds Upgrade/Connection headers)

More Linux & System Administration Tools

View all 17

Nginx Redirect Generator SSH Command Generator Apache .htaccess Generator SSH Config Generator Nginx Config Generator SCP Command Generator systemd Service Generator Rsync Command Generator

Pair this with the Nginx Config Generator's SSL/HTTPS options if your proxy also needs to terminate SSL.

What Is an Nginx Reverse Proxy?

An Nginx reverse proxy forwards incoming requests to a backend application (running on a different port or server) while remaining the public-facing entry point - commonly used in front of Node.js, Python, or other application servers.

Why Use This Tool?

A working reverse proxy needs several headers passed through correctly (Host, X-Real-IP, X-Forwarded-For, X-Forwarded-Proto) so your backend application sees accurate request information - easy to forget one when writing this by hand.

How to Use It

Enter your public domain and the backend host/port to proxy to.
Enable WebSocket support if your app uses it (adds the Upgrade/Connection headers).
Copy the generated server block into your Nginx configuration.

Limitations

This is a solid starting reverse proxy configuration - review timeout values, buffer sizes, and SSL setup for your specific backend's needs before relying on it in production.

Frequently Asked Questions

Nginx receives visitor requests and forwards them to your application server (for example Node.js on port 3000), then sends the response back. It can also handle HTTPS and caching.

Headers such as X-Forwarded-For and X-Forwarded-Proto tell your app the visitor's real IP and whether the original request used HTTPS.

WebSockets upgrade the HTTP connection, so Nginx must pass the Upgrade and Connection headers and use HTTP/1.1 to the backend.