Hi,
Do we have a Zitadel module for NS8?
The app overview on the wiki.
HTH
2 Likes
Installation is running. But Citadel is not working. The app won’t start and I get a Bad Gateway error.
2 Likes
cc: @oneitonitram
Anything in the logs please?
2 Likes
It’s in beta, and the last commit was over a year ago, so I suppose that isn’t too much of a surprise.
@EXING_LEE, do you need Zitadel specifically? Because there are other SSO/IAM solutions available, including Authentik, Keycloak, and LemonLDAP::NG. I’ve been using the former for a while, and it’s working pretty well. And I’d personally wonder why we need a fourth one–what does it bring to the table that the others don’t?
4 Likes
Unfortunately, I can’t help you with that anymore. I just restored the backup. Zitadel is gone from the server.
2 Likes
Authentik
I installed it, but the webpage keeps crashing and I can’t set it up.
Keycloak
I don’t see it in the GeniusDynamics repository.
LemonLDAP::NG
I saw it after adding the KSAT repository. I’ll try it sometime.
Zitadel
I saw it in the GeniusDynamics repository, but I can’t install it.
It seems you’d need to install it at the shell, not through the software. But it also seems to be broken; it seems to continually restart with this in the logs:
2025-09-06T12:16:42-04:00 [1:zitadel1:podman] zitadel
2025-09-06T12:16:42-04:00 [1:zitadel1:systemd] Started Podman zitadel.service.
2025-09-06T12:16:42-04:00 [1:zitadel1:systemd] Starting Podman postgresql-app.service...
2025-09-06T12:16:42-04:00 [1:zitadel1:systemd] Started libcrun container.
2025-09-06T12:16:42-04:00 [1:zitadel1:zitadel1] ae8e778098123f52d67f01c638fd1e18f2868b32e6c19869aec669c2235e49e5
2025-09-06T12:16:42-04:00 [1:zitadel1:systemd] Started Podman postgresql-app.service.
2025-09-06T12:16:42-04:00 [1:zitadel1:systemd] Starting Podman zitadel-app.service...
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app]
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app] PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app]
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:42.803 UTC [1] LOG: starting PostgreSQL 16.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:42.803 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:42.803 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:42.806 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:42.833 UTC [25] LOG: database system was shut down at 2025-09-06 16:16:41 UTC
2025-09-06T12:16:42-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:42.842 UTC [1] LOG: database system is ready to accept connections
2025-09-06T12:16:43-04:00 [1:zitadel1:systemd] Started libcrun container.
2025-09-06T12:16:43-04:00 [1:zitadel1:zitadel1] 89cd742da4513b8d53ebf5c3b93a1aeb1844691d17e7e87e507bceb387d9df72
2025-09-06T12:16:43-04:00 [1:zitadel1:systemd] Started Podman zitadel-app.service.
2025-09-06T12:16:43-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:43Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:75"
2025-09-06T12:16:43-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:43Z" level=info msg="verify user" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_user.go:39" username=postgres
2025-09-06T12:16:43-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:43.971 UTC [31] ERROR: role "postgres" already exists
2025-09-06T12:16:43-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:43.971 UTC [31] STATEMENT: CREATE USER "postgres" WITH PASSWORD '167d8af6c92c98c3'
2025-09-06T12:16:43-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:43Z" level=info msg="verify database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:39" database=zitadel
2025-09-06T12:16:43-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:43.975 UTC [32] ERROR: database "zitadel" already exists
2025-09-06T12:16:43-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:43.975 UTC [32] STATEMENT: CREATE DATABASE "zitadel"
2025-09-06T12:16:43-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:43Z" level=info msg="verify grant" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:34" database=zitadel user=postgres
2025-09-06T12:16:43-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:43Z" level=info msg="verify zitadel" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:78" database=zitadel
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify system" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:39"
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify encryption keys" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:44"
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify projections" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:49"
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify eventstore" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:54"
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify events tables" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:59"
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify system sequence" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:64"
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify unique constraints" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:69"
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="setup started" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:99"
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:43" name=14_events_push
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:43" name=01_tables
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:43" name=02_assets
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:43" name=28_add_search_table
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:43" name=31_add_aggregate_index_to_fields
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:43" name=03_default_instance
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=info msg="starting migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:66" name=03_default_instance
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=error msg="migration failed" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:68" error="ID=INST-mruNY Message=Errors.Invalid.Argument" name=03_default_instance
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel-app] time="2025-09-06T16:16:44Z" level=fatal msg="migration failed" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:239" error="ID=INST-mruNY Message=Errors.Invalid.Argument" name=03_default_instance
2025-09-06T12:16:44-04:00 [1:zitadel1:systemd] zitadel-app.service: Main process exited, code=exited, status=1/FAILURE
2025-09-06T12:16:44-04:00 [1:zitadel1:zitadel1] 89cd742da4513b8d53ebf5c3b93a1aeb1844691d17e7e87e507bceb387d9df72
2025-09-06T12:16:44-04:00 [1:zitadel1:systemd] zitadel-app.service: Failed with result 'exit-code'.
2025-09-06T12:16:44-04:00 [1:zitadel1:systemd] zitadel-app.service: Scheduled restart job, restart counter is at 199.
2025-09-06T12:16:44-04:00 [1:zitadel1:systemd] Stopped Podman zitadel-app.service.
2025-09-06T12:16:44-04:00 [1:zitadel1:systemd] Stopping Podman postgresql-app.service...
2025-09-06T12:16:44-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:44.880 UTC [1] LOG: received fast shutdown request
2025-09-06T12:16:44-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:44.881 UTC [1] LOG: aborting any active transactions
2025-09-06T12:16:44-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:44.889 UTC [1] LOG: background worker "logical replication launcher" (PID 28) exited with exit code 1
2025-09-06T12:16:44-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:44.889 UTC [23] LOG: shutting down
2025-09-06T12:16:44-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:44.890 UTC [23] LOG: checkpoint starting: shutdown immediate
2025-09-06T12:16:44-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:44.911 UTC [23] LOG: checkpoint complete: wrote 16 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.002 s, total=0.022 s; sync files=11, longest=0.001 s, average=0.001 s; distance=74 kB, estimate=74 kB; lsn=0/27620C0, redo lsn=0/27620C0
2025-09-06T12:16:44-04:00 [1:zitadel1:postgresql-app] 2025-09-06 16:16:44.917 UTC [1] LOG: database system is shut down
2025-09-06T12:16:45-04:00 [1:zitadel1:zitadel1] ae8e778098123f52d67f01c638fd1e18f2868b32e6c19869aec669c2235e49e5
2025-09-06T12:16:45-04:00 [1:zitadel1:zitadel1] ae8e778098123f52d67f01c638fd1e18f2868b32e6c19869aec669c2235e49e5
2025-09-06T12:16:45-04:00 [1:zitadel1:systemd] Stopped Podman postgresql-app.service.
2025-09-06T12:16:45-04:00 [1:zitadel1:systemd] Stopping Podman zitadel.service...
2025-09-06T12:16:45-04:00 [1:zitadel1:conmon] conmon 9fceba899bf39e0ada7c <nwarn>: Failed to open cgroups file: /sys/fs/cgroup/user.slice/user-1004.slice/user@1004.service/user.slice/user-libpod_pod_015bd226a590e70c812a5abc5faef22dbc6ffd885e02895f2370381722263f16.slice/libpod-9fceba899bf39e0ada7ce631edc1c65883d47a2fd51afae06537f4159a5c61de.scope/container/memory.events
2025-09-06T12:16:45-04:00 [1:zitadel1:systemd] Removed slice cgroup user-libpod_pod_015bd226a590e70c812a5abc5faef22dbc6ffd885e02895f2370381722263f16.slice.
2025-09-06T12:16:45-04:00 [1:zitadel1:systemd] user-libpod_pod_015bd226a590e70c812a5abc5faef22dbc6ffd885e02895f2370381722263f16.slice: Consumed 1.256s CPU time.
2025-09-06T12:16:45-04:00 [1:zitadel1:podman] zitadel
2025-09-06T12:16:45-04:00 [1:zitadel1:podman] 015bd226a590e70c812a5abc5faef22dbc6ffd885e02895f2370381722263f16
2025-09-06T12:16:45-04:00 [1:zitadel1:systemd] Stopped Podman zitadel.service.
2025-09-06T12:16:45-04:00 [1:zitadel1:systemd] Starting Podman zitadel.service...
2025-09-06T12:16:45-04:00 [1:zitadel1:systemd] Created slice cgroup user-libpod_pod_e24fb574932cfe669dcc9daa5a18bba8fcb279e5f4dd07f845877ad5b19e5206.slice.
2025-09-06T12:16:45-04:00 [1:zitadel1:podman] e24fb574932cfe669dcc9daa5a18bba8fcb279e5f4dd07f845877ad5b19e5206
1 Like
It also requires CLI installation at this time, but also is in a restart loop (at least for me), logging this continually:
2025-09-06T12:24:33-04:00 [1:keycloak1:systemd] Starting Podman keycloak.service...
2025-09-06T12:24:33-04:00 [1:keycloak1:systemd] Created slice cgroup user-libpod_pod_adae0f645ae4b979308a179e50cbbbd625eb1fe76ee855fb9da318796f6823d7.slice.
2025-09-06T12:24:33-04:00 [1:keycloak1:podman] adae0f645ae4b979308a179e50cbbbd625eb1fe76ee855fb9da318796f6823d7
2025-09-06T12:24:33-04:00 [1:keycloak1:systemd] Started libcrun container.
2025-09-06T12:24:33-04:00 [1:keycloak1:podman] keycloak
2025-09-06T12:24:33-04:00 [1:keycloak1:systemd] Started Podman keycloak.service.
2025-09-06T12:24:33-04:00 [1:keycloak1:systemd] Starting Podman postgresql-app.service...
2025-09-06T12:24:34-04:00 [1:keycloak1:systemd] Started libcrun container.
2025-09-06T12:24:34-04:00 [1:keycloak1:keycloak1] cb8090f8cbf5df42ef0f785a8f1ff3b9c30161d5210e7e7638a3932bff5f7c65
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app]
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app] PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app]
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:34.238 UTC [1] LOG: starting PostgreSQL 15.5 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20231014) 13.2.1 20231014, 64-bit
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:34.238 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:34.238 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:34.240 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:34.260 UTC [19] LOG: database system was shut down at 2025-09-06 16:24:32 UTC
2025-09-06T12:24:34-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:34.266 UTC [1] LOG: database system is ready to accept connections
2025-09-06T12:24:34-04:00 [1:keycloak1:systemd] Started Podman postgresql-app.service.
2025-09-06T12:24:34-04:00 [1:keycloak1:systemd] Starting Podman keycloak-app.service...
2025-09-06T12:24:35-04:00 [1:keycloak1:systemd] Started libcrun container.
2025-09-06T12:24:35-04:00 [1:keycloak1:keycloak1] e4a4657fe3702dba375829f309b596848010230a601bebe26fcb8b7eb4ebb351
2025-09-06T12:24:35-04:00 [1:keycloak1:systemd] Started Podman keycloak-app.service.
2025-09-06T12:24:36-04:00 [1:keycloak1:keycloak-app] Option: '--http-port 7080 --https-port 7443' is not expected to contain whitespace, please remove any unnecessary quoting/escaping
2025-09-06T12:24:36-04:00 [1:keycloak1:keycloak-app] Possible solutions: --http-enabled, --http-host, --http-port, --https-port, --https-cipher-suites, --https-protocols, --https-certificate-file, --https-certificate-key-file, --https-key-store-file, --https-key-store-password, --https-key-store-type, --https-trust-store-file, --https-trust-store-password, --https-trust-store-type, --http-max-queued-requests, --http-pool-max-threads, --http-metrics-histograms-enabled, --http-metrics-slos, --http-relative-path, --https-client-auth, --http-management-port, --https-management-certificate-file, --https-management-certificate-key-file, --https-management-key-store-file, --https-management-key-store-password, --http-management-relative-path, --https-management-client-auth
2025-09-06T12:24:36-04:00 [1:keycloak1:keycloak-app] Try 'kc.sh start-dev --help' for more information on the available options.
2025-09-06T12:24:36-04:00 [1:keycloak1:systemd] libpod-e4a4657fe3702dba375829f309b596848010230a601bebe26fcb8b7eb4ebb351.scope: Consumed 2.088s CPU time.
2025-09-06T12:24:36-04:00 [1:keycloak1:conmon] conmon e4a4657fe3702dba3758 <nwarn>: Failed to open cgroups file: /sys/fs/cgroup/user.slice/user-1005.slice/user@1005.service/user.slice/user-libpod_pod_adae0f645ae4b979308a179e50cbbbd625eb1fe76ee855fb9da318796f6823d7.slice/libpod-e4a4657fe3702dba375829f309b596848010230a601bebe26fcb8b7eb4ebb351.scope/container/memory.events
2025-09-06T12:24:36-04:00 [1:keycloak1:systemd] keycloak-app.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2025-09-06T12:24:36-04:00 [1:keycloak1:keycloak1] e4a4657fe3702dba375829f309b596848010230a601bebe26fcb8b7eb4ebb351
2025-09-06T12:24:36-04:00 [1:keycloak1:systemd] keycloak-app.service: Failed with result 'exit-code'.
2025-09-06T12:24:36-04:00 [1:keycloak1:systemd] keycloak-app.service: Scheduled restart job, restart counter is at 40.
2025-09-06T12:24:36-04:00 [1:keycloak1:systemd] Stopped Podman keycloak-app.service.
2025-09-06T12:24:36-04:00 [1:keycloak1:systemd] Stopping Podman postgresql-app.service...
2025-09-06T12:24:36-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:36.881 UTC [1] LOG: received fast shutdown request
2025-09-06T12:24:36-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:36.882 UTC [1] LOG: aborting any active transactions
2025-09-06T12:24:36-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:36.885 UTC [1] LOG: background worker "logical replication launcher" (PID 22) exited with exit code 1
2025-09-06T12:24:36-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:36.886 UTC [17] LOG: shutting down
2025-09-06T12:24:36-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:36.886 UTC [17] LOG: checkpoint starting: shutdown immediate
2025-09-06T12:24:36-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:36.903 UTC [17] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.017 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2025-09-06T12:24:36-04:00 [1:keycloak1:postgresql-app] 2025-09-06 16:24:36.907 UTC [1] LOG: database system is shut down
2025-09-06T12:24:37-04:00 [1:keycloak1:keycloak1] cb8090f8cbf5df42ef0f785a8f1ff3b9c30161d5210e7e7638a3932bff5f7c65
2025-09-06T12:24:37-04:00 [1:keycloak1:keycloak1] cb8090f8cbf5df42ef0f785a8f1ff3b9c30161d5210e7e7638a3932bff5f7c65
2025-09-06T12:24:37-04:00 [1:keycloak1:systemd] Stopped Podman postgresql-app.service.
2025-09-06T12:24:37-04:00 [1:keycloak1:systemd] Stopping Podman keycloak.service...
2025-09-06T12:24:37-04:00 [1:keycloak1:systemd] Removed slice cgroup user-libpod_pod_adae0f645ae4b979308a179e50cbbbd625eb1fe76ee855fb9da318796f6823d7.slice.
2025-09-06T12:24:37-04:00 [1:keycloak1:systemd] user-libpod_pod_adae0f645ae4b979308a179e50cbbbd625eb1fe76ee855fb9da318796f6823d7.slice: Consumed 2.255s CPU time.
2025-09-06T12:24:37-04:00 [1:keycloak1:podman] keycloak
2025-09-06T12:24:37-04:00 [1:keycloak1:podman] adae0f645ae4b979308a179e50cbbbd625eb1fe76ee855fb9da318796f6823d7
2025-09-06T12:24:37-04:00 [1:keycloak1:systemd] Stopped Podman keycloak.service.
1 Like
Hello
There are some breaking changes that were introduce in v3 Am working on them this week
Within this week there will be an official release
2 Likes
This is a known issue that I think is fixed in development, but not sure when it will be released. A workaround, as root, is to run sysctl fs.protected_regular=0.
2 Likes
I have already fixed the permissions issue in dev branch
Will release it since nothing breaks on update
2 Likes
current vrsion of Zitadel is Releases · zitadel/zitadel v 4.1.2
since we did not have a rleased version, Our thinking was to skip all the other versions, since version 2 which is what we were bulding for, and release the version 4, And Support it throughout.
This is possible to have ready Within the Weekend, As the Updates required to implement are not that massive.
So the first version would start at v 4, not 2 and not 3
2 Likes
Can anybody confirm the available Authentik version 2.0.1 in SS is working correctly please?
A bit confused for this thread discusses Zitadel, Keycloack and Authentic.
Authenik 2.0.1 is based on the tests that you had done before, and confirmed, nothing else has been added or removed after your tests. unless there is a concern youve identified.
I’m able to log in with it, at least.
That’s on me, sorry–wanting to suggest alternatives cluttered the thread. Let’s take further discussion of Authentik to its thread:
1 Like
should be releasing Zitadel beta version today, you’ll kindly help test the same for any regressions..
1 Like
1 Like
I am sorry, appreciating the message, but this is a bit too easy.
- What is the change log
- What needs to be tested
- What is the goal
- What are your concerns
- How do you expect tests should be done
- What effect will this test version have on prod versions ( not all have spare test servers)
- What is the caution of warnings
3 Likes
Agree with HF that a lot more information from you would be appropriate here. But having installed that version on a clean server, I’m getting a Bad Gateway when I try to browse there, and I’m seeing this in the logs:
2025-09-08T18:19:14-04:00 [1:zitadel1:systemd] Starting Podman zitadel.service...
2025-09-08T18:19:14-04:00 [1:zitadel1:systemd] Created slice cgroup user-libpod_pod_31e4332567b18c7e6cc49bd1928d8befe8b7a984c2da7e3007f85e5870fa626e.slice.
2025-09-08T18:19:14-04:00 [1:zitadel1:podman] 31e4332567b18c7e6cc49bd1928d8befe8b7a984c2da7e3007f85e5870fa626e
2025-09-08T18:19:14-04:00 [1:zitadel1:systemd] Started libcrun container.
2025-09-08T18:19:14-04:00 [1:zitadel1:podman] zitadel
2025-09-08T18:19:14-04:00 [1:zitadel1:systemd] Started Podman zitadel.service.
2025-09-08T18:19:14-04:00 [1:zitadel1:systemd] Starting Podman postgresql-app.service...
2025-09-08T18:19:14-04:00 [1:zitadel1:systemd] Started libcrun container.
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app]
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app] PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app]
2025-09-08T18:19:14-04:00 [1:zitadel1:zitadel1] 2f6a53279b17405b6118c68790ed9d586fdcec1dc965221d11fc1eecd273ff65
2025-09-08T18:19:14-04:00 [1:zitadel1:systemd] Started Podman postgresql-app.service.
2025-09-08T18:19:14-04:00 [1:zitadel1:systemd] Starting Podman zitadel-app.service...
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:14.957 UTC [1] LOG: starting PostgreSQL 17.6 on x86_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:14.957 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:14.958 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:14.960 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:14.981 UTC [24] LOG: database system was shut down at 2025-09-08 22:19:13 UTC
2025-09-08T18:19:14-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:14.987 UTC [1] LOG: database system is ready to accept connections
2025-09-08T18:19:15-04:00 [1:zitadel1:systemd] Started libcrun container.
2025-09-08T18:19:15-04:00 [1:zitadel1:zitadel1] 8b6ae417cf557df35da8b03d578dd4dd5022ea5f272c7c822fa01081cd3b5970
2025-09-08T18:19:15-04:00 [1:zitadel1:systemd] Started Podman zitadel-app.service.
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify user" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_user.go:40" username=postgres
2025-09-08T18:19:16-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:16.290 UTC [28] ERROR: role "postgres" already exists
2025-09-08T18:19:16-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:16.290 UTC [28] STATEMENT: -- replace postgres with the name of the user
2025-09-08T18:19:16-04:00 [1:zitadel1:postgresql-app] CREATE USER "postgres" WITH PASSWORD '1984c006f059d3f2'
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:40" database=zitadel
2025-09-08T18:19:16-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:16.291 UTC [28] ERROR: database "zitadel" already exists
2025-09-08T18:19:16-04:00 [1:zitadel1:postgresql-app] 2025-09-08 22:19:16.291 UTC [28] STATEMENT: -- replace zitadel with the name of the database
2025-09-08T18:19:16-04:00 [1:zitadel1:postgresql-app] CREATE DATABASE "zitadel"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify grant" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:35" database=zitadel user=postgres
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify zitadel" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:80" database=zitadel
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify system" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:46"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify encryption keys" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:51"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify projections" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:56"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify eventstore" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:61"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify events tables" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:66"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify unique constraints" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:71"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="setup started" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:108"
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:46" name=14_events_push
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:46" name=40_init_push_func_v4
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:46" name=01_tables
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:46" name=02_assets
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:46" name=28_add_search_table
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:46" name=31_add_aggregate_index_to_fields
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:46" name=46_init_permission_functions
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:46" name=03_default_instance
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=info msg="starting migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:69" name=03_default_instance
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=error msg="migration failed" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:71" error="ID=INST-mruNY Message=Errors.Invalid.Argument" name=03_default_instance
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=error msg="migration failed" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:364" error="ID=INST-mruNY Message=Errors.Invalid.Argument" name=03_default_instance
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel-app] time="2025-09-08T22:19:16Z" level=fatal msg="setup failed, skipping cleanup" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:124" error="migration failed: ID=INST-mruNY Message=Errors.Invalid.Argument"
2025-09-08T18:19:16-04:00 [1:zitadel1:systemd] zitadel-app.service: Main process exited, code=exited, status=1/FAILURE
2025-09-08T18:19:16-04:00 [1:zitadel1:zitadel1] 8b6ae417cf557df35da8b03d578dd4dd5022ea5f272c7c822fa01081cd3b5970
2025-09-08T18:19:16-04:00 [1:zitadel1:systemd] zitadel-app.service: Failed with result 'exit-code'.
1 Like