What steps will reproduce the problem?
Look at logs
What is the expected output?
net.connect warn Failed connection, but unexpected!
What do you see instead?
Some hint of _what_ it was that was unexpected. Even with debug logs, on a busy server it is difficult to determine what this relates to.
What version of the product are you using? On what operating system?
Prosody trunk nightly build 1638 (2022-03-24, cf922f34e264)
on Debian 11
Please provide any additional information below.
the log message was introduced with net.connect in
https://hg.prosody.im/trunk/rev/601681acea73
Zash
on
Quite possibly related to happy eyeballs, i.e. when the connection that loses the race is closed?
What steps will reproduce the problem? Look at logs What is the expected output? net.connect warn Failed connection, but unexpected! What do you see instead? Some hint of _what_ it was that was unexpected. Even with debug logs, on a busy server it is difficult to determine what this relates to. What version of the product are you using? On what operating system? Prosody trunk nightly build 1638 (2022-03-24, cf922f34e264) on Debian 11 Please provide any additional information below. the log message was introduced with net.connect in https://hg.prosody.im/trunk/rev/601681acea73
Quite possibly related to happy eyeballs, i.e. when the connection that loses the race is closed?