mod_s2s_bidi: interoperability issue with prosody

[Menelmacar]

Environment

• On my side prosody trunk 25-04-03, debian stable
• ejabberd version: 2504
• OS: Linux (Debian)

Bug description

I get a connection abort if my server is the one connecting to ejabberd if they have s2s_bidi enabled.

I can't connect to ejabberd servers running Version 2504 if they have enabled mod_s2s_bidi.

I've tested this with two different ejabberd servers. One of the is magicbroccoli.de (they disabled bidi for our debugging, and now connection works again with them)

So I tested with another ejabberd2504 I found in the wild, with max verbose debug logs on my side. I didn't ask them for consent, so I hide their address in my log. Here is the full attempt from my side: https://stuff.snikket.de/bidi-error.log

Updates: The issue goes away after a server ejabberd on ejabberd or (maybe?) if the bidi module is reloaded. Currently I only found few ejabberd servers on this version with bidi that had the issue.

[Menelmacar]

Maybe @mightyBroccoli or someone else could provide debug logs from the ejabberd side. I can ping everyone with my server, trying to establish a connection to trigger it.

[Zoidberg2]

We tested this with my server(Menel and Me) and the connection was successful. ejabberd 25.04.

[Menelmacar]

So far 2 of 7 ejabberd servers I could test with show the issue with mine. and I tested with a complete fresh minimal install of prosody 0.12.3 so I think all versions of prosody up to trunk show the issue with ejabberds bidi currently.

It seems a reload of the module, or a restart of the server fixes the issue. And it is unclear under what condition it reappears while running. If I ever can get hold onto ejabberd logs I'll update. Everyone that want, can test it easily whith deploying any prosody version with bidi, and doing an xmpp ping to a ejabberd server with bidi enabled, that isn't connected already from the ejabberd side.