ejabberd - Comments for "Once again: Login into Webadmin fails"

in 1.1.2 still same problem with web admin console

weij — Tue, 03 Oct 2006 07:47:49 +0000

hi all,

still have the same problem with version 1.1.2.
the problem exist with the initial administrator and a new account.
are there any other known solutions?

override_acls.
{acl, admin, {user, "admin", "hostname"}}.
{acl, local, {user_regexp, ""}}.
{access, pubsub_createnode, [{allow, all}]}.
{access, configure, [{allow, admin}]}.

If I exchgange following line with the next one it works fine!!!
{access, configure, [{allow, admin}]}.
{access, configure, [{allow, all}]}.

When I log on to Web Console I can see I AM an Administrator. But I still can´t connect when I use the first line!?
(I don´t know if this is important - I used the Installer Package)

thanks for advise

joe

works fine, thx again.

kriz99 — Fri, 29 Sep 2006 13:36:07 +0000

works fine, thx again.

Yes, the latter is probably

sander — Wed, 27 Sep 2006 16:20:48 +0000

Yes, the latter is probably better, but FreeBSD is also a good alternative for ejabberd ;-)

--
sander

I do know Cygwin, but never

kriz99 — Wed, 27 Sep 2006 09:44:47 +0000

I do know Cygwin, but never tried... but installing the whole package only to add an admin? I'm not sure... I think I wait for 1.2 beta - or switch to Linux. ;-)

The ejabberd 1.1.1 installer

mfoss — Wed, 27 Sep 2006 09:12:49 +0000

The ejabberd 1.1.1 installer was compiled for Erlang R10B-10, and you installed R11B instead. Just uninstall R11 and install R10.

Cygwin is Windows software;

sander — Wed, 27 Sep 2006 08:34:55 +0000

Cygwin is Windows software; it adds missing parts to Windows ;-)

--
sander

I've tried it with Exodus

kriz99 — Wed, 27 Sep 2006 06:27:38 +0000

I've tried it with Exodus using:

Quote:

Jabber ID: admin@jabber.local
Password: admin
Ressource: WORK (btw: what stands that for?)
Priority: 1
Save PWD: checked
This is a new account: checked

...but the server only responds this:

Quote:

Erlang (BEAM) emulator version 5.5.1 [async-threads:0]

Eshell V5.5.1 (abort with ^G)
(ejabberd@wss08)1>
=INFO REPORT==== 27-Sep-2006::07:21:46 ===
I(<0.225.0>:ejabberd_listener:90): (#Port<0.326>) Accepted connection {{172,17,
xxx,xxx},1115} -> {{172,17,xxx,xxx},5222}

=ERROR REPORT==== 27-Sep-2006::07:21:47 ===
** Generic server <0.289.0> terminating
** Last message in was {tcp,#Port<0.326>,
<<"">
}
** When Server state == {state,#Port<0.326>,
gen_tcp,
none,
<0.288.0>,
infinity,
{xml_stream_state,
<0.288.0>,
#Port<0.331>,
[],
0,
infinity},
infinity}
** Reason for termination ==
** {badarg,[{erlang,binary_to_term,
[<<0,0,0,0,131,108,0,0,0,1,104,2,97,0,104,2,107,0,13,115,11
,114,101,97,109,58,115,116,114,101,97,109,108,0,0,0,4,104,2,107,0,2,116,111,107
0,12,106,97,98,98,101,114,46,108,111,99,97,108,104,2,107,0,5,120,109,108,110,11
,107,0,13,106,97,98,98,101,114,58,99,108,105,101,110,116,104,2,107,0,12,120,109
108,110,115,58,115,116,114,101,97,109,107,0,32,104,116,116,112,58,47,47,101,116
104,101,114,120,46,106,97,98,98,101,114,46,111,114,103,47,115,116,114,101,97,10
,115,104,2,107,0,7,118,101,114,115,105,111,110,107,0,3,49>>]},
{xml_stream,parse,2},
{ejabberd_receiver,process_data,2},
{ejabberd_receiver,handle_info,2},
{gen_server,handle_msg,6},
{proc_lib,init_p,5}]}

What does that mean?

Windows installer

kriz99 — Wed, 27 Sep 2006 05:51:31 +0000

Ok... then I wait 'til it's released and try again.

Cygwin

kriz99 — Wed, 27 Sep 2006 05:48:12 +0000

sander wrote:

1 will probably work when you install Cygwin. You better do this, because it makes Windows less userunfriendly

If I wanted to run Linux I would have installed it. :-D

The upcoming packaged

mremond — Tue, 26 Sep 2006 21:24:30 +0000

The upcoming packaged Windows installer let you define the admin account and password at installation time.
It has been in beta test and it will be release for ejabberd 1.1.2 (due tomorrow).

--
Mickaël Rémond
Process-one

1 will probably work when

sander — Tue, 26 Sep 2006 17:35:37 +0000

1 will probably work when you install Cygwin. You better do this, because it makes Windows less userunfriendly :o)

--
sander

create the jabber account with any client

mfoss — Tue, 26 Sep 2006 14:22:08 +0000

kriz99 wrote:

Is 1. possible with Ejabbered on Windows?

Not that I'm aware, but don't worry.

kriz99 wrote:

Or what Client can I take do do this (I have exodus installed)?

Most Jabber clients can register accounts, Exodus too.

Thx... your right! But I

kriz99 — Tue, 26 Sep 2006 14:07:18 +0000

Thx... your right! But I believe I've even missed "3.3 Creating an Initial Administrator"! Sorry, my mistake.

Quote:

Instructions to create an initial administrator account:

1. Register an account on your ejabberd deployment. An account can be created in two ways:
1. Using the tool ejabberdctl (see section 3.4.2):

% ejabberdctl node@host register admin example.org password

2. Using In-Band Registration (see section A.14): you can use a Jabber client to register an account.

Is 1. possible with Ejabbered on Windows? Or what Client can I take do do this (I have exodus installed)?

Thx again,
Chris

kriz99 wrote: When I go to

mfoss — Tue, 26 Sep 2006 13:46:07 +0000

kriz99 wrote:

When I go to http://host:5280/admin and try to login using:

admin@jabber.local
admin

My ejabberd.cfg:

Quote:

...
%override_acls.

% Users that have admin access. Add line like one of the following after you
% will be successfully registered on server to get admin access:
%{acl, admin, {user, "aleksey"}}.
%{acl, admin, {user, "ermine"}}.
{acl, admin, {admin, "admin", "jabber.local"}}.

Where is the problem?

The syntax on your ejabberd.cfg is not correct, and you will need to override the old ACLs, so replace

Quote:

%override_acls.
{acl, admin, {admin, "admin", "jabber.local"}}.

with

Quote:

override_acls.
{acl, admin, {user, "admin", "jabber.local"}}.