ejabberd - Comments for "Can't retrieve muc archives"

After updating to the latest

Qwerty — Thu, 22 Dec 2016 13:49:14 +0000

After updating to the latest release everything works -)

Muc messages arrive just as p2p archives, everything is fine -)

Hi, we've compiled server

Qwerty — Wed, 21 Dec 2016 16:15:59 +0000

Hi, we've compiled server from sources and have it running. Currently have some issues creating group chats.

Will get back as soon as we can.

You can go to your developer

badlop — Fri, 16 Dec 2016 10:41:37 +0000

You can go to your developer machine, install the same erlang and download the same ejabberd sources used in the production machine. Apply the patch, compile the relevant module (or all), and copy the changed *.beam file to the production machine.

Thanks for the

Qwerty — Mon, 12 Dec 2016 15:12:42 +0000

Thanks for the reply,

Currently we have server in the form of a binary. We'll setup a chat server from ejabberd sources and get back to you.

Thanks again, cheers.

Hi, I installed 16.04,

badlop — Mon, 12 Dec 2016 10:44:31 +0000

Hi, I installed 16.04, enabled mod_mam with the default:always option, created an account, logged in, created a room, configured the room to archive, sent a message to the room, then sent a request similar to yours, just replacing the TO attribute with the room full jid (in my case "room1@conference.localhost"), and I got a valid response.

I also tried to make some mistakes, like providing invalid TO address, disabling the option, the module... and I couldn't get exactly the same error than you, that 501.

Apply this patch, compile, reinstall, restart, try again, and see if anything relevant appears in the ejabberd logs when you make the request: