сертификат протух 11 декабря. Tls negotiation failed. @Voker57 чини

RECOVERY: OK. RTT to bitcheese.net: 618 ms

PROBLEM: (Service Check Timed Out)

RECOVERY: ERROR

RECOVERY: OK. RTT to bitcheese.net: 115 ms

PROBLEM: CRITICAL. No response from bitcheese.net in 10s.

RECOVERY: OK. RTT to bitcheese.net: 465 ms

PROBLEM: CRITICAL. bitcheese.net returned: iq id=033ecafe-358a-47c1-a621-0ff989a44cc4-4 to=s2scheck@blasux.ru/39443181301431185387438181 from=bitcheese.net xml:lang=en type=errorping xmlns=urn:xmpp:ping /error code=404 type=cancelremote-server-not-found xmlns=urn:ietf:params:xml:ns:xmpp-stanzas //error/iq

RECOVERY: OK. RTT to bitcheese.net: 64 ms

PROBLEM: CRITICAL. bitcheese.net returned: iq id=69670de4-9c1b-4db9-bcc3-244a25194ad2-4 to=s2scheck@blasux.ru/33993432181427564387845140 from=bitcheese.net xml:lang=en type=errorping xmlns=urn:xmpp:ping /error code=404 type=cancelremote-server-not-found xmlns=urn:ietf:params:xml:ns:xmpp-stanzas //error/iq

RECOVERY: OK. RTT to bitcheese.net: 866 ms

PROBLEM: CRITICAL. No response from bitcheese.net in 10s.

RECOVERY: OK. RTT to bitcheese.net: 770 ms

PROBLEM: CRITICAL. No response from bitcheese.net in 10s.

RECOVERY: OK. RTT to bitcheese.net: 917 ms

PROBLEM: CRITICAL. No response from bitcheese.net in 10s.

RECOVERY: OK. RTT to bitcheese.net: 716 ms

Кто там у нас ворочает bitcheese? Хуйните inet6 в s2s-listener (вот так: https://www.ejabberd.im/node/1138 ) А то ежаберда настолько говно, что фейлит s2s если у собеседника есть AAAA-запись, но он не слушает на v6 (у bitcheese AAAA есть, но слушает оно только v4)

PROBLEM: CRITICAL. No response from bitcheese.net in 10s.