Hi,
I have seen various posts on here about dialback issues, but have not found a solution to my problem amongst them.
I have an ejabberd server set up with no SRV entries (the default DNS entry should resolve fine). Telnet to port 5269 works ok.
I can connect to google users and users of other homehosted xmpp servers, but i cannot connect to jabber.org accounts. The log shows the usual:
@ejabberd_s2s_out:wait_for_validation:417 Closing s2s connection:
myserver.dom -> jabber.org (invalid dialback key)
On the machine the server is located, i opened up erl and looked for jabber's SRV:
2> inet_res:getbyname("_xmpp-server._tcp.jabber.org", srv, 1000).
{ok,{hostent,"_xmpp-server._tcp.jabber.org",[],srv,2,
[{30,30,5269,"hermes2.jabber.org"},
{31,30,5269,"hermes2v6.jabber.org"}]}}
And verified that my own server does not have an SRV:
3> inet_res:getbyname("_xmpp-server._tcp.myserver.dom", srv, 1000).
{error,nxdomain}
So now i'm at somewhat of a loss. Any help would be appreciated.
Thanks.
Ok, fixed it! Back in May,
Ok, fixed it!
Back in May, jabber.org starteddisallowing non tls-ed connections . Turns out my server was not quite set up correctly to do tls.
I set in /etc/ejabberd/ejabberd.yml
s2s_use_starttls: true
s2s_certfile: "<path to cert file>"
and things were on their way. The value of "true" is not a valid value according to the comments in the config file, but it seems to have the effect of connecting with tls when possible and falling back to unencrypted when not.