Important: When using these guides, it’s important to recognize that we cannot provide a guide for every possible
method of deploying a proxy. These guides show a suggested setup only, and you need to understand the proxy
configuration and customize it to your needs. To-that-end, we include links to the official proxy documentation
throughout this documentation and in the See Also section.
It’s strongly recommended that users setting up Authelia for the first time take a look at our
Get started guide. This takes you through various steps which are essential to
bootstrapping Authelia.
Important: You should read the Forwarded Headers section and this section as part of any proxy configuration.
Especially if you have never read it before.
Important: The included example is NOT meant for production use. It’s used expressly as an example to showcase
how you can configure multiple IP ranges. You should customize this example to fit your specific architecture and needs.
You should only include the specific IP address ranges of the trusted proxies within your architecture and should not
trust entire subnets unless that subnet only has trusted proxies and no other services.
This guide makes a few assumptions. These assumptions may require adaptation in more advanced and complex scenarios. We
can not reasonably have examples for every advanced configuration option that exists. Some of these values can
automatically be replaced with documentation variables.
Documentation Variable Configuration
The following are the assumptions we make:
Deployment Scenario:
Single Host
Authelia is deployed as a Container with the container name authelia on port 9091
Proxy is deployed as a Container on a network shared with Authelia
The above assumption means that Authelia should be accessible to the proxy on http://authelia:9091 and as such:
You will have to adapt all instances of the above URL to be https:// if Authelia configuration has a TLS key and
certificate defined
You will have to adapt all instances of authelia in the URL if:
you’re using a different container name
you deployed the proxy to a different location
You will have to adapt all instances of 9091 in the URL if:
you have adjusted the default port in the configuration
You will have to adapt the entire URL if:
Authelia is on a different host to the proxy
All services are part of the example.com domain:
This domain and the subdomains will have to be adapted in all examples to match your specific domains unless you’re
just testing or you want to use that specific domain
Envoy utilizes the ExtAuthz Authz implementation. The
associated Metadata should be considered required.
The examples below assume you are using the default
Authz Endpoints Configuration or one similar to the
following minimal configuration:
The examples below also assume you are using the modern
Session Configuration which includes the domain, authelia_url, and
default_redirection_url as a subkey of the session.cookies key as a list item. Below is an example of the modern
configuration as well as the legacy configuration for context.