What steps will reproduce the problem? 1. In /etc/prosody/prosody.cfg.lua, set the following under the MUC component: restrict_room_creation = true component_admins_as_room_owners = true muc_tombstone_expiry = 86400*9999 (or any time you want, doesn't matter anyway) Globally: muc_restrict_rooms = { { ["*"] = "all" }; } muc_restrict_exceptions = { "community" } muc_restrict_allow_admins = true 2. Restart the service: `rcctl restart prosody` 3. Launch shell: `prosodyctl shell` 4. Delete old channel: `muc:room("abandoned@example.com"):destroy()` (execute twice to truly delete it) 5. Restart the service: `rcctl restart prosody` 6. Launch shell: `prosodyctl shell` 7. Check MUC list: `muc:list("chat.xmpp.076.ne.jp")` What is the expected output? Channel should stay gone. What do you see instead? Deleted channel is back again like if it was never deleted. Results vary, because sometimes it stays gone, and sometimes it's back again. And if it stays gone, it'll come back again within up to 2 weeks. And since Prosody is very buggy on OpenBSD (possibly due to a memory leak?), unfortunately we have to restart the service frequently. What version of the product are you using? On what operating system? Prosody 13.0.1 OpenBSD 7.7 amd64 Please provide any additional information below.