resolved!

MavEtJu — Thu, 17 Nov 2005 05:23:29 +0000

Resolved!

I had the SRV records pointing to 5222 instead of 5269.
*dumb*

With the move of jabberd to

mfoss — Wed, 02 Nov 2005 09:40:17 +0000

With the move of jabberd to ejabberd I access to about half of my non-local contacts.

Can you determine if the contacts you are 'missing' are on specific servers? What servers are those that you can't connect to?

The problem can have several reasons:

ejabberd has a newly discovered bug (rare)
your installation of ejabberd is faulty (maybe it's a DNS SRV issue, it can be fixed easily)
other Jabber server has bugs (rare)
other Jabber server installation is faulty (very rare)
the connection between your server and other specific server has 'hanged', for some unknown reason (rare, but possible)

How to check if your Jabber server can connect to other specific server?

Login to an account on your server.
Open the 'Service Discovery', 'Jabber Explorer', or whatever it is called (in Psi, Gajim, Tkabber, Exodus...)
You will see your local server. Now type in the address bar the name of other Jabber server: jabber.org
You should be presented with information from that other server. If you don't receive any information, then your server couldn't contact the other server.
Now try to 'discover' those servers: jabber.ru jabberes.org jabber.com im.gentoo.org xmpp.org amessage.de
Comment here which ones were you able to connect to and which ones you couldn't.

About the network messages you captured, are you sure all those messages are from the same 'conversation'? Message-1 is xmlns=jabber:server, but for some reason ejabberd answers in Message-2 with xmlns=jabber:client.

Did you change the configuration of listening ports on ejabberd.cfg?

And finally, what version of ejabberd (0.9.1, 0.9.8, svn...), and how did you install it (source, debian/apt, freebsd/ports, linux/installer, windows/installer...)?

ejabberd - Comments for "XML Namespace issues?"

resolved!

With the move of jabberd to