Thanks for your post, which I found when trying to find out why
Conversations kept coming up with "No group chat server found".  You
have probably resolved this by now, but I thought I would let you know
that I believe I have on my own system.  I can't be sure exactly which
bit I needed to get right, but I got there via seeing what ejabberd
defaulted to, and then replicating that on prosody.

In particular, I used the same convention for the muc name as ejabberd
hard-codes,  conference.machine.doman, whereas previously, I used a
newly made up name, chatroom.domain.  But I think the real clincher was
the muc_mam module. I had this in the wrong place. After this, I could
create groups on the Conversations client.

For what it's worth, I have written up my system notes on my blog. I'll
not give a URL as I believe this email goes to a list service, but it's
on my domain as in this email /blog

But thanks again for being part of my trail to get prosody purring.

Best wishes

Stevan

Stevan Lockhart <stevan@vasten.co.uk> wrote:

> Thanks for your post, which I found when trying to find out why
> Conversations kept coming up with "No group chat server found".  You
> have probably resolved this by now, but I thought I would let you know
> that I believe I have on my own system.  I can't be sure exactly which
> bit I needed to get right, but I got there via seeing what ejabberd
> defaulted to, and then replicating that on prosody.

Interesting approach! I solved it by fixing up my Prosody config to
point to the correct VirtualHost (had to set it to icyphox.sh).

> For what it's worth, I have written up my system notes on my blog. I'll
> not give a URL as I believe this email goes to a list service, but it's
> on my domain as in this email /blog

Will check those out.

> But thanks again for being part of my trail to get prosody purring.

I'm glad my post was of help. Thank you for writing to me. :)

--
Anirudh Oppiliappan
https://icyphox.sh