UIAA service exception during user registration (v0.5.5) #1409

New issue

Open

opened 2026-02-18 04:25:06 +00:00 by Beanie · 2 comments

Beanie commented

2026-02-18 04:25:06 +00:00

Possibly caused by beanie error, but exception being raised nonetheless.

Server logs:

Feb 18 04:19:40 fit.theargo.space continuwuity[41338]:   2026-02-18T04:19:40.854204Z ERROR conduwuit_core::error::response: Server error, error: uiaa, error_debug: uiaa, kind: Unknown, status: 500 Internal Server Error
Feb 18 04:19:40 fit.theargo.space continuwuity[41338]:     at src/core/error/response.rs:19 on conduwuit:worker ThreadId(3)
Feb 18 04:19:40 fit.theargo.space continuwuity[41338]:

During a POST request to https://matrix.theargo.space/_matrix/client/v3/register in Element Web.

Request:

{"username":"simon","password":"says","initial_device_display_name":"chat.theargo.social: Firefox on Linux","auth":{"session":"removed"}}

Response (401):

{"flows":[{"stages":["m.login.registration_token"]}],"params":null,"session":"removed"}

Token hasn't even been entered yet, but entering the correct token works fine for the 2nd user onwards (new instance).

Possibly caused by beanie error, but exception being raised nonetheless. Server logs: ``` Feb 18 04:19:40 fit.theargo.space continuwuity[41338]: 2026-02-18T04:19:40.854204Z ERROR conduwuit_core::error::response: Server error, error: uiaa, error_debug: uiaa, kind: Unknown, status: 500 Internal Server Error Feb 18 04:19:40 fit.theargo.space continuwuity[41338]: at src/core/error/response.rs:19 on conduwuit:worker ThreadId(3) Feb 18 04:19:40 fit.theargo.space continuwuity[41338]: ``` During a POST request to `https://matrix.theargo.space/_matrix/client/v3/register` in Element Web. Request: ```json {"username":"simon","password":"says","initial_device_display_name":"chat.theargo.social: Firefox on Linux","auth":{"session":"removed"}} ``` Response (401): ```json {"flows":[{"stages":["m.login.registration_token"]}],"params":null,"session":"removed"} ``` Token hasn't even been entered yet, but entering the correct token works fine for the 2nd user onwards (new instance).