Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For the purposes of this post, the root domain

I have an XMPP Server (ejabberd) running on Debian 6.

In Clients (Pidgin, Adium) when I try to add a gtalk xmpp account as a Contact, I get "Not Authorized" messages, along with 404 and 503 error (debugging output below).

While this would suggest a misconfiguration of ejabberd, if I configure the XMPP server to host, adding a gtalk user works just fine. Same is true if the XMPP server hosts

Perhaps this is a DNS issue? Well, I've looked at DNS, hosts files, and I've either verified that they are correct. But I've removed them and replaced them just in case.

Server build? I've rebuilt it from scratch. Same problem. Network? I've tried it on a different network.

I've run out of ideas.

Can gtalk blacklist servers? By mistake?

If you have any ideas, they'd be appreciated.

XMPP Console output from Pidgin client with '' when trying to add user '':

<iq type='result' to='' id='2188721256'/>
<iq type='set' id='purplec8d28432'>
    <query xmlns='jabber:iq:roster'>
        <item jid='' name=''>
<presence to='' type='subscribe'/>
<iq from='' to='' id='push524344776' type='set'>
    <query xmlns='jabber:iq:roster'>
        <item subscription='none' jid=''>
<iq type='result' id='push524344776'/>
<iq from='' to='' id='purplec8d28432' type='result'/>
<iq from='' to='' id='push1181680121' type='set'>
    <query xmlns='jabber:iq:roster'>
        <item ask='subscribe' subscription='none' jid=''>
<iq type='result' id='push1181680121'/>
<presence from='' to='' type='error'>
    <error code='404' type='cancel'>
        <remote-server-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
share|improve this question
It's likely we're going to need to either look at your configuration files and your DNS record setup to help you with this. – Scrivener Feb 3 '13 at 19:24

Resolved. The problem was gtalk's internal DNS.

Turns out a predecessor opened a (free) Google Apps account for the domain 6 years ago, stopped using it 5 years ago, never told anyone and probably forgot about it themselves.

This mean that when tried to chat with, the internal records showed was using the gtalk service, not the ejabberd service I setup. There would then be no response, no authorization.

What was most vexing about this problem is that all the NS records I could find showed that I had set things up correctly, including dig srv @

Anyway, once I discovered the account, I turned down the gtalk service and now everything works.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.