[XMPP] - s2s directtls failed #427

New Issue

Closed

opened 2023-02-07 20:11:10 +01:00 by muppeth · 5 comments

muppeth commented

2023-02-07 20:11:10 +01:00

Owner

We seem to be failing directtls with server2server connections:
https://connect.xmpp.net/

We seem to be failing directtls with server2server connections: https://connect.xmpp.net/

muppeth added this to the 23.02 - February milestone 2023-02-07 20:11:10 +01:00

muppeth added the

xmpp

label 2023-02-07 20:11:10 +01:00

muppeth commented

2023-02-07 20:11:24 +01:00

Author

Owner

This could be related to #426

meaz commented

2023-02-09 16:58:59 +01:00

Owner

could it be because s2s_direct_tls_ports is set to 5269 whereas it is already s2s default? See https://prosody.im/doc/dns

See also list of ports https://prosody.im/doc/configure

could it be because `s2s_direct_tls_ports` is set to `5269` whereas it is already `s2s` default? See https://prosody.im/doc/dns See also list of ports https://prosody.im/doc/configure

muppeth added this to the 23.02 - February project 2023-02-15 22:47:11 +01:00

muppeth commented

2023-02-16 07:23:19 +01:00

Author

Owner

Yes thos could be he reason. I have been testing it around. I will update host_vars and make PR. We should schedule it to run during upcoming deployment, because changes to DNS and firewall need to be done at the same time too.
Also good moment to test how server will react to restart :)

Yes thos could be he reason. I have been testing it around. I will update host_vars and make PR. We should schedule it to run during upcoming deployment, because changes to DNS and firewall need to be done at the same time too. Also good moment to test how server will react to restart :)

muppeth commented

2023-02-16 07:25:49 +01:00

Author

Owner

Yes I can confirm it to be fixed on bot.disroot.org so this should be an easy fix as well.