ejabberd - Comments for "invalid dialback key to gmail.com after restart"

This happened to me again.

jason — Thu, 07 Sep 2017 21:38:51 +0000

This happened to me again. Adding mod_s2s_dialback to the modules list in ejabberd.yml seems to have fixed the problem.

I don't have Google Apps

jfranklin — Sat, 10 Sep 2016 17:30:30 +0000

I don't have Google Apps enabled on the domain, and I'm still, 10 day on now, unable to federate with Google.

In case you're still

bloke — Thu, 08 Sep 2016 08:14:43 +0000

In case you're still experiencing intermittent "invalid dialback key" errors and have Google Apps enabled for your domain with ejabberd — disable it.

I've been using ejabberd like that for years but for some reason on 1 Sep dialback errors appeared. Tried a lot of things without luck until eventually I disabled Google Apps and that seems to helped.

I have had the problem since

jfranklin — Fri, 02 Sep 2016 23:04:06 +0000

I have had the problem since late in the evening on August 31st. I've verified my SRV records, I've verified the SSL certs are all current and properly chained, and I'm able to connect still to other jabber servers. Only Google is offline.

@jason, your Gmail contacts coming back online gives me hope, but I don't see it on my server yet.

My gmail contacts are

jason — Fri, 02 Sep 2016 18:18:05 +0000

My gmail contacts are starting to come on line so the problem appears to have fixed itself.

I would still like to know how to fix this when it happens, why it happened, and maybe how to prevent it.

Started happening for me on

skylark — Fri, 02 Sep 2016 13:42:15 +0000

Started happening for me on the night from August 31st to September 1st. Checked my SRV records but that didn't seem to help.

I have exactly the same

bloke — Fri, 02 Sep 2016 06:26:00 +0000

I have exactly the same problem starting yesterday. The s2s certificate is not expired and is valid. Any advice?