August 11, 2025Aug 11 I'm Authentik 2025.2.4 and preparing the supported upgrade path to the latest stable. First step was to move to Postgresql 16. I just upgraded from Postgresql 12.5 to 16 successfully. 1. Backup the Postgresql 12.5 databasedocker exec -it <Postgres12.5_container_name> pg_dump -U <user> -d authentik --no-owner --no-privileges > /mnt/cache/appdata/backups/authentik_db_fresh_backup.dump2. Prepare the New PostgreSQL 16 DatabaseEnsure your new PostgreSQL 16 database is completely empty before restoring the new backup.docker exec -it <Postgres16_container_name> psql -U <user> -d authentik -c "DROP SCHEMA public CASCADE; CREATE SCHEMA public; GRANT ALL ON SCHEMA public TO authentik;"Bashdocker stop <authentik_core_container_name> <authentik_worker_container_name> docker exec -it <Postgres12.5_container_name> psql -U user -d authentik -c "DROP SCHEMA public CASCADE; CREATE SCHEMA public; GRANT ALL ON SCHEMA public TO authentik;"3. Restore the Backup to PostgreSQL 16docker exec -i <Postgresql16_container_name> psql -U user -d authentik < /mnt/cache/appdata/authentik/backups/<authentik_db_backup_name>.dump4. Edit the Authentik server Postgresql to new IP 5. Run the Authentik Database Migrationsdocker exec -it authentik ak migrateThis command will update your restored database schema to be compatible with the new Authentik containers.6. Start the Authentik ContainersYou can now start both containers. The core and worker containers will run on a fully migrated and up-to-date database.
December 12, 2025Dec 12 I wanted to give you a big thanks for this guide! It worked like a charm. Now to work up the courage to update the authentik container itself
April 24Apr 24 Used this guide to upgrade from postgres 15 to 18 on authentik 2026.2.2. Worked like a charm, thank you so much!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.