Could not start connectivity check

Install & Config
1

Hello,
I have jitsi configured on k8s AWS and I’m constantly seeing in JVB logs

Could not start connectivity check: No socket found for 10.10.2.7:30300/udp->xxx.xxx.xx.xxx:58671/udp

Is the private address of the pod here normal? Shouldn’t it be the public ip that’s discovered through the AWS harvester?

2

This is fine, what version of the JVB are you running? IIRC that error got resolved a few releases ago.

3

We’re using stable-7882.
Weird thing about this, iOS will figure out ICE, but Android won’t, there does not seem to be much difference in the logs/data they both are sending.
Also worth noting that we are on newest lib-jitsi-meet, running React Native

4

What logs do you see on the client?

5

Not much:

 DEBUG  2022-10-31T10:40:21.450Z [modules/RTC/BridgeChannel.js] <anonymous>:  Dominant speaker: e886f113, previous speakers:
 INFO  2022-10-31T10:40:34.967Z [modules/RTC/BridgeChannel.js] <anonymous>:  Endpoint connection status changed: f448f667 active=false
 DEBUG  2022-10-31T10:40:35.978Z [modules/RTC/TraceablePeerConnection.js] <anonymous>:  oniceconnectionstatechange failed
 LOG  2022-10-31T10:40:35.981Z [modules/xmpp/JingleSessionPC.js] <anonymous>:  (TIME) ICE failed JVB:	 1667212835980
 DEBUG  2022-10-31T10:40:36.016Z [modules/RTC/TraceablePeerConnection.js] <anonymous>:  onconnectionstatechange failed
 INFO  2022-10-31T10:40:38.086Z [modules/connectivity/IceFailedHandling.js] <_actOnIceFailed>:  ICE failed, enableForcedReload: undefined, enableIceRestart: true, supports restart by terminate: true
 INFO  2022-10-31T10:40:38.089Z [modules/connectivity/IceFailedHandling.js] <_actOnIceFailed>:  Sending ICE failed - the connection did not recover, ICE state: failed, use 'session-terminate': false```

I've looked into it more and it seems like it does not work only on Android wifi, but does on LTE.
One more interesting thing is when it does connect, I always see 'rel-addr' on jvb starting with 10.x.x.x, but when it does not it starts with '192.x.x.x' .
6

We’ve solved the issue by using host network and opening up ips and firewalls.
Interesting to note that if we hotspoted from Android it would not work but if it was a hotspot from iOS it would always connect, no matter if client Android or iOS, so there are some differences how network is resolved regarding the OS.