Running XMPP (Metronome) on a domain name different than the main one

Support apps
,
6

I fixed that too. Same results so far.

Interestingly enough, when I try to check in Gajim Accounts ↦ Discover Services for both servers, they both seem to work.

monolith. shows Metronome as running, with muc., vjud., pubsub. and xmpp-upload. services running; and jabber. as “None”
monolith. shows Metronome as running, with muc., vjud., pubsub. and xmpp-upload. services running; and jabber. as “None”630×736 71.5 KB

campfire. shows Metronome as running, with biboumi., muc., vjud., pubsub. and xmpp-upload. services running; and jabber. as “None”
campfire. shows Metronome as running, with biboumi., muc., vjud., pubsub. and xmpp-upload. services running; and jabber. as “None”630×736 82.9 KB

… could it be that YunoHost simply did not create the accounts for Metronome on campfire.?

This is what happens now when I try to log into campfire. using Gajim:

Jan 06 16:36:05 socket	debug	accepted incoming client connection from: 192.168.88.82 56554 to 5222 
Jan 06 16:36:05 c2s55b8b7fb5540	info	Client connected
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Client sent opening <stream:stream> to campfire.wheremymonkeyis.at
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Sent reply <stream:stream> to client
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Received[c2s_unauthed]: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
Jan 06 16:36:05 socket	debug	try to start ssl at client id: 55b8b7fb5540 
Jan 06 16:36:05 socket	debug	ssl session delayed until writebuffer is empty... 
Jan 06 16:36:05 c2s55b8b7fb5540	debug	TLS negotiation started for c2s_unauthed...
Jan 06 16:36:05 socket	debug	starting ssl handshake after writing 
Jan 06 16:36:05 socket	debug	starting handshake... 
Jan 06 16:36:05 socket	debug	ssl handshake of client with id:table: 0x55b8b7fb5540, attempt:1 
Jan 06 16:36:05 socket	debug	ssl handshake of client with id:table: 0x55b8b7fb5540, attempt:2 
Jan 06 16:36:05 socket	debug	ssl handshake of client with id:table: 0x55b8b7fb5540, attempt:3 
Jan 06 16:36:05 socket	debug	ssl handshake of client with id:table: 0x55b8b7fb5540, attempt:4 
Jan 06 16:36:05 socket	debug	ssl handshake of client with id:table: 0x55b8b7fb5540, attempt:5 
Jan 06 16:36:05 socket	debug	ssl handshake done 
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Client sent opening <stream:stream> to campfire.wheremymonkeyis.at
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Sent reply <stream:stream> to client
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Received[c2s_unauthed]: <auth mechanism='PLAIN' xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jan 06 16:36:05 campfire.wheremymonkeyis.at:auth_ldap2	debug	_M.bind - no DN found for username = hook
Jan 06 16:36:05 campfire.wheremymonkeyis.at:saslauth	debug	sasl reply: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/><text>Unable to authorize you with the authentication credentials you&apos;ve sent</text></failure>
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Received[c2s_unauthed]: <abort xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Received </stream:stream>
Jan 06 16:36:05 c2s55b8b7fb5540	info	c2s stream for <192.168.88.82> closed: session closed
Jan 06 16:36:05 c2s55b8b7fb5540	debug	Destroying session for (unknown) ((unknown)@campfire.wheremymonkeyis.at)
Jan 06 16:36:05 socket	debug	try to close client connection with id: 55b8b7fb5540 
Jan 06 16:36:05 socket	debug	closing delayed until writebuffer is empty 
Jan 06 16:36:05 socket	debug	closing client after writing 
Jan 06 16:36:05 socket	debug	closing client with id: 55b8b7fb5540 client to close 
Jan 06 16:36:05 c2s55b8b7fb5540	info	Client disconnected: connection closed

I may be wrong, but this part strikes me:

Jan 06 16:36:05 campfire.wheremymonkeyis.at:auth_ldap2	debug	_M.bind - no DN found for username = hook

Could it be related to this?