Failed to start SCTP: DTLS not established

[guillemcordoba]

This may not be a bug in this library, but I often get these warnings when trying to communicate between a node running in my laptop and one running on my phone, and seems like no communication can happen between them, breaking all holochain behavior with timeouts:

[2024-01-09][20:05:34][tx5_go_pion_sys][WARN] Failed to ping without candidate pairs. Connection is not possible yet.
[2024-01-09][20:05:34][tx5_go_pion_sys][WARN] Failed to ping without candidate pairs. Connection is not possible yet.
[2024-01-09][20:05:34][tx5_go_pion_sys][WARN] Failed to ping without candidate pairs. Connection is not possible yet.
[2024-01-09][20:06:04][tx5_go_pion_sys][WARN] Failed to read from candidate udp4 relay 137.184.154.88:58075 related 0.0.0.0:49929: read udp 137.184.154.88:58075: use of closed network connection
[2024-01-09][20:06:04][tx5_go_pion_sys][WARN] Failed to start manager: connecting canceled by caller
[2024-01-09][20:06:04][tx5_go_pion_sys][WARN] Failed to start SCTP: DTLS not established
[2024-01-09][20:06:04][tx5_go_pion_sys][WARN] undeclaredMediaProcessor failed to open SrtcpSession: the DTLS transport has not started yet
[2024-01-09][20:06:04][tx5_go_pion_sys][WARN] undeclaredMediaProcessor failed to open SrtpSession: the DTLS transport has not started yet
[2024-01-09][20:06:05][tx5_go_pion_sys][WARN] Failed to ping without candidate pairs. Connection is not possible yet.
[2024-01-09][20:06:05][tx5_go_pion_sys][WARN] Failed to ping without candidate pairs. Connection is not possible yet.
[2024-01-09][20:06:35][tx5_go_pion_sys][WARN] Failed to read from candidate udp4 relay 137.184.154.88:65117 related 0.0.0.0:39648: read udp 137.184.154.88:65117: use of closed network connection
[2024-01-09][20:06:35][tx5_go_pion_sys][WARN] Failed to start manager: connecting canceled by caller
[2024-01-09][20:06:35][tx5_go_pion_sys][WARN] Failed to start SCTP: DTLS not established
[2024-01-09][20:06:35][tx5_go_pion_sys][WARN] undeclaredMediaProcessor failed to open SrtcpSession: the DTLS transport has not started yet
[2024-01-09][20:06:35][tx5_go_pion_sys][WARN] undeclaredMediaProcessor failed to open SrtpSession: the DTLS transport has not started yet
[2024-01-09][20:07:02][tx5_go_pion_sys][WARN] Failed to ping without candidate pairs. Connection is not possible yet.
[2024-01-09][20:07:02][tx5_go_pion_sys][WARN] Failed to ping without candidate pairs. Connection is not possible yet.
[2024-01-09][20:07:02][tx5_go_pion_sys][WARN] Failed to ping without candidate pairs. Connection is not possible yet.
[2024-01-09][20:08:02][tx5_go_pion_sys][WARN] Failed to accept RTP stream is already closed
[2024-01-09][20:08:02][tx5_go_pion_sys][WARN] Failed to accept RTCP stream is already closed
[2024-01-09][20:08:02][tx5_go_pion_sys][WARN] Failed to read from candidate udp4 relay 137.184.154.88:64366 related 0.0.0.0:44440: read udp 137.184.154.88:64366: use of closed network connection

Any pointers on what to do @neonphog ? Would #77 have something to do with this?

[neonphog]

I did identify some race conditions especially with slower nodes that hopefully will be addressed with #77 - connecting canceled by caller seems rather explicit, though still perhaps could have been caused by a race condition?

[guillemcordoba]

Oh okey cool! I'm hoping to release my mobile app in a couple of days... What would the status be on #77? Is it semi working already?

[neonphog]

It is notionally functional, with some rough edges, such as no automatic connection cleanup. I'm still working some CI issues and have more unit tests to write. Also, it is going to require some holochain integration changes, and will be a breaking protocol difference.

[neonphog]

@guillemcordoba - Okay, between the state changes in #77 and the TURN server side fixes applied as indicated by the turn_doctor, hopefully we shouldn't see as much of this. Note that it is only on develop (0.3).

[guillemcordoba]

@neonphog thanks for all the work! I'll close this for now and reopen this issue if I see the error again.