Self-host Authelia with Levelrail

Verified

Single sign-on and two-factor portal. The admin user is created at first boot from a generated password (visible in the service environment settings, never on a process command line); more users go in /data/users.yml. Sessions are scoped to this portal's own host, so widen the cookie domain in /config/configuration.yml before protecting other apps. One-time codes are written to /data/notification.txt.

  • AuthorautheliaVerified by Levelrail
  • LicenceApache-2.0
  • Memory256 MiB
  • Archarm64
  • Services1

How to self-host Authelia

  1. Pull the images

    One image is pulled on your server.

    Show images
    • authelia/authelia:4.39.28
  2. Create the app

    One service starts in a single Compose app, with 2 named volume mounts for your data, on port 9091.

  3. Fill in the secrets

    4 secrets are generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Authelia requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 tested
Ports
9091
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Verified. Verified on arm64 with image tag 4.39.28. Our CI ran this exact image version and it answered on its health path. Evidence

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Authelia. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Authelia docs page.

Deploy Authelia your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Authelia from the CLI

levelrail-cli templates deploy authelia --name my-authelia

Deploy Authelia with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/authelia/deploy

Authelia configuration

Authelia services

ServiceImagePortsVolumes
authelia authelia/authelia:4.39.28 9091 data -> /dataconfig -> /config

Authelia environment variables

VariableServiceValue
ADMIN_PASSWORD authelia Generated at deploy
AUTHELIA_IDENTITY_VALIDATION_RESET_PASSWORD_JWT_SECRET authelia Generated at deploy
AUTHELIA_SESSION_SECRET authelia Generated at deploy
AUTHELIA_STORAGE_ENCRYPTION_KEY authelia Generated at deploy
PORTAL_URL authelia Preset by the template
X_AUTHELIA_CONFIG_FILTERS authelia Preset by the template

Ports and volumes

Ports
9091
Volumes
2 named mounts: data -> /data, config -> /config

Authelia FAQ

How much memory does Authelia need?

The catalog lists about 256 MiB of memory for Authelia.

Does Authelia run on arm64?

For Authelia, arm64 is tested; amd64 is image published.

What licence is Authelia under?

Authelia is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does Authelia need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does Authelia use?

Authelia listens on port 9091 inside the stack.

Where does Authelia keep its data?

In named volumes: data mounted at /data and config mounted at /config.

Can I deploy Authelia on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id authelia for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image authelia/authelia:4.39.28 is what you deploy there.

levelrail-cli templates deploy authelia --name my-authelia