Can't get access to web console

Windows 2000 server, Erlang OTP R10B etc in compliance with tutorial.
config file by default (not changed).
then i go to the http://localhost:5280/admin i see the user/password information windows.
in windows i wrote - user - "admin" and password - blank or "admin" and i get the error - 401 Unauthorized.
What the user and password information i must set in this window?
where and how i must write the user name and user password?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I have read all of the

I have read all of the posts, following the instructions, tryed it in lynx and tryed it in firefox, and i still cannot connect. I have edited the config and done everything i could think of. can someone please help me?

robert

Without detailed information

Without detailed information (all your actions) it is very dificult to help you...

--
sander

Ok. I read the

Ok. I read the reference.
But anyway i can't get access.
This is my config
% $Id: ejabberd.cfg 347 2005-05-15 23:03:25Z alexey $

override_global.
override_local.
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, "schess"}}.
{acl, admin, {user, "open"}}.

% Blocked users:
%{acl, blocked, {user, "test"}}.

% Local users:
{acl, local, {user_regexp, ""}}.

% Another examples of ACLs:
%{acl, jabberorg, {server, "jabber.org"}}.
%{acl, aleksey, {user, "aleksey", "jabber.ru"}}.
%{acl, test, {user_regexp, "^test"}}.
%{acl, test, {user_glob, "test*"}}.

% Only admins can use configuration interface:
{access, configure, [{allow, all}]}.

% Every username can be registered via in-band registration:
{access, register, [{allow, all}]}.

% After successful registration user will get message with following subject
% and body:
{welcome_message,
{"Welcome!",
"Welcome to Jabber Service. "
"For information about Jabber visit http://jabber.org"}}.
% Replace them with 'none' if you don't want to send such message:
%{welcome_message, none}.

% List of people who will get notifications about registered users
%{registration_watchers, ["admin1@localhost",
% "admin2@localhost"]}.

% Only admins can send announcement messages:
{access, announce, [{allow, admin}]}.

% Only non-blocked users can use c2s connections:
{access, c2s, [{deny, blocked},
{allow, all}]}.

% Set shaper with name "normal" to limit traffic speed to 1000B/s
{shaper, normal, {maxrate, 1000}}.

% Set shaper with name "fast" to limit traffic speed to 50000B/s
{shaper, fast, {maxrate, 50000}}.

% For all users except admins used "normal" shaper
{access, c2s_shaper, [{none, admin},
{normal, all}]}.

% For all S2S connections used "fast" shaper
{access, s2s_shaper, [{fast, all}]}.

% Admins of this server are also admins of MUC service:
{access, muc_admin, [{allow, admin}]}.

% All users are allowed to use MUC service:
{access, muc, [{allow, all}]}.

% This rule allows access only for local users:
{access, local, [{allow, all}]}.

% Authentification method. If you want to use internal user base, then use
% this line:
{auth_method, internal}.

% For LDAP authentification use these lines instead of above one:
%{auth_method, ldap}.
%{ldap_servers, ["localhost"]}. % List of LDAP servers
%{ldap_uidattr, "uid"}. % LDAP attribute that holds user ID
%{ldap_base, "dc=example,dc=com"}. % Base of LDAP directory

% For authentification via external script use the following:
%{auth_method, external}.
%{extauth_program, "/path/to/authentification/script"}.

% Host name(s):
{hosts, ["localhost"]}.

% Default language:
{language, "en"}.

% Listened ports:
{listen,
[
{5222, ejabberd_c2s, [{access, c2s},
{shaper, c2s_shaper}]},

% To create selfsigned certificate run the following command from the
% command prompt:
%
% openssl req -new -x509 -days 365 -nodes -out ejabberd.pem -keyout ejabberd.pem
%
% and answer the questions.
% {5222, ejabberd_c2s, [{access, c2s},
% starttls, {certfile, "./ejabberd.pem"},
% {shaper, c2s_shaper}]},

% When using SSL/TLS ssl option is not recommended (it requires patching
% erlang ssl application). Use tls option instead (as shown below).
% {5223, ejabberd_c2s, [{access, c2s},
% tls, {certfile, "./ejabberd.pem"},
% {shaper, c2s_shaper}]},

{5269, ejabberd_s2s_in, [{shaper, s2s_shaper}]},

% {5555, ejabberd_service, [{access, all},
% {host, "icq.localhost", [{password, "secret"}]}]},

{5280, ejabberd_http, [http_poll, web_admin]}
]}.

% If SRV lookup fails, then port 5269 is used to communicate with remote server
{outgoing_s2s_port, 5269}.

% Used modules:
{modules,
[
{mod_register, [{access, register}]},
{mod_roster, []},
{mod_shared_roster, []},
{mod_privacy, []},
{mod_configure, []},
{mod_disco, []},
{mod_stats, []},
{mod_vcard, []},
{mod_offline, []},
{mod_announce, [{access, announce}]},
{mod_private, []},
{mod_irc, []},
% Default options for mod_muc:
% host: "conference." ++ ?MYNAME
% access: all
% access_create: all
% access_admin: none (only room creator has owner privileges)
{mod_muc, [{access, muc},
{access_create, muc},
{access_admin, muc_admin}]},
{mod_pubsub, []},
{mod_time, []},
{mod_last, []},
{mod_version, []}
]}.

% Local Variables:
% mode: erlang
% End:

i create user schess with "pandion". After that i correct config file, located in ejabberd root directory. but i can't get access to web console after that. anyway i see the 401 error. i use the schess@localhost username and pass or simple schess with pass but 401 and nothing else.

Where is the error?
help me!

I am having a similar

I am having a similar problem, with the exception that I have registered a user "admin" and "paulc" both are listed as admin users:
{acl, admin, {user, "admin"}}.
{acl, admin, {user, "paulc"}}

I've tried commenting out admin and just using paulc and commenting out paulc and just using admin.
soemthing I have noticed for example:
When I have just paulc listed as the admin, I then try to open the admin gui. if I type paulc as the user and [password] as the password, it prompts me again, like it didn't accept it. If i use paulc@thedomain.com (where thedomain.com is the domain i have it configured with), and the password, it then gives me the Not Allowed error.
Does the configured domain have to be a FQDN? This is an internal machine and not connected to the net. Why would it not allow the admin account I have defined, login? The server is running, I can login to it with both of the accounts I defined above.

Thanks
Paul C.

You can put as many admins

  • You can put as many admins as you want.
  • Take a look at the logs, too.
  • Instead of just
    {acl, admin, {user, "paulc"}}.
    Try with this:
    {acl, admin, {user, "paulc", "thedomain.com}}.
  • When asked for user and passwd on the wedamin, use paulc@thedomain.com
  • If it still says 'Not Allowed', maybe the user is not admin at all.

How to check if a user is admin:

  1. With a 'Jabber Discovery'-enabled client like Exodus, Tkabber, Psi login with that account
  2. Open the Discovery/Browser.
  3. You will be see 'conference', 'pubsub', 'vjud'...
  4. If you can see 'online users', 'all users', 'config'... then that user has admin privileges. If no, then he hasn't.

Thanks!! adding the domain

Thanks!! adding the domain after the username fixed it!

Similar problem

I also cant get access to my new ejabberd implementation web console; i connect on the right url, and it asks for authentication (which apparently is working correctly). But i get this from my browser right after logging in:

An error occurred while loading http://im.metrored.com.mx:5280/admin:
Connection to host im.metrored.com.mx is broken.

What could cause this?

Check the ejabberd log

Check the ejabberd log files, maybe you find some usefull information. That exact error message doesn't seem to be produced by ejabberd: it isn't a problem with your password, or with your admin rights...

You can try to do this on the same machine where ejabberd is installed, to be sure it isn't an ejabberd problem. If you don't have phisical access to the machine, maybe you can use SSH and a command-line browser like Lynx.

Already tried acessing locally using Lynx, no go...

This is the output of a local lynx access attempt:

[root@NMU-IT-WSDB1 conf]# lynx http://localhost:5280/admin -verbose

Looking up localhost:5280
Making HTTP connection to localhost:5280
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Access without authorization denied -- retrying
Retrying with access authorization information.
Looking up localhost:5280
Making HTTP connection to localhost:5280
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `http://localhost:5280/admin'
Alert!: Unable to access document.

lynx: Can't access startfile

And this is what the logfile has to say about it:

=INFO REPORT==== 2006-05-02 09:53:05 ===
I(<0.216.0>:ejabberd_listener:90): (#Port<0.1113>) Accepted connection {{127,0,0
,1},38907} -> {{127,0,0,1},5280}

=INFO REPORT==== 2006-05-02 09:53:05 ===
I(<0.209.0>:ejabberd_http:76): started: {gen_tcp,#Port<0.1113>}

=INFO REPORT==== 2006-05-02 09:53:11 ===
I(<0.2142.0>:ejabberd_http:171): (#Port<0.1113>) http query: 'GET' /admin

I dont see much to go on troubleshooting from that information; any ideas?

Surf the web interface with Lynx

My Jabber server is called "localhost":

$ cat ejabberd.cfg | grep "^{host"
{hosts, ["localhost"]}.

I created an account with username "badlop" and password "mypass". That account has admin rigths:

$ cat ejabberd.cfg | grep badlop
{acl, admin, {user, "badlop", "localhost"}}.

If I try to access the web interface, ejabberd will ask me to login:

$ lynx http://localhost:5280/admin -dump
HTTP: Access authorization required.
       Use the -auth=id:pw parameter.

Looking up localhost:5280
Making HTTP connection to localhost:5280
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Access without authorization denied -- retrying

lynx: Can't access startfile http://localhost:5280/admin

If I specify wrong user or password I get an error message:

$ lynx http://localhost:5280/admin -dump -auth=badlopqqqq@localhost:iforgotmypass

or

$ lynx http://localhost:5280/admin -dump -auth=badlop@localhost:iforgotmypass

Looking up localhost:5280
Making HTTP connection to localhost:5280
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Access without authorization denied -- retrying
Retrying with access authorization information.
Looking up localhost:5280
Making HTTP connection to localhost:5280
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Can't retry with authorization!  Contact the server's WebMaster.
Can't Access `http://localhost:5280/admin'
Alert!: Unable to access document.

lynx: Can't access startfile

If I specify the correct user and password, it works correctly:

$ lynx http://localhost:5280/admin -dump -auth=badlop@localhost:mypass

[1]Administración

     * [2]Listas de Control de Acceso
     * [3]Reglas de Acceso
     * [4]Hosts Virtuales
     * [5]Nodos
     * [6]Estadísticas
...
Syndicate content