ejabberd - Comments for "Install on Windows, but cant get to web interface"

Proposed in the bug tracker

mfoss — Wed, 19 Mar 2008 01:53:08 +0000

Thanks for reporting this. I guess the best is to explain correctly in the installer, so I submited this proposal: Clarify the explanation about the admin user name

Another problem...

vm — Sat, 15 Mar 2008 20:39:03 +0000

I found that if you choose an admin user name during install that has a space in it, for instance, "John Doe", instead of "JohnDoe" you will not be able to login into the admin web interface. I modified the space out of the config file and it worked.

Waiting for the release version

denmarkleaf — Wed, 13 Feb 2008 01:38:14 +0000

I've read the problem's detail. Thanks:)

As Badlop Said

denmarkleaf — Wed, 13 Feb 2008 01:31:29 +0000

e.g.
"testserver" --> "TestServer"

Ok, problem tracked

mfoss — Mon, 11 Feb 2008 16:21:35 +0000

Thank you for explaining how to reproduce the problem. Now I can finally reproduce it: when in the binary installer you specify a domain name with some capital letters, the account created in the database specifies the domain in lower case, but the ACL line added in your ejabberd.cfg still uses capital letters.

ejabberd 2.0.0-rc1 reads the ACL line as it is, and later the capitalization doesn't match. Until this improvement is made, the solution for the current 2.0.0-rc1 (and older) is to edit ejabberd.cfg and replace all the appearances of 'DOMAIN' with 'domain'.

Problem tracked here:
Normalize ACL before adding to the configuration tables

Which version are you using

mremond — Mon, 11 Feb 2008 11:05:12 +0000

Which version are you using ?
I cannot reproduce your problem here in version 2.0rc1

--
Mickaël Rémond
Process-one

could you send us your

mremond — Mon, 11 Feb 2008 11:03:18 +0000

could you send us your bitrock*.log files ?

They should be in one of your temporary directory.
It will help us understanding why the postinstall script failed in your case.

Thank you !

--
Mickaël Rémond
Process-one

Settled

denmarkleaf — Mon, 11 Feb 2008 05:59:50 +0000

Tried some tests, I've settle the problem. Thanks a lot for badlop and others who pay attention to this problem and help me.
The problem seems very simple, although it puzzled me for a long time. THAT IS, when your os computer name has capital letters, even you write the right user name and password, you also get Unauthorized page. Every one who are interested on it can test it. I think there is a bug when check the admin user.

Yes, it has

denmarkleaf — Fri, 01 Feb 2008 03:04:59 +0000

I am sorry that I didn't describe clearly.
In the ejabberd.cfg,the line you indicated exists and the information is right.

Check if the user has admin rights

mfoss — Thu, 31 Jan 2008 09:16:13 +0000

denmarkleaf wrote:

I tried 1 and 3. About 2,I contrast the ejabberd.cfg with the one on the available OS. Only the domain name is different. So No.2 test is passed.

Did you understand what I said in 2.?
In your ejabberd.cfg, you must have a line that gives admin privileges to your user:

{acl, admin, {user, "admin", "example.org"}}.

Thanks for your attention

denmarkleaf — Thu, 31 Jan 2008 08:43:11 +0000

I tried 1 and 3. About 2,I contrast the ejabberd.cfg with the one on the available OS. Only the domain name is different. So No.2 test is passed.
The cmd/regedit/taskmanager are also in gear.
I am very puzzled.
Thanks a lot. I even want to reinstall the os, but still not. Because I think there must be some problem with the Windows environment.
How about your opinion? Thanks for your help.:)

Check if the installer granted admin privileges

mfoss — Wed, 30 Jan 2008 10:16:03 +0000

There can be three different problems:

The Jabber account was not created in the Jabber server during the installation. To check if it exists, try to login using a normal Jabber client in the account.
The Jabber account exists, but doesn't have admin privileges. To check if it has privileges, look in ejabberd.cfg for a line that says: {acl, admin, {user, "admin", "example.org"}. or similar
The account exists and has admin privileges, but you put the wrong JID or password.

In your case you already tested 1. and 3. Can you check 2.? If that's your problem, you can simply add the mentioned line.

Also, can you try this in the Windows machine that gives you problems?

Go to Start menu, Run, and put: cmd. Does the MS-DOS command-line open?
Go to Start menu, Run, and put: regedit. Does the Registry Editor open?
Press Ctrl+Alt+Supr. Does the Task Manager open?

same same same

Anonymous — Mon, 28 Jan 2008 19:17:54 +0000

I think everyone running 2.0.0-rc1 on Windows has the same problem

yes

denmarkleaf — Mon, 28 Jan 2008 07:46:20 +0000

Yes,I put it correctly like "admin@mydomainname", and the password is alos correct. But still "401 Unauthorized":(

username in webadmin -

evadim — Mon, 28 Jan 2008 06:46:47 +0000

username in webadmin - "admin@you-domain.tld" , not "admin"