I am running Windows Server 2k3 and i have ejabberd started, and i get a page saying
"By default, the web administration interface is enabled. You should be able to connect to the admin interface and log in with the user admin@DOMAIN and the password you defined during the installation.
i have tried EVERYTHING to get this to work. logged in with admin@DOMAIN, just admin, ejabberd@localhost. I know the password i entered at setup and i have reinstalled a couple times cause i though maybe i just didnt have it down correctly. No matter what i do i get the Unauthorized page. is this a known problem, or am i over looking something ?
ejabberd expects the same
ejabberd expects the same JID and password of the Jabber account created during the setup, so admin@domain and the password should be ok.
Did you try to login on the Jabber server with a Jabber client, indicating that same JID and password? It should work.
Check also ejabberd log files, they may indicate an error.
Same problem
I've installed ejabberd-1.1.2 on my XP machine and facing the same problem-can't log in to the admin web interface.
Yah I am trying with the full JID and password that I gave during the installation process..but still no luck.
Nebody has ne idea how to solve this problem ?.
Why not?
can't log in to the admin web interface.
Why not? What error do you get?
Authorization prob
Don know !! While I enter JID and pwd the login prompt returns and after returning for 3 times I get a "401 Unauthorized" message on the browser.I don c ne error message on the Erlang console.
I guess it's kinda authorization failure,but I'm confident about my JID and pwd and tried 2nd time uninstalling ejabberd and installing it back.
Can u tell me why it's happening ?
I too am having the exact
I too am having the exact same problem.
Windows XP Pro SP2 - Windows Install.
Get to the admin logon screen and it just won't accept my JID:PW combo. I'm very confident my PW is correct. Seems like this is a common problem for Windows users...what's going on?
Any help would be greatly appreciated.
Seconded... Thirded... Fourthed..???
Exactly the same problem.
Windows XP SP2 w/ Internet Explorer 7, windows installer, ejabberd v.1.1.2
windows installer account creation, using the account@host format for the userID..etc.
I know this is redundant, but there isn't a clearly visible way to fix it publicly displayed yet...
Same issue here
I too am having the login issue. WinXP SP2. It acts like the user/pass is wrong. Anyone have any ideas?? Or is it time to look elsewhere?
Erlang on Windows
Erlang on Windows is the problem.
On some install, Erlang cannot work on Windows in network mode. It means that ejabberd cannot start and that the postinstall script creating the initial user cannot work too.
We have looked a bit into it, but it seems that
In this case, the Erlang console simply displays an enotsock error (cannot listen to socket as it is supposed not to be a socket).
From what I understand, several thing can corrupt the socket driver on Windows.
Maybe you could check this URL and tell us if it helps:http://support.microsoft.com/kb/811259 http://windowsxp.mvps.org/winsock.htm http://www.cit.cornell.edu/computer/security/spyware/repair.html
Regarding the damaged Winsock, there is several web site on the Internet dealing with this Windows annoyance:
- From Microsoft website,
How to determine and recover from Winsock2 corruption:
-
-
Thank you for your help,
--
Process-one
Mickaël Rémond
FAQ entry contribution
If anyone in this thread can fix the issue, he maybe can contribute a FAQ entry intead of or besides a success reply to this thread.
--
sander
Had the same problem, got into administration
I just started working with this today and ran into the same situation. I have not yet attempted to use it, only to access administration.
I found if you install using localhost you can access administration.
I created an entry in hosts with the computers IP address called jabber, told the install the location was jabber.http://jabber:5280/admin/ and accessed the admin like I should.
Started ejabbered, entered
This could be a workaround to the problem, granted not ideal. At the very least you could play with the administration. The jabber entry could be put into your network computers hosts files if you have a small computer group or entered into DNS.
---------------------
Almityone
Is there a fix for windows web login to jabberd?
Hi,
I tryed the suggestion about updating the host file or dns file.
I am not able to log still to the web login.
Is there a fix or a work around to get ejabberd to work on a windows 2003 server?
Thanks
acomisp AT yahoo DOT com
Another problem...
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.
Proposed in the bug tracker
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
Problem solved :)
Guyz,
The problem is solved.One of my too dear ppl Marfi got the problem identified and solved it by himself.
After installing ejabberd using the installer exe run the postinstall.bat script from cmd as follows:
postinstall.bat adminusername hostname password
This is to create entry for the admin user in the ejabberd database which was supposed to be created during the installation process.I think this is a bug with installer and hope that the bug'll be removed soon.
Problem solved
Another way is to simply register new "admin" user by any XMPP client.
thanx a lot!!!!
your solution worked for me, thanks!!!
Great Information
HI,
I am happy that i found the solution in your article after two days googling and many times install/unistall.
could you send us your
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 !
--
Process-one
Mickaël Rémond
I'm having the same problem
I'm having the same problem here on a Windows 2000 server. I'm unable to log in with any username/password combination. I'm trying to install 1.1.1_4 but this is providing its own set of problems (the initial web page can't be found).
I ought to say (and this is meant purely as constructive criticism) this site isn't very newbie friendly. This is my first attempt using - let alone installing - a jabber system and, although this seems to be the simplest daemon I could find, the language of this site and the documentation seems to require a certain level of understanding of the jabber protocol that I simply don't have. For example, I could not work out how to log into the chat room to ask for help using gaim and I can't find any instructions on the website for how to do so either.
A getting started guide would go a long way to easing my frustration right now. :)
newbie
I ought to say (and this is meant purely as constructive criticism) this site isn't very newbie friendly. This is my first attempt using - let alone installing - a jabber system and, although this seems to be the simplest daemon I could find, the language of this site and the documentation seems to require a certain level of understanding of the jabber protocol that I simply don't have.
I have on my long-term TODO list the creation of a Glossary section for the ejabberd guide. Maybe you can help me by telling which terms I should explain in it?
For example, I could not work out how to log into the chat room to ask for help using gaim and I can't find any instructions on the website for how to do so either.
A getting started guide would go a long way to easing my frustration right now. :)
There existssuch newbie information on jabber.org , although, when your web browser and your Jabber IM client supports XMPP uris, you just would be able to click on the link to open the chatroom in your client; we will be grateful if you can blame so hard to your web browser creator and your IM client creator, that they add support for this; life will be much easier. Besides that, you remind me of something else I had in mind: a web interface to the chatroom. (@Badlop: what about installing MUCkl?).
More examples of newbie problems are welcome.
--
sander
That link to jabber.org/user
That link to jabber.org/user was invaluable. Thanks very much. After reading that I worked out how to join the ejabberd room using gaim. I posted a howto in the comments.
Hello, Regarding the Windows
Hello,
Regarding the Windows XP problem with Erlang, you might be interested by this post:
Erlang Networking fixed on Windows XP/2003
Best regards,
--
Process-one
Mickaël Rémond
I think that is about windows environment
>ejabberd 2.0.0 RC1
>windows 20003 Server
I've tried at least 4 computers, the same os windows 2003 Server. But I can't access the web admin interface only on one os. Though I can use it in an available computer, I want to know why.
1>the user name and password have no problem.
2>though when I log on the web admin interface, it return "401 Unauthorized",I can log on with the user admin by Pidgin client. But I can't catch abundant operations that the ejabberd server has grantted the user admin(e.g. send announcement to all online user).
3>I also can register new user by it, and chat with the user admin.
4>I checked the winsock. It is available.
5>I've installed and uninstalled several times,still the bad result.
By analyse above phenomena, I think that is about the windows environment.But I can't know what is wrong with that OS.Could someone tell me why?Thanks a lot.
Sorry for my poor english.
username in webadmin -
username in webadmin - "admin@you-domain.tld" , not "admin"
yes
Yes,I put it correctly like "admin@mydomainname", and the password is alos correct. But still "401 Unauthorized":(
Check if the installer granted admin privileges
There can be three different problems:
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?
Thanks for your attention
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 user has admin rights
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:
Yes, it has
I am sorry that I didn't describe clearly.
In the ejabberd.cfg,the line you indicated exists and the information is right.
same same same
I think everyone running 2.0.0-rc1 on Windows has the same problem
Settled
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.
Which version are you using
Which version are you using ?
I cannot reproduce your problem here in version 2.0rc1
--
Process-one
Mickaël Rémond
As Badlop Said
e.g.
"testserver" --> "TestServer"
Ok, problem tracked
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
Waiting for the release version
I've read the problem's detail. Thanks:)