Skip to main content
Reverse proxy that puts an OAuth2 or OIDC login in front of any upstream. The install form carries oauth2-proxy.cfg as an editable file with a generated cookie secret, so it starts without extra flags. This page describes the Levelrail template for OAuth2 Proxy (Security). It deploys the services below as one Docker Compose app on your own server. Project site: https://oauth2-proxy.github.io/oauth2-proxy/. Recommended memory: about 64 MiB.

Services, ports and volumes

Environment variables

This template sets no environment variables. Passwords and keys marked as generated are created for you when the app is deployed and stored as secrets. Values are not shown here.

Security and requirements

Level: Standard. What this template needs:
  • No health check, so a deploy is judged by the process starting (oauth2-proxy).
What Levelrail adds around it:
  • Automatic HTTPS and an ingress shield in front of every domain.
  • One-step rollback to the previous revision.
  • Exposure report shows what is reachable from outside.
  • Host firewall rules managed for published ports.

Deploy OAuth2 Proxy with Levelrail

In the dashboard, open Apps, choose New app, then Browse templates, and select OAuth2 Proxy. Review the Compose body and deploy. With the CLI:
See the service template catalog for how templates work, and Getting started if you have not installed Levelrail yet.

More Security templates

All templates are listed in the self-host gallery.
Last modified on November 12, 2026