Could not register user error
š¬Self-hostedāUnsolved
Testing with self-hosted v4.13.0 zitadel running on Debian systemd with UI v2 container running same version. Standard setup following docs. Tested with earlier v4 builds that had the same issue.
Stack includes service with webhook that responds to zitadel actions. This is specifically related to user.human.added.
Do not recall seeing this in v3 using the same webhook code.
Attempt to register a new user from V2 UI intermittently results in Could not register user error.
Logs show this sequence of events
[2026-04-08T15:21:52Z] INFO UserService/AddHumanUser
status: success (grpc=0, http=200)
instance_id: 3668...0843
org_id: 3668...6379
user_id: 3668...2811
host: auth.mtrose.me
[2026-04-08T15:21:52Z] INFO request served
service: zitadel.user.v2.UserService
method: POST /AddHumanUser
code: code_0
duration_ms: ~820
trace_id: 210e4e43...
[2026-04-08T15:21:52Z] WARN User lookup failed
error: NotFound (QUERY-Dfbg2)
cause: sql: no rows in result set
location: internal/query/user.go:882
user_id: 3668...2811
trace_id: 7413c031...
[2026-04-08T15:21:52Z] INFO SessionService/CreateSession
request received
host: auth.mtrose.me
project_id: 3668...1915
[2026-04-08T15:21:52Z] INFO request served
service: zitadel.session.v2.SessionService
method: POST /CreateSession
code: not_found
duration_ms: ~12
trace_id: 7413c031...
I see the webhook response on my side return with 200. My webhook does not modify zitadel state or call any zitadel APIs.
I believe the registration should succeed even in the case my webhook returned an error or timed out.
Restarting zitadel and trying a new registration will work for at least one attempt. Deleting the action and restarting will also resolve the issue.
Stack includes service with webhook that responds to zitadel actions. This is specifically related to user.human.added.
Do not recall seeing this in v3 using the same webhook code.
Attempt to register a new user from V2 UI intermittently results in Could not register user error.
Logs show this sequence of events
[2026-04-08T15:21:52Z] INFO UserService/AddHumanUser
status: success (grpc=0, http=200)
instance_id: 3668...0843
org_id: 3668...6379
user_id: 3668...2811
host: auth.mtrose.me
[2026-04-08T15:21:52Z] INFO request served
service: zitadel.user.v2.UserService
method: POST /AddHumanUser
code: code_0
duration_ms: ~820
trace_id: 210e4e43...
[2026-04-08T15:21:52Z] WARN User lookup failed
error: NotFound (QUERY-Dfbg2)
cause: sql: no rows in result set
location: internal/query/user.go:882
user_id: 3668...2811
trace_id: 7413c031...
[2026-04-08T15:21:52Z] INFO SessionService/CreateSession
request received
host: auth.mtrose.me
project_id: 3668...1915
[2026-04-08T15:21:52Z] INFO request served
service: zitadel.session.v2.SessionService
method: POST /CreateSession
code: not_found
duration_ms: ~12
trace_id: 7413c031...
I see the webhook response on my side return with 200. My webhook does not modify zitadel state or call any zitadel APIs.
I believe the registration should succeed even in the case my webhook returned an error or timed out.
Restarting zitadel and trying a new registration will work for at least one attempt. Deleting the action and restarting will also resolve the issue.
