ejabberd - Comments for "FreeBSD 5.4 Problems starting...."

Re: Tks for the reply. I

mfoss — Sat, 24 Dec 2005 00:02:03 +0000

blake wrote:

But by running ejabberctl as user ejabberd, it all seems to work. Is it ok to continue this way? Or is there some reason it's better not to do this?

I think it's ok, and in fact avoiding the root account is a good idea for security reasons.

blake wrote:

Now when I try to log on to the web, having set my user as an admin in the ejabberd.cfg, it does not accept the logon.

http://ejabber.my.local:5280/admin/

brings up the logon:

Name: blake
Pass: password

No go!

When you browser asks for the 'username', put the full JID. It's described on the ejabberd guide.

Tks for the reply. I

blake — Fri, 23 Dec 2005 23:32:37 +0000

Tks for the reply. I appreciate your help.
I've no knowledge at all of erl, so hope I can grasp this.

Quote:

I think the reason is: ejabberdctl and ejabberd must have the same 'cookie' (it's an Erlang/OTP thing, not related to your webbrowser). The cookie can be set on $HOME/.erlang.cookie, or with -setcookie SDADSAD option when calling 'erl'.

I'm not clear how to set the cookies at all. But by running ejabberctl as user ejabberd, it all seems to work. Is it ok to continue this way? Or is there some reason it's better not to do this?

Quote:

Ejabberd says this when I put a wrong Jabber server. If you say 'blake ejabber password', in ejabberd.cfg you have something like this, right?

I still had the full domain name here, so changed it. It then registered a new user. It now shows when asked to list:

blake@ejabber

Now when I try to log on to the web, having set my user as an admin in the ejabberd.cfg, it does not accept the logon.

http://ejabber.my.local:5280/admin/

brings up the logon:

Name: blake
Pass: password

No go!

I am now able to register new users from client programs, so that's good.

tks.

~ blake

Re: FreeBSD 5.4 Problems starting....

mfoss — Fri, 23 Dec 2005 20:33:55 +0000

blake wrote:

from my system, as root:
ejabberdctl ejabbderd@ejabber status

error returned:
Can't get node ejabbderd@ejabber status: nodedown

If I su to user jabberd and do the same:
ejabberdctl ejabbderd@ejabber status

results:
Node ejabberd@ejabber is started. Status: started

blake wrote:

When trying to register a new user as user jabberd:
ejabberdctl ejabberd@ejabber register blake ejabber password

results:
Can't register user "blake@ejabber" at node ejabberd@ejabber: not_allowed

Ejabberd says this when I put a wrong Jabber server. If you say 'blake ejabber password', in ejabberd.cfg you have something like this, right?

{hosts, ["ejabber"]}.