Reverse Proxy

Configure reverse proxies to route traffic, terminate TLS, enforce rate limits, and serve as the gateway between clients and backend services.

When to Use

• Routing traffic from a public domain to one or more backend services.
• Terminating TLS at the edge and forwarding plain HTTP to backends.
• Adding rate limiting, CORS, security headers, and access control.
• Consolidating multiple services under a single domain with path-based routing.
• Handling WebSocket upgrades, gRPC proxying, or HTTP/2 passthrough.

Prerequisites

• Backend service(s) running on known host:port.
• TLS certificate (Let's Encrypt, ACM, or self-signed for development).
• nginx 1.25+ or Traefik 3.x installed.
• DNS record pointing the domain to the proxy server.