Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sometimes deactivating users won't kick them out of any room #447

Closed
Kimiblock opened this issue Jun 10, 2024 · 3 comments · Fixed by #455
Closed

Sometimes deactivating users won't kick them out of any room #447

Kimiblock opened this issue Jun 10, 2024 · 3 comments · Fixed by #455

Comments

@Kimiblock
Copy link
Contributor

I wanted to use another server_name, so @kimiblockmoe:moetrix.kimiblock.top was deactivated. But the account itself is not kicked from any room.

There isn't any log (level is warn) when deactivating (16:08 in my TZ).

Logs prior to deactivation:

Jun 10 11:41:20 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T03:41:20.536354Z  WARN conduit_api::ruma_wrapper::request: try_from_http_request failed: Deserialization(Json(Error("invalid type: null, expected a sequence", line: 1, column: 58)))
Jun 10 13:34:24 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T05:34:24.650520Z  WARN conduit_service::sending::sender: error for $R4PV2nxDOpXiSokpAbQK1aquNfw9sZjuqIumchT_c6I from remote: Err("M_INVALID_PARAM: Event has been soft failed")
Jun 10 13:34:24 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T05:34:24.694017Z  WARN conduit_service::sending::sender: error for $R4PV2nxDOpXiSokpAbQK1aquNfw9sZjuqIumchT_c6I from remote: Err("M_INVALID_PARAM: Event has been soft failed")
Jun 10 13:34:24 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T05:34:24.734989Z  WARN conduit_service::sending::sender: error for $R4PV2nxDOpXiSokpAbQK1aquNfw9sZjuqIumchT_c6I from remote: Err("M_INVALID_PARAM: Event has been soft failed")
Jun 10 13:34:24 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T05:34:24.812382Z  WARN conduit_service::sending::sender: error for $R4PV2nxDOpXiSokpAbQK1aquNfw9sZjuqIumchT_c6I from remote: Err("M_INVALID_PARAM: Event has been soft failed")
Jun 10 13:34:24 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T05:34:24.828210Z  WARN conduit_service::sending::sender: error for $R4PV2nxDOpXiSokpAbQK1aquNfw9sZjuqIumchT_c6I from remote: Err("M_INVALID_PARAM: Event has been soft failed")
Jun 10 13:34:25 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T05:34:25.070984Z  WARN conduit_service::sending::sender: error for $R4PV2nxDOpXiSokpAbQK1aquNfw9sZjuqIumchT_c6I from remote: Err("M_INVALID_PARAM: Event has been soft failed")
Jun 10 13:34:25 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T05:34:25.117314Z  WARN conduit_service::sending::sender: error for $R4PV2nxDOpXiSokpAbQK1aquNfw9sZjuqIumchT_c6I from remote: Err("M_INVALID_PARAM: Event has been soft failed")
Jun 10 14:02:52 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T06:02:52.327887Z  WARN conduit_api::ruma_wrapper::request: try_from_http_request failed: Deserialization(Json(Error("invalid type: null, expected a sequence", line: 1, column: 58)))
Jun 10 14:02:53 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T06:02:53.589502Z  WARN conduit_api::ruma_wrapper::request: try_from_http_request failed: Deserialization(Json(Error("invalid type: null, expected a sequence", line: 1, column: 58)))
Jun 10 14:02:53 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T06:02:53.589504Z  WARN conduit_api::ruma_wrapper::request: try_from_http_request failed: Deserialization(Json(Error("invalid type: null, expected a sequence", line: 1, column: 58)))
Jun 10 14:46:07 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T06:46:07.044203Z  WARN conduit_api::client_server::room: Event not found, event ID: "$dizMFJVst-deF-gKiRkEF_HykFKhFvbcAAfjy7bVNys"
Jun 10 14:46:20 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T06:46:20.988942Z  WARN conduit_service::sending::sender: error for $R4PV2nxDOpXiSokpAbQK1aquNfw9sZjuqIumchT_c6I from remote: Err("M_INVALID_PARAM: Event has been soft failed")
Jun 10 15:09:15 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T07:09:15.140878Z  WARN conduit_service::rooms::auth_chain: Could not find pdu mentioned in auth events event_id="$LVY-QO25-hgS_38-pKNB6kgqMSKTYeFeY5jGpq0UDpQ"
Jun 10 15:09:15 serverOS-kimiblock.top conduwuit[1374130]: 2024-06-10T07:09:15.540065Z  WARN conduit_service::rooms::auth_chain: Could not find pdu mentioned in auth events event_id="$wV9yzTHxw2tcePo6bTDLoR89X0uWN5unUg3I6EG3cfs"
@girlbossceo
Copy link
Owner

Admin command for user deactivation was changed to default to always leave rooms to prevent this from happening again. A feature request for resetting your power level in each room to the room default power level was created #446

@Kimiblock
Copy link
Contributor Author

Kimiblock commented Jun 11, 2024 via email

@girlbossceo
Copy link
Owner

No, this isn't possible to determine. A possible workaround would be creating an account with the same username as the previous account / resetting the password for that account to login to it again and leave the rooms; however since you said you re-used your server name, the event auth failures may be "expected" as servers are enforcing signatures on events and notice your server signing key is mismatched with what they have.

Since the ones you posted are soft failures, they aren't being out right rejected, but it will make them delayed to appear for other servers in the room.

If re-using a server name, servers will fully start accepting everything from you with no failures or issues after about 2-5 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants