MUC Chatroom "403 Forbidden" after configuring a new room

Corey Wilson
Added over 5 years ago

I posted this in "Newbie Questions" but never received an answer to the question, Hoping someone can help:

I've come across a few more problems as I'm working with Tigase, and was wondering if someone might help :)

I noticed when creating a MUC room I am always receiving a "403 forbidden" when trying to save a chatroom configuration.

Additionally, when I try to obtain the room configuration with: user@host I get no response,


<body rid="102798866104" xmlns="" sid="435d5c5b-f2fc-4eed-b2d6-1ee5762c7756">
  <iq from="user@host" to="room@muc" type="get" xmlns="jabber:client" id="6599:sendIQ">
    <query xmlns=""></query>
//No Response

but with user@host/resource I do get the form back from the server.


<body rid="102798866104" xmlns="" sid="435d5c5b-f2fc-4eed-b2d6-1ee5762c7756">
  <iq from="user@host/resource" to="room@muc" type="get" xmlns="jabber:client" id="6599:sendIQ">
    <query xmlns=""></query>
//Receive Response 

I have attached the log, I don't have the log handy but can repost it later if required

I noticed there are quite a few:

FINEST: Still no comp name matches:

FINEST: None compId matches:

although I am not sure what it means.

Also, is there any resources detailing what different log errors mean?

Replies (3)


Added by Bartosz Małkowski TigaseTeam over 5 years ago

I have no idea what is wrong.

What version you use?

Can you show me whole communication between your client and MUC? What you send to create new room? WHat answer MUC sent?

Added by Corey Wilson over 5 years ago

I started to write a long post step by step of what I was doing, and then realized I wasn't sending a presence to create the room before I configured it - I think it I have it figured out now and is working as expected.

One thing I did notice is muc rooms don't seem to be destroyed when no one is in the room, even tho the rooms are not persistent. They have been active for almost a week and since they weren't set up properly I can't remove them.


Added by Artur Hefczyc TigaseTeam over 5 years ago

The reason for not destroying these rooms is probably just because they were created incorrectly and the system is still waiting for a correct configuration for the room.

Please let us know if other non-persistent rooms which are correctly configured and unlocked are not destroyed by the system automatically.