Reverse Proxy Config Generator
Put a clean domain and HTTPS in front of a self-hosted app. Generate the config for Nginx, Caddy or Traefik, with optional WebSocket support and an HSTS header.
🔒 Runs entirely in your browser. Nothing you type is sent anywhere.
How to use it
- Enter the domain you want to use and the host and port your app listens on.
- Pick Nginx, Caddy or Traefik depending on what you run.
- Copy the config and drop it into place, then reload the proxy.
Which one
- Nginx: the most common choice. The config assumes certificates from Let’s Encrypt; the hint shows the one certbot command to get them.
- Caddy: the easiest for self-hosting. It gets and renews certificates automatically and handles WebSockets without extra lines.
- Traefik: labels you add to a container in your docker-compose file, so the proxy picks the app up automatically. Good when everything runs in Docker.
Why put a reverse proxy in front
A reverse proxy lets you reach several apps on one server through tidy names like jellyfin.example.com instead of :8096, terminates HTTPS in one place, and gives you a single spot to add security headers, rate limits or a tool like CrowdSec.
FAQ
Do I still need to open ports? Only 80 and 443 to the proxy. The apps behind it can stay bound to localhost, which is safer.
Is anything sent to a server? No. The config is built in your browser.