Hi Cyril, Thanks for the report. Can you please bump your log level up to 'debug' (there should be comments in your config file explaining how to do this), and include those logs? The 'info' level logs tend to give a high-level approximate view of issues, but only the debug logs can be relied upon when debugging the low-level individual connection attempts.
Thanks! On 31 August 2016 at 22:16, Cyril Brulebois <k...@debian.org> wrote: > Package: prosody > Version: 0.9.7-2+deb8u3 > Severity: normal > > Hi, > > My server is trying to initiate a connection to crans.org, which has the > following DNS bits set up: > | _xmpp-server._tcp.crans.org. 466 IN SRV 5 0 5269 xmpp.crans.org. > | > | xmpp.crans.org. 466 IN A 138.231.136.66 > | xmpp.crans.org. 466 IN AAAA > 2a01:240:fe3d:4:200:42ff:fe42:4204 > > Logs say: > | Aug 31 23:02:18 s2soute11b40 info Beginning new connection attempt to > crans.org ([2a01:240:fe3d:4:200:42ff:fe42:4204]:5269) > | Aug 31 23:02:18 s2soute11b40 info Out of connection options, can't > connect to crans.org > | Aug 31 23:02:18 s2soute11b40 info Sending error replies for 1 queued > stanzas because of failed outgoing connection to crans.org > > which is fair enough because: > - trying IPv6 first is the right thing to do; > - this port appears closed on IPv6 at the time of writing. > > But prosody should move to trying a connection on IPv4 instead of simply > giving up and trying again a moment later. > > Thanks for your time. > > > KiBi.
