ejabberd - Comments for "Install MUCkl - Multi-User Chat Web Frontend"

most likely too late for the

kurniawan — Fri, 10 Jul 2015 21:03:19 +0000

most likely too late for the OP, but i hope this would help somebody else.

i had the same problem using Chrome web browser, something to do with CORS (and to allow that i need to deliver specific header entries in response, didn't have time for rebuilding from source etc.)
quick work-around is to use "binding" type instead of "polling", also needs to configure "/http-bind" for Apache's mod_rewrite, port is the same, target path is "http-bind" (essentially replace "poll" with "bind"), then point HTTPBASE in config.js to "/http-bind". one last thing, enable mod_http_bind in "modules" section in ejabberd.cfg

install on debian

wattafunnyname — Thu, 21 Apr 2011 13:20:50 +0000

i tried to follow all the instruction above.
the ejabberd server is working , with admin account and persistant room.

and all the other configurations.

but when i log in there is just a blank screen with only a background image.

no error messages (apache, ejabberd, firebug...)what so ever.

can you help me?

p.s.
apache is configured correctly to reach hostname.tld/http-poll

Create a persistent room with muckl?

ripleyr — Mon, 29 Jun 2009 19:54:03 +0000

Oops, my mistake. I believe the problem is a coding issue with my modified version of muckl. I've been able to successfully create persistent rooms using a clean copy of muckl, so the problem must be with my modified version. I'll get it straightened out. Sorry for the distraction!

Create a persistent room with muckl?

ripleyr — Mon, 29 Jun 2009 16:39:25 +0000

Yes, that makes the rooms public, I understand. But still if the server is rebooted or ejabberd restarted, those rooms created through muckl no longer exist (are no longer accessible). So they are not really persistent for some reason. I have muckl customized so that there are no predefined rooms in its config file. Rooms are created when an admin uses a specially configured muckl (that authenticates with the ejabberd admin account) to access a room. Then non-admin users use another installation of muckl that authenticates with a regular user account to access the room. It all works well until the server is rebooted or ejabberd restarted. Then the regular users get error "Room creation is denied by service policy" when they enter a room because the room doesn't exist anymore and only admins have the rights to create a room.

Now, if I create a room using a jabber client like Exodus, then the rooms ARE persistent and survive a restart/reboot. But only when the rooms are created via an admin using muckl are the rooms not persistent.

With your configuration, the

mfoss — Wed, 24 Jun 2009 21:42:15 +0000

With your configuration, the new rooms are persistent, but they are not publicly visible in the Service Discovery. Make sure you have this to true:

{public, true},

Create a persistent room with muckl?

ripleyr — Wed, 24 Jun 2009 18:00:32 +0000

> Create a Persistent Room
>
> Create a persistent chatroom with a Multi-User Chat compatible Jabber client and ensure
> yourself that the user you created in previous step has sufficient permissions to this chatroom.

Does anyone know if muckl can create a persistent room? I have ejabberd.cfg configured for persistent rooms as the default, but if I connect to ejabberd with muckl (even if I configure muckl to use the ejabberd admin username/password), it will create a room, but it is not persistent. If the ejabberd service is restarted, the room is dropped. I want admins to create rooms by entering the room with muckl and then non-admin users can enter those rooms with muckl. But I don't want non-admins to be able to create a room. Here's my settings:

{mod_muc, [
%%{host, "conference.@HOST@"},
{access, muc},
{access_create, muc_admin},
{access_persistent, muc_admin},
{access_admin, muc_admin},
{history_size, 20},
{min_message_interval, 0.4},
{min_presence_interval, 4},
{default_room_options,
[
{allow_change_subj, false},
{allow_private_messages, false},
{allow_query_users, false},
{allow_user_invites, false},
{allow_visitor_nickchange, false},
{allow_visitor_status, false},
{anonymous, true},
{logging, true},
{max_users, 200},
{members_by_default, true},
{members_only, false},
{moderated, false},
{password_protected, false},
{persistent, true},
{public, false},
{public_list, false},
{title, "chatroom"}
]}
]},

Internal Server Error

bindalf — Fri, 06 Mar 2009 12:08:22 +0000

After some time in a channel, connected with Muckl to ejabberd, i get a "Internal Server Error, Reconnect ?" popup. Nothing in ejabberd logfile.
With other clients i have no problems. i use http binding. What could cause the Internal Server Error ?

How to prevent password change

mfoss — Sun, 25 Nov 2007 10:44:37 +0000

Captain_Fantastic wrote:

At the moment any jabber client can be log in using the muckl credentials stored in config.js, change the password,

If the Jabber account used my MUCkl is muckl@example.org, this will prevent him from changing the password or registering new accounts:

{acl, muckl, {user, "muckl", "example.org"}}.
{access, register, [{deny, muckl}, {allow, all}]}.
{modules,
 [
  ...
  {mod_register,   [
        ...
        {access, register}
  ]},
  ...
]}.

Captain_Fantastic wrote:

send messages to random users and everything else a normal user can do.

I can only think of two possibilities: using privacy lists or Legoscia's mod_filter.

account lock down

Captain_Fantastic — Sun, 25 Nov 2007 01:30:57 +0000

It would be nice if you could add how to stop the muckl user on the server from doing anything that isn't needed for Muckl.

At the moment any jabber client can be log in using the muckl credentials stored in config.js, change the password, send messages to random users and everything else a normal user can do.

Blacklisting IPs would be handy too. (Could this work when the traffic is proxied by the webserver?)

Muckl's great :)

Modules need to be loaded on Apache2

Florian Jensen — Thu, 11 Oct 2007 18:33:42 +0000

Hey,

I had some problems with Apache2 and HTTP-Polling. The thing that needs to be done: You need the mod_rewrite and ALL proxys (proxy proxy_connect proxy_http)

And alter apache2/mods-enabled/proxy.conf and add the allowed domain.

Fixed

mfoss — Wed, 11 Jul 2007 07:22:26 +0000

Yes, thanks, fixed.

>> Port Module

Anonymous — Wed, 11 Jul 2007 01:00:21 +0000

>> Port Module Options
>> 5280 ejabberd_http [http_poll, web_admin]}]

Shouldn't it be

Port Module Options
5280 ejabberd_http [http_poll, web_admin]