Web Server Tools

Nginx Reverse Proxy Generator

Generate an Nginx reverse proxy block that puts a Node.js, Python or other app behind your domain, with optional WebSocket support.

Free & instant No signup How to use FAQ

Domain

Backend Host

Backend Port

Enable WebSocket support (adds Upgrade/Connection headers)

Not sure what to enter?

Enter your domain and the port your app listens on to get a proxy_pass block that forwards visitors to it with the correct headers.

How do I put my app behind Nginx?

Run the app on a private port (for example 3000) and let Nginx forward requests for your domain to it with proxy_pass. Nginx then handles HTTPS and passes the visitor's real IP and protocol to the app in headers. This generator writes that block, with WebSocket support if your app needs it.

How to create a reverse proxy config

Enter the domain visitors will use.
Enter the backend host and port your app listens on (usually 127.0.0.1 and the app's port).
Tick WebSocket support if the app uses live connections.
Click Generate, save the block in your Nginx config and reload.

Related checks

To see whether the app answers through the proxy, use the Website Status Checker.
To check which headers the proxied site returns, use the HTTP Headers Checker.

When the proxy is live, the Website Status Checker and Website Response Time Checker show whether the app answers through Nginx and how fast - and JustChecker monitoring alerts you if the app behind the proxy stops responding.

Frequently Asked Questions

Nginx receives the visitor's request on port 80/443 and passes it to your app running privately on another port (for example 3000). Nginx handles HTTPS, compression and static files, so the app does not have to.

When the app uses live connections - chat, notifications, dashboards with real-time updates, Socket.IO or similar. Without the Upgrade and Connection headers those connections fail behind Nginx.

Nginx could not reach the app. Check that the app is running, that it listens on the host and port in the config (127.0.0.1:3000, for example) and that a firewall or SELinux policy is not blocking the connection.

Share this tool:

Need a website for your business? Only $599