Firefox cannot use external TURN server with latest stable 2.0.6173-1

I’m updating from jitsi 2.0.4627-1 (from last year) to the the latest stable 2.0.6173-1. I use a separate JVB an also my own external STUN/TURN server. With UDP blocked, when I join the conference from Chrome, I can see that the TURN server is working (and wireshark show that there is indeed traffic to my TURN)

But with Firefox I don’t see any video or audio stream, and no traffic to the TURN either. But no error in the javascript log either. This was working with 2.0.4627-1.

The ICE stats in about:webrtc are puzzling. With jitsi 2.0.4627-1 I had a straightforward selection:

ICE State Nominated Selected Local Candidate Remote Candidate
succeeded true true <my_turn_IP>:51871/udp(relay-tls) [non-proxied] <JVB_aws_public_IP>:10000/udp(srflx) 1

But now, none of the candidate are selected and somehow the private IP of my AWS JVB is in the candidate too.

ICE State Nominated Selected Local Candidate Remote Candidate

inprogress true false <my_coturn_IP>:54354/udp(relay-tls) [non-proxied] <JVB_aws_private_IP>:10000/udp(host)

succeeded false false <my_coturn_IP>:54354/udp(relay-tls) [non-proxied] <JVB_aws_public_IP>:10000/udp(srflx)

Here is my previous prosody config:

turncredentials_secret = "the_turn_server_secret";
turncredentials = {
  { type = "stun", host = "my-turn-server.com", port = "443" },
  { type = "turn", host = "my-turn-server.com", port = "443", transport = "udp" },
  { type = "turns", host = "my-turn-server.com", port = "443", transport = "tcp" }
};

Updated config:

external_service_secret = "the_turn_server_secret";
external_services = {
  { type = "stun", host = "my-turn-server.com", port = 443 },
  { type = "turn", host = "my-turn-server.com", port = 443, transport = "udp", secret = true, ttl = 86400, algorithm = "turn" },
  { type = "turns", host = "my-turn-server.com", port = 443, transport = "tcp", secret = true, ttl = 86400, algorithm = "turn" }
};

And here is my JVB sip-communicator.properties, basically the same as before, except that I moved the websocket config to jvb.conf

org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true
org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=stun.l.google.com:19302
org.jitsi.videobridge.ENABLE_STATISTICS=true
org.jitsi.videobridge.STATISTICS_TRANSPORT=muc
org.jitsi.videobridge.xmpp.user.shard.HOSTNAME={{ jitsi_meet_server_name }}
org.jitsi.videobridge.xmpp.user.shard.DOMAIN=auth.{{ jitsi_meet_server_name }}
org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb
org.jitsi.videobridge.xmpp.user.shard.PASSWORD={{ jitsi_meet_videobridge_password }}
org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.auth.{{ jitsi_meet_server_name }}
org.jitsi.videobridge.xmpp.user.shard.MUC_NICKNAME=jvb-nickname
org.jitsi.videobridge.xmpp.user.shard.DISABLE_CERTIFICATE_VERIFICATION=true
org.jitsi.videobridge.ENABLE_REST_SHUTDOWN=true
org.jitsi.videobridge.shutdown.ALLOWED_SOURCE_REGEXP=127.0.0.1

Any idea what prevent the ICE negotiation to succeed with Firefox now?

How do you block UDP/10000?

I’m joining the conference from a windows machine, so I’m using the windows defender firewall to block UDP 10000-10010 (going in or out).

1 Like

/etc/prosody/conf.avail/DOMAIN.cfg.lua

is
"external_services";

included in

modules_enabled =

?

oh well, I just learned from your post that in January Jitsi-meet devs decided to deprecate their mod_turncredentials module to replace it with the external_services prosody module (that will be integrated in Prosody only starting with version 12). Thanks for the head-up, Jitsi-meet devs :slight_smile:

Now this begs the question, could there be an incompatibility between Firefox and this new shiny module, since everything is tested with Chrome now ? could be interesting to bring back the old turncredentials module to find out, no ?

Yes, it’s in. Also it’s working with Chrome, so my prosody config is probably ok.

And watch out for the freaking evil change in the port attribute, with turncredentials you need quote like this port = “443” , but with external_services it’s mandatory to have no quote port = 443, otherwise it fails silently. Lost an entire day because of that :cry:

Good idea thanks, I will try.

The new modules does work for me with Firefox. So I think it is not a generic issue.

Could you open about:webrtc, press the “clear log” at the bottom of the page, then do a test run and share the “connection log” afterwards?
The “connection log” is basically the logging output of Firefox ICE stack. Hopefully that shows some clues what is going wrong in your case.

Thanks for the tip @drno !!

Just to explain a little bit my setup, I have 3 servers on AWS: meet, JVB and TURN.
So they all have a public ip (ex 35.75…) and private ip (ex 172.30…)

Firefox connection log

Session Statistics
[ 3 | 4294967317 ] https://{{meet_FQDN}}/FD221D 2021-08-20T01:19:29.611Z
show details
Connection Log
hide log
+++++++ BEGIN (process id 12048) ++++++++
(ice/INFO) /builds/worker/checkouts/gecko/dom/media/webrtc/transport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:184 function nr_socket_multi_tcp_create_stun_server_socket skipping STUN with different IP version (6) than local socket (4),
(ice/WARNING) /builds/worker/checkouts/gecko/dom/media/webrtc/transport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:623 function nr_socket_multi_tcp_listen failed with error 3
(ice/WARNING) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): failed to create passive TCP host candidate: 3
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): Skipping TURN server because of address type mis-match
(ice/INFO) /builds/worker/checkouts/gecko/dom/media/webrtc/transport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:184 function nr_socket_multi_tcp_create_stun_server_socket skipping STUN with different IP version (4) than local socket (6),
(ice/WARNING) /builds/worker/checkouts/gecko/dom/media/webrtc/transport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:623 function nr_socket_multi_tcp_listen failed with error 3
(ice/WARNING) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): failed to create passive TCP host candidate: 3
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): Skipping TURN server because of address type mis-match
(ice/INFO) /builds/worker/checkouts/gecko/dom/media/webrtc/transport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:184 function nr_socket_multi_tcp_create_stun_server_socket skipping STUN with different IP version (6) than local socket (4),
(ice/WARNING) /builds/worker/checkouts/gecko/dom/media/webrtc/transport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:623 function nr_socket_multi_tcp_listen failed with error 3
(ice/WARNING) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): failed to create passive TCP host candidate: 3
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): Skipping TURN server because of address type mis-match
(ice/INFO) /builds/worker/checkouts/gecko/dom/media/webrtc/transport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:184 function nr_socket_multi_tcp_create_stun_server_socket skipping STUN with different IP version (6) than local socket (4),
(ice/WARNING) /builds/worker/checkouts/gecko/dom/media/webrtc/transport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:623 function nr_socket_multi_tcp_listen failed with error 3
(ice/WARNING) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): failed to create passive TCP host candidate: 3
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): Skipping TURN server because of address type mis-match
(ice/WARNING) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) has no stream matching stream PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D transport-id=transport_0 - 918c6246:7b4c47dd98b1e1bb64f78a1ca2f7f0cb
(ice/NOTICE) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) no streams with non-empty check lists
(ice/NOTICE) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) no streams with pre-answer requests
(ice/NOTICE) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) no checks to start
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate host(IP4:192.168.20.137:54069/UDP)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(EAw/): setting pair to state FROZEN: EAw/|IP4:192.168.20.137:54069/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:192.168.20.137:54069/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(EAw/): Pairing candidate IP4:192.168.20.137:54069/UDP (7e7c00ff):IP4:{{JVB_AWS_private_ip}}:10000/UDP (7effffff) priority=9114160845369114623 (7e7c00fffdffffff)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/ICE-STREAM(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D transport-id=transport_0 - 918c6246:7b4c47dd98b1e1bb64f78a1ca2f7f0cb): Starting check timer for stream.
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(EAw/): setting pair to state WAITING: EAw/|IP4:192.168.20.137:54069/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:192.168.20.137:54069/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(EAw/): setting pair to state IN_PROGRESS: EAw/|IP4:192.168.20.137:54069/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:192.168.20.137:54069/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/NOTICE) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) is now checking
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(MgEN): setting pair to state FROZEN: MgEN|IP4:192.168.20.137:54069/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:192.168.20.137:54069/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(MgEN): Pairing candidate IP4:192.168.20.137:54069/UDP (7e7c00ff):IP4:{{JVB_AWS_public_ip}}:10000/UDP (64ffffff) priority=7277816997779866110 (64fffffffcf801fe)
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate host(IP6:[240d:1a:8cb:3400:3da1:100e:a043:6c7]:54070/UDP)
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate host(IP4:192.168.1.5:54071/UDP)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(HZA4): setting pair to state FROZEN: HZA4|IP4:192.168.1.5:54071/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:192.168.1.5:54071/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(HZA4): Pairing candidate IP4:192.168.1.5:54071/UDP (7e7d00ff):IP4:{{JVB_AWS_private_ip}}:10000/UDP (7effffff) priority=9114442320345825279 (7e7d00fffdffffff)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(eL4Y): setting pair to state FROZEN: eL4Y|IP4:192.168.1.5:54071/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:192.168.1.5:54071/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(eL4Y): Pairing candidate IP4:192.168.1.5:54071/UDP (7e7d00ff):IP4:{{JVB_AWS_public_ip}}:10000/UDP (64ffffff) priority=7277816997779997182 (64fffffffcfa01fe)
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate host(IP4:172.20.144.1:54072/UDP)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(Ov+X): setting pair to state FROZEN: Ov+X|IP4:172.20.144.1:54072/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:172.20.144.1:54072/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(Ov+X): Pairing candidate IP4:172.20.144.1:54072/UDP (7e7f00ff):IP4:{{JVB_AWS_private_ip}}:10000/UDP (7effffff) priority=9115005270299246591 (7e7f00fffdffffff)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(+aQU): setting pair to state FROZEN: +aQU|IP4:172.20.144.1:54072/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:172.20.144.1:54072/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(+aQU): Pairing candidate IP4:172.20.144.1:54072/UDP (7e7f00ff):IP4:{{JVB_AWS_public_ip}}:10000/UDP (64ffffff) priority=7277816997780259326 (64fffffffcfe01fe)
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate host(IP4:192.168.20.137:57564/TCP) active
(generic/INFO) Write buffer not empty for IP4:0.0.0.0:443/TLS 44 - already armed (@2ae941d67e4), not connected
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate host(IP6:[240d:1a:8cb:3400:3da1:100e:a043:6c7]:63912/TCP) active
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate host(IP4:192.168.1.5:51148/TCP) active
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate host(IP4:172.20.144.1:54362/TCP) active
(generic/INFO) Write buffer not empty for IP6:[::]:443/TLS 44 - already armed (@2ae941d6de4), not connected
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(Ov+X): setting pair to state WAITING: Ov+X|IP4:172.20.144.1:54072/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:172.20.144.1:54072/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(Ov+X): setting pair to state IN_PROGRESS: Ov+X|IP4:172.20.144.1:54072/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:172.20.144.1:54072/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(generic/INFO) Write buffer not empty for IP4:0.0.0.0:443/TLS 44 - already armed (@2ae941d73e4), not connected
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(HZA4): setting pair to state WAITING: HZA4|IP4:192.168.1.5:54071/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:192.168.1.5:54071/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(HZA4): setting pair to state IN_PROGRESS: HZA4|IP4:192.168.1.5:54071/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(host(IP4:192.168.1.5:54071/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(generic/INFO) Invoking writable_cb on connected (44)
(generic/INFO) Writable_cb IP4:0.0.0.0:443/TLS (0 (2ae941d67e4) pending)
(generic/INFO) Invoking writable_cb on connected (44)
(generic/INFO) Writable_cb IP6:[::]:443/TLS (0 (2ae941d6de4) pending)
(generic/INFO) Invoking writable_cb on connected (44)
(generic/INFO) Writable_cb IP4:0.0.0.0:443/TLS (0 (2ae941d73e4) pending)
(generic/ERR) NrTcpSocket::OnClose 2ae941d6000 reason=2152398861 name=NS_ERROR_CONNECTION_REFUSED
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): Error 10 on reliable socket(2ae941d6000). Abandoning.
(turn/WARNING) TURN(relay(IP4:192.168.20.137:0/TLS|IP4:0.0.0.0:443/TLS)) failed
(turn/INFO) TURN(relay(IP4:192.168.20.137:0/TLS|IP4:0.0.0.0:443/TLS)): cancelling
(turn/WARNING) ICE-CANDIDATE(relay(IP4:192.168.20.137:0/TLS|IP4:0.0.0.0:443/TLS)): nr_turn_allocated_cb called with state 4
(turn/WARNING) ICE-CANDIDATE(relay(IP4:192.168.20.137:0/TLS|IP4:0.0.0.0:443/TLS)): nr_turn_allocated_cb failed
(ice/WARNING) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND(relay(IP4:192.168.20.137:0/TLS|IP4:0.0.0.0:443/TLS)): failed to initialize, 3 remaining
(generic/ERR) NrTcpSocket::OnClose 2ae941d6800 reason=2152398878 name=NS_ERROR_UNKNOWN_HOST
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): Error 10 on reliable socket(2ae941d6800). Abandoning.
(turn/WARNING) TURN(relay(IP6:[240d:1a:8cb:3400:3da1:100e:a043:6c7]:0/TLS|IP6:[::]:443/TLS)) failed
(turn/INFO) TURN(relay(IP6:[240d:1a:8cb:3400:3da1:100e:a043:6c7]:0/TLS|IP6:[::]:443/TLS)): cancelling
(turn/WARNING) ICE-CANDIDATE(relay(IP6:[240d:1a:8cb:3400:3da1:100e:a043:6c7]:0/TLS|IP6:[::]:443/TLS)): nr_turn_allocated_cb called with state 4
(turn/WARNING) ICE-CANDIDATE(relay(IP6:[240d:1a:8cb:3400:3da1:100e:a043:6c7]:0/TLS|IP6:[::]:443/TLS)): nr_turn_allocated_cb failed
(ice/WARNING) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND(relay(IP6:[240d:1a:8cb:3400:3da1:100e:a043:6c7]:0/TLS|IP6:[::]:443/TLS)): failed to initialize, 2 remaining
(generic/ERR) NrTcpSocket::OnClose 2ae941d7400 reason=2152398861 name=NS_ERROR_CONNECTION_REFUSED
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): Error 10 on reliable socket(2ae941d7400). Abandoning.
(turn/WARNING) TURN(relay(IP4:172.20.144.1:0/TLS|IP4:0.0.0.0:443/TLS)) failed
(turn/INFO) TURN(relay(IP4:172.20.144.1:0/TLS|IP4:0.0.0.0:443/TLS)): cancelling
(turn/WARNING) ICE-CANDIDATE(relay(IP4:172.20.144.1:0/TLS|IP4:0.0.0.0:443/TLS)): nr_turn_allocated_cb called with state 4
(turn/WARNING) ICE-CANDIDATE(relay(IP4:172.20.144.1:0/TLS|IP4:0.0.0.0:443/TLS)): nr_turn_allocated_cb failed
(ice/WARNING) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND(relay(IP4:172.20.144.1:0/TLS|IP4:0.0.0.0:443/TLS)): failed to initialize, 1 remaining
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(+aQU): setting pair to state WAITING: +aQU|IP4:172.20.144.1:54072/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:172.20.144.1:54072/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(+aQU): setting pair to state IN_PROGRESS: +aQU|IP4:172.20.144.1:54072/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:172.20.144.1:54072/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(stun/INFO) STUN-CLIENT(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)::TURN): Received response; processing
(stun/WARNING) STUN-CLIENT(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)::TURN): nr_stun_process_error_response failed
(stun/WARNING) STUN-CLIENT(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)::TURN): Error processing response: Retry may be possible, stun error code 401.
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(eL4Y): setting pair to state WAITING: eL4Y|IP4:192.168.1.5:54071/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:192.168.1.5:54071/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(eL4Y): setting pair to state IN_PROGRESS: eL4Y|IP4:192.168.1.5:54071/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:192.168.1.5:54071/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(stun/INFO) STUN-CLIENT(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)::TURN): Received response; processing
(turn/INFO) TURN(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)): Succesfully allocated addr IP4:{{my_TURN_AWS_public_ip}}:52929/UDP lifetime=3600
(ice/ERR) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): peer (PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default) pairing local trickle ICE candidate turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): setting pair to state FROZEN: 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(8xT6): Pairing candidate IP4:{{my_TURN_AWS_public_ip}}:52929/UDP (7d1fff):IP4:{{JVB_AWS_private_ip}}:10000/UDP (7effffff) priority=35219556427366399 (7d1ffffdffffff)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(pVg7): setting pair to state FROZEN: pVg7|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(pVg7): Pairing candidate IP4:{{my_TURN_AWS_public_ip}}:52929/UDP (7d1fff):IP4:{{JVB_AWS_public_ip}}:10000/UDP (64ffffff) priority=35219555554951167 (7d1fffc9ffffff)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D): All candidates initialized
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(MgEN): setting pair to state WAITING: MgEN|IP4:192.168.20.137:54069/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:192.168.20.137:54069/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(MgEN): setting pair to state IN_PROGRESS: MgEN|IP4:192.168.20.137:54069/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(host(IP4:192.168.20.137:54069/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): setting pair to state WAITING: 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): setting pair to state IN_PROGRESS: 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(turn/INFO) TURN(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)): Creating permission for IP4:{{JVB_AWS_private_ip}}:10000/UDP
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(pVg7): setting pair to state WAITING: pVg7|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(pVg7): setting pair to state IN_PROGRESS: pVg7|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(turn/INFO) TURN(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)): Creating permission for IP4:{{JVB_AWS_public_ip}}:10000/UDP
(stun/INFO) STUN-CLIENT(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)::TURN): Received response; processing
(stun/INFO) STUN-CLIENT(8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)): Received response; processing
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(2q27): setting pair to state FROZEN: 2q27|IP4:{{my_TURN_AWS_private_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(prflx|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D)/CAND-PAIR(2q27): Pairing candidate IP4:{{my_TURN_AWS_private_ip}}:52929/UDP (6d7d00ff):IP4:{{JVB_AWS_private_ip}}:10000/UDP (7effffff) priority=7889463221701050367 (6d7d00fffdffffff)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): setting pair to state FAILED: 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(2q27): setting pair to state SUCCEEDED: 2q27|IP4:{{my_TURN_AWS_private_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(prflx|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): triggered check on 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): received STUN check on failed pair, resurrecting: 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): setting pair to state WAITING: 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): Inserting pair to trigger check queue: 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(stun/INFO) STUN-CLIENT(relay(IP4:192.168.1.5:0/TLS|IP4:0.0.0.0:443/TLS)::TURN): Received response; processing
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(8xT6): setting pair to state IN_PROGRESS: 8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(stun/INFO) STUN-CLIENT(pVg7|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)): Received response; processing
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(pVg7): setting pair to state SUCCEEDED: pVg7|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)
(stun/INFO) STUN-CLIENT(8xT6|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)): Received response; processing
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(2q27): setting pair to state SUCCEEDED: 2q27|IP4:{{my_TURN_AWS_private_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(prflx|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)
(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default): no FROZEN/WAITING pairs for PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D transport-id=transport_0 - 918c6246:7b4c47dd98b1e1bb64f78a1ca2f7f0cb
+++++++ END (process id 12048) ++++++++

So I can see in this log that three pairs succeed, and yet none of them got selected somehow.

(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(2q27): setting pair to state SUCCEEDED: 2q27|IP4:{{my_TURN_AWS_private_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(prflx|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)

(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(pVg7): setting pair to state SUCCEEDED: pVg7|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP|IP4:{{JVB_AWS_public_ip}}:10000/UDP(turn-relay(IP4:192.168.1.5:0/TLS|IP4:{{my_TURN_AWS_public_ip}}:52929/UDP)|candidate:2 1 udp 1694498815 {{JVB_AWS_public_ip}} 10000 typ srflx raddr {{JVB_AWS_private_ip}} rport 10000 generation 0)

(ice/INFO) ICE-PEER(PC:{9e7cd77a-b729-4f36-bde2-a0d6b31a7d8f} 1629422365434000 (id=4294967317 url=https://{{meet_FQDN}}/FD221D:default)/CAND-PAIR(2q27): setting pair to state SUCCEEDED: 2q27|IP4:{{my_TURN_AWS_private_ip}}:52929/UDP|IP4:{{JVB_AWS_private_ip}}:10000/UDP(prflx|candidate:1 1 udp 2130706431 {{JVB_AWS_private_ip}} 10000 typ host generation 0)

The second one seeps perfectly fine to me, I don’t understand why it’s not selected.

Edit: Also just in case my coturn config

turnserver.conf

use-auth-secret
keep-address-family
static-auth-secret={{ secret }}
realm={{ turn_FQDN }}
cert=/etc/coturn/fullchain.pem
pkey=/etc/coturn/privkey.pem
no-tcp
listening-port=443
tls-listening-port=443
external-ip={{ public_ip }}
no-tlsv1
no-tlsv1_1

trying it with latest unstable and p2p disabled
Firefox port 10000 blocked x Chrome = video works
Firefox port 10000 blocked x Firefox = video don’t work
however by telnetting to port 5766 on the server I can see that Firefox does establish the connection to Turn. Do you use coturn as turn server ? If yes can you enable telnet interface (option cli-password=) and take a look at the coturn status (‘ps’ command) ?
edit: obviously you use coturn, sorry for the inane question.

@arzar is it intentional that you are setting TURNS via TCP in your prosody config, but then you are disabling TCP in your co-turn config?
It results in the browser just wasting time on trying to make TCP connections and getting connection resets as seen in the log.

One possible explanation for Firefox marking candidate pairs as succeeded, but not selecting it could be that Firefox believes that the other side, so JVB, being the ICE controller and therefore waiting for the JVB to select one of the working pairs. From the top of my head I currently don’t recall how its determined which ICE agent is controller and which is controlled.

Didn’t know even know that coturn offer a telnet cli ! Thanks for the information.

With firefox:

 ps

    1) id=001000000000000002, user <1629529976>:
      realm: {{ coturn_FQDN }}
      started 6 secs ago
      expiring in 3594 secs
      client protocol TLS/TCP, relay protocol UDP
      client addr {{ my_pc_ip }}:57285, server addr {{ TURN_AWS_private_ip }}:443
      relay addr {{ TURN_AWS_private_ip }}:50288
      fingerprints enforced: ON
      mobile: OFF
      TLS method: UNKNOWN
      TLS cipher: TLS_AES_256_GCM_SHA384
      usage: rp=9, rb=1092, sp=8, sb=1104
       rate: r=0, s=0, total=0 (bytes per sec)
      peers:
          {{ JVB_AWS_public_ip }}
          {{ JVB_AWS_private_ip }}

  Total sessions: 1

With chrome:

 ps

    1) id=000000000000000002, user <1629529782>:
      realm: {{ coturn_FQDN }}
      started 4 secs ago
      expiring in 596 secs
      client protocol TLS/TCP, relay protocol UDP
      client addr {{ my_pc_ip }}:64817, server addr {{ TURN_AWS_private_ip }}:443
      relay addr {{ TURN_AWS_private_ip }}:53745
      fingerprints enforced: OFF
      mobile: OFF
      TLS method: UNKNOWN
      TLS cipher: TLS_AES_256_GCM_SHA384
      usage: rp=19, rb=2409, sp=34, sb=5092
       rate: r=0, s=0, total=0 (bytes per sec)
      peers:
          {{ JVB_AWS_public_ip }}
          {{ JVB_AWS_public_ip }}:10000
          {{ JVB_AWS_private_ip }}
          {{ JVB_AWS_private_ip }}:10000

  Total sessions: 1

Almost the same, but with Chrome there is a peer JVB_ip:10000 in addition to just JVB_ip

I basically took it from the jitsi turn config file:

But I have to admit it had always confused me… What do no-tcp does exactly?

Edit: Maybe the jitsi conf use no-tcp to force either udp or tcp tls?

what’s strange in your coturn status for chrome is the 0 values for rate; there don’t seem to be data exchanged while you say it works ???
For the record, I have the no-tcp options disabled in my config, but the setup is very different.
Edit: I use the coturn version shipped with Ubuntu 20.04 in vanilla Jitsi install, as you use a separate install you may have a different version; it may be relevant or not.

Ah, sorry about that, I just did the ps right after joining the conference on chrome, so the rate was not computed yet, but if I wait a few seconds, the rate is not zero anymore and data is flowing.

My previous Meet, JVB and TURN were all unbutu 18.04, but when I updated to the latest stable, I actually created brand new server for Meet and JVB with ubuntu 20.04, but didn’t touch the TURN… So now, only my TURN server use ubuntu 18.04 (and coturn itself is version 4.5.0.7)

In 20.04 it’s the 4.5.1.1 version. 16 months of development between the 2 versions.

I tried a TURN server on ubuntu 20.04, so with coturn 4.5.1.1, and it was the same behavior, Chrome Ok, firefox not ok…

Also removing no-tcp or not from the config also doesn’t change the result. Really struggling to understand what is going on now.

You don’t need external-ip line in TURN config

external-ip={{ public_ip }}

Is the TLS certificate of TURN from a trusted CA?

Hmm I don’t remember exactly the circumstances, but last year when I created the turn server it wouldn’t work at all without that line. Because my TURN server is on AWS, I think coturn need to know the public ip somehow. But I will try again without.

It’s a let’s encrypt certificate.

I would recommend to turn on TURN TCP, so remove the ‘no-tcp’ option from your coturn config, because that enables clients which are behind UDP blocking firewalls to connect over TCP in worst case. But this is independent of the problem you are debugging here.

Since Jitsi is the offerer it is also the ICE controller. So the Firefox log suggests that Firefox is able to send binding requests to your JVB and gets responses. But since the JVB is the ICE controller Firefox sits there and waits for the JVB to also send ICE binding requests towards Firefox and tell it which candidate pair should be used for this connection.
Quite possible that JVB not sending binding requests to Firefox is also the reason why your co-turn doesn’t show the port 10000 in your telnet session.

Just as an additional explanation ‘no-tcp’ turns off TCP support on your co-turn server. That means your co-turn server uses UDP only. And as mentioned above if you have clients which are behind UDP blocking firewalls then these clients won’t be able to make connections to your JVB.

No, it doesn’t. I have this option since last year, jitsi has it by default too, and I has always been able to connect to my turn server by tcp TSL 443 even behind a corporate firewall blocking all UDP. I think what no-tcp does is that it turn off the plain tcp listener, but the tls one is still active. Because if I also add no-tls, then my turn is only accessible by udp

This actually worked! :grinning_face_with_smiling_eyes: I could get Chrome and Firefox to get audio and video stream! Now I’m really confused. EC2 instances run behind a NAT, so I thought that option was mandatory, heck even the official doc mentions that external-ip is for Amazon EC2 users…

I can’t shake the feeling that I’m exploiting the fact that my TURN server and my JVB are in the same VPC somehow.