User not found after Postgres migration
Hi there, I was initially unable to migrate to Zitadel v3 due to no SSL on my database. I now tried to apply this workaround here: https://github.com/zitadel/zitadel/issues/9120#issuecomment-2888582544 – using a v3 Zitadel to migrate to Postgres. This first returned an error because some assets relation did not exist. However i remembered a --replace flag from different issues being mentioned, which mostly ran without errors (it had a problem with smtp settings and returned some weird
message \"PasswordChange.Footer\" not found in language \"en\" errors but otherwise ran through.
However now my user is not found and \dt gives no relations, but the DB is over 200M in size.
In my log i see some warnings like: level=warning msg="asset in login could not be served" .. error="download failed: ID=DATAB-pCP8P Message=Errors.Assets.Object.NotFound Parent=(sql: no rows in result set)GitHub
[Bug]: zitadel mirror command does not work correctly towards PSQL ...
Preflight Checklist I could not find a solution in the documentation, the existing issues or discussions I have joined the ZITADEL chat Environment Self-hosted Version 2.64.1 Database PostgreSQL Da...
1 Reply
It would even allow me to register my previous user 😦 however it fails to send the email:
level=error msg="could not create email channel" caller="/home/runner/work/zitadel/zitadel/internal/notification/types/user_email.go:29" error="ID=QUERY-fwofw Message=Errors.SMTPConfig.NotFound Parent=(sql: no rows in result set)"
so if i dont use replace, i get FATA[0000] unable to copy assets to destination caller="/home/runner/work/zitadel/zitadel/cmd/mirror/system.go:90" error="ERROR: duplicate key value violates unique constraint \"assets_pkey\" (SQLSTATE 23505)"
i now did setup and init for mirror which i was missing. the mirror command rand jsut as above with the same errors but it ran through, still. zitadel now seems to recognize my user, but upon login enters a loop of death und the browser.
msg="request error" oidc_error.parent="ID=QUERY-Sghn4 Message=Errors.Internal Parent=(cannot decode, empty data)" oidc_error.description="ID=QUERY-Sghn4 Message=Errors.Internal Parent=(cannot decode, empty data)" oidc_error.type=server_error status_code=500
...this seems console specific. it is still possible to login into clients