Home » Forums » ejabberd & XMPP » ejabberd Administration

ejabberd on Ubuntu Intrepid- Connection problems

Submitted by rupin.chheda on Fri, 2009-07-17 02:45

Hi,
I have been successfully able to install ejabberd, I know this for a fact that I can login to the admin console using the browser.
The problem arises when I try to connect to the server using a chat client like Pidgin or Empathy, which returns me an error like this

Invalid XML

I tried this
# netstat -nl | grep 5222
I got
tcp 0 0 0.0.0.0:5222 0.0.0.0:* LISTEN

I did
#telnet localhost 5222

I recieved

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
hello
<stream:error>Invalid XML</stream:error>Connection closed by foreign host.

Can anyone point out to me what could be wrong here in my configuration, that although the webinterface is functional, I am unable to login to the server using a chat client.

I tried tkabber as well,

It said

Authentication Failed :Request Error(Not acceptable) Server haven't provided SASL authentication feature.
I am also unsure if my config is really correct enough so that ejabberd can accept connections from chat clients.

Any help would be greatly appreciated.
Thanks,
Rupin

‹ Clustering ejabberd with mnesia db on solaris fails Multiple DNS domain configuration file troubles ›

It is strange that you et

Submitted by mfoss on Wed, 2009-07-22 22:20.

It is strange that you get "Invalid XML". I get this using ejabberd trunk svn:

$ telnet localhost 5222
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
hello
<?xml version='1.0'?>
<stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' 
id='none' from='localhost' version='1.0'>
<stream:error><xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
</stream:error>
</stream:stream>Connection closed by foreign host.

In fact, in ejabberd 2.0.1 source code I don't find any mention of "Invalid XML". Neither in the patch that ubuntu applies to generate their package.

Take a look at ejabberd.log and sasl.log, maybe they show some error message.

Regarding configuration: the default config of ejabberd, also in Debian and Ubuntu has port 5222 connections working correctly, so it is unlikely that the problem is related to configuration issue.

If noidea what is he problem, you can try to reinstall thepackge from scratch. Keep the default config, create dummy account "test@localhost" and try to login.

If that fails too, maybe the problem is in the package. In that case you can try to install ejabberd from source code.

»
Syndicate content

User login