Unable to leave room

[viktorstrate]

I have a room that I can not delete, when I try to I get the following error log and the room persists in my client.

homeserver-1  | 2025-10-29T07:57:06.733926Z  WARN tuwunel_service::membership::leave: Failed to leave room <ROOM_ID> remotely: Remote server <SERVER_ADDR> responded with: [403 / M_FORBIDDEN] <MY_USER> not in room <ROOM_ID>. user_id=<MY_USER>
homeserver-1  | 2025-10-29T07:57:08.087331Z  WARN tuwunel_service::membership::leave: Failed to leave room <ROOM_ID> remotely: Remote server <SERVER_ADDR> responded with: [403 / M_FORBIDDEN] No create event in auth events user_id=<MY_USER>

One way to remove it is to join it and then leave it, but I have a room that gives me this error when I try to join it, so there is no way for me to remove it.

MatrixError: [403] Answer from matrix.org: [403 / M_FORBIDDEN] You do not belong to any of the required rooms/spaces to join this room.

[jevolk]

Thank you for reporting. Is a restricted room type involved in this issue?

[viktorstrate]

I'm not that experienced with the inner workings of Matrix so I don't know for sure. But for one of the rooms, I think I got an error that said I was not allowed to join the room, maybe because my account was not on matrix.org.

But it did also happen with a normal room, since I was able to remove it by clicking "Join Room" in the client and then after it had joined properly, I was able to leave it.

From the first error message Failed to leave room ... <MY_USER> not in room ..., it looks to me like my server and the other one disagrees on the state, my server thinks that I've joined the room, but the remote one thinks not. I suppose then that it is safe just to delete the room locally, since the remote server already thinks that I'm not joined?

[balgerion]

i have same problem i have many

i dont know why but its not possible to leave them

Error leaving room
MatrixError: [403] M_FORBIDDEN: Auth check failed: cannot leave if not joined, invited or knocked (https://matrix.*********/_matrix/client/v3/rooms/!1pZ8qM0ZZCbP29XlxP%3Amatrix.**********/leave)

it would be awesome to have some sort of cmdlet to force delete them from database

[jevolk]

@viktorstrate If it's not too late I'd prefer if you could preserve the room to know if the bug is eventually properly fixed.

@balgerion I'll need more information, including whether your server is configured to automatically forget rooms or if you tried the forget button. You can try upgrading the server to see if it no longer occurs after the latest changes on the main branch. You may have to clear-cache and reload at this point for those rooms in any case.

[viktorstrate]

Sure, I'll keep the room 👍

[jevolk]

I think I misunderstood this issue initially and it may not have been necessary to keep either of you waiting. Was the first action an attempt to delete the room? The leave operation on room deletion can flake sometimes. We have more work to do on this feature. In these cases the options are to --force delete the room, but unfortunately a client clear-cache is usually necessary when things get out of sync like this.

If this issue occurred during a normal in-client standard leave action then this will have to be looked into further. Note that the main branch has some updates for non-sliding-sync room leaves, but it may be too late to avoid a client clear-cache. Also note there is a room "forget" functionality which a client should offer; less destructive than a server-side deletion above. This should be attempted first.

[viktorstrate]

Yeah that might be it, clearing the cache did fix the problem. Thank you, for the quick responses and support on the issue.