I'm new here. I have searched and read many posts here for the past hours trying to resolve the issues I'm having. I am posting as a last resort.
Everything installs fine on FreeBSD5.4. No problems at all.
Starting from the rc.d appears to be fine.
To check that the server is running I run:
hostname: ejabber.my.server
hostname -s returns: ejabber
ejabberd.cfg hostname: ejabber
ejabberd.sh start script, hardcoded to host: ejabber
(from reading other posts some found it worked to use the short domain name)
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
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
I have successfully been running the Jabber 1.4 for years. I seeking to upgrade to something hopefully better, I have settled on ejabber as my choice.
Any help on what I'm doing wrong here? It's probably that I don't quite grasp how this is working.
TIA!
~ blake
Re: FreeBSD 5.4 Problems starting....
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
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'.
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"]}.Tks for the reply. I
Tks for the reply. I appreciate your help.
I've no knowledge at all of erl, so hope I can grasp this.
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?
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.
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: Tks for the reply. I
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.
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.
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.