Skip to main content

Upgrade authentik

Upgrading to the latest version of authentik, whether a new major release or a patch, involves running a few commands to pull down the latest images and then restarting the servers and databases.

Important considerations​

danger

authentik does not support downgrading. Make sure to back up your database in case you need to revert an upgrade.

  • Be sure to carefully read the Release Notes for the specific version to which you plan to upgrade. The release might have special requirements or actions or contain breaking changes.

  • Make a backup of your PostgreSQL database before upgrading. You can dump your existing database to get a backup file. For more information about dumping and backing up your database, refer to Upgrade PostgreSQL on Docker Compose or Upgrade PostgreSQL on Kubernetes.

  • You need to upgrade in sequence of the major releases; do not skip directly from an older major version to the most recent version. For example, if you are currently running 2023.10.3, you will need to first upgrade to 2024.2.x, then 2024.4.x, and then 2024.6.x, in sequence.

  • The version of the authentik instance and any outposts must be the same. We recommended that you always upgrade any outposts at the same time you upgrade your authentik instance.

Upgrade authentik​

In your terminal, navigate to your installation directory and follow these steps:

1. Retrieve latest docker-compose.yml file​

Download the docker-compose.yml file using either wget -O docker-compose.yml https://goauthentik.io/docker-compose.yml or curl -O https://goauthentik.io/docker-compose.yml or a similar process.

2. Run upgrade commands

docker compose pull
docker compose up -d

Verify your upgrade​

You can view the current version of your authentik instance by logging in to the Admin interface, and then navigating to Dashboards -> Overview.

Troubleshooting your upgrade​

If you run the upgrade commands but your version on the Dashboard doesn’t change, follow this steps:

  1. Look at the server logs and search for an entry of migration inconsistency.
  2. If you see this entry, revert to your database backup.
  3. Now, upgrade to each subsequent higher version. That is, upgrade in sequence, do not skip directly to the most recent version.