Looking for ejabberd docs?

To access the most up-to-date ejabberd documentation, please visit docs.ejabberd.im »

Modified ACL and now get read errors with Jabber Clients

Submitted by gonoles_1980 on Fri, 2006-09-08 00:43

I tried to modify the ejabberd.cfg file to add new virual hosts so I could see the users from the web interface.

I added

{acl, admin, {foobarname, "admin", "mydomain.net"}}.

Now I get a read error from the jabber client Gaim and JWChat doesn't connect.

I removed this the line above from the ejabberd.cfg, but it looks like the information is still in the database. I was working until I made that change, any ideas on what to do?

Reload and override

Submitted by legoscia on Fri, 2006-09-08 10:18.

At the top of your ejabberd.cfg, there is a line:

%override_acls.

Remove the % sign at the beginning. Then follow the instructions for reloading the configuration.

(The % sign is the Erlang comment sign. Removing it thus makes the directive override_acls active, which is what you need in this case.)

That works.

Submitted by gonoles_1980 on Fri, 2006-09-08 22:22.

So simple :(, I feel like a dunce.

Thanks a bunch for the help :).

I decided to ask in this

Submitted by Makc666 on Mon, 2006-09-11 12:00.

I decided to ask in this topic.

In Web Admin I make ANY changes for my sever configuration.
For example I change some mod_* settings.

Then I stop ejabberd and star it again.
When I go to Web Admin interface I see that none of those changes have been saved.

Also I see that ejabberd.cfg file was not changed during stop-start.

How I can make so that all changes in Web Admin were saved after server restart?

Thanks

ejabberd.cfg is never

Submitted by mfoss on Mon, 2006-09-11 12:05.

ejabberd.cfg is never modified. Some configuration changes you make on the web admin are stored on the database (users, rosters, ACL and Access), and others aren't (listening sockets and modules).