Multi-user chat configuration 5.2 - Getting Failed to retrieve MultiUserChat service names

Jonathan Hunter
Added over 4 years ago

Hi Guys,

I have just upgraded the 5.2, and in my I have defined the following;

--comp-name-1 = muc

--comp-class-1= tigase.muc.MUCComponent

However when I try and start a multi-user chat I get a jabber error

Failed to retrieve MultiUserChat service names.

Do I need to define this anywhere?

Many thanks


Replies (5)

Added by Jonathan Hunter over 4 years ago

Hi Guys,

I have added another virtual host so that cleared initial problem.

I now am getting Failed to join room chatroom

And feature not implemented.

Can you please let me know what should be configured for MUC ?



Added by Wojciech Kapcia TigaseTeam over 4 years ago

First of please tell us which exact version of Tigase are you using (5.2 final?) and share your whole configuration file (sensitive data should/can be obscured).

Subsequently please:

  • check if there are any exceptions in tigase logs (i.e. logs/ directory),

  • describe how you want to join the room, which tools do you use (from the above exception I would guess Jitsi?).

Added by Jonathan Hunter over 4 years ago


Yes sorry, 5.2 Final.

And yes using Jitsi to connect, it outputs the attached error. (Jitsi log)

--virt-hosts =,

--auth-db-uri = jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase12

--user-db-uri = jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase12

--user-db = mysql

--admins =

--comp-name-3 = message-archive

--auth-db = tigase-custom

--comp-name-2 = proxy

config-type = --gen-config-def

--comp-name-1 = muc

--comp-class-1 = tigase.muc.MUCComponent

--sm-plugins = +amp,+message-all,+roster-presence,-jabber:iq:privacy

--debug = server

--comp-class-3 = tigase.archive.MessageArchiveComponent

--comp-class-2 = tigase.socks5.Socks5ProxyComponent

In logs I am seeing

MessageRouter.getLocalComponent() FINEST: Still no comp name matches (VHost lookup):

So presume thats related to the issue?

Also see tigase logs exert connected with domains changed.

Its shows user 2333 trying to add user 2703 to an MUC chat.



Added by Wojciech Kapcia TigaseTeam over 4 years ago

The entry in the logs serves only as information, later on there is correct entry that the packet will be process by muc component.

Two things I've noticed:

  • in Jitsi you are sending request to!

  • in the Tigase logs I have following entry:

<presence xmlns="jabber:client" id="JdtAK-153" to="" from=""><c xmlns="" ext="" node="" hash="sha-1" ver="ioKGfQS1h2a6Ysl4Csit+9VC4x8="/></presence>

As you can see, you are sending packet addressed to which is simply an attempt to change previously established nickname and Tigase currently doesn't support such hence returns you an 501 error, but you are still able to join and use the room.

Added by Jonathan Hunter over 4 years ago

Ok great thanks for the response.

Will sort it out on client side.