I recently updated my dev environment to the latest unstable (2.0.5953-1) and the CoTurn is no longer working. I am using a separate CoTurn server. The CoTurn server still works for another Jitsi implementation so I know it still works. I am not seeing any errors in prosody or the TURN server but the client is showing its unable to connect to wss:// on the videobridge. This only happens when I block port 10000 forcing the client to use the TURN Server.
In the JVB logs it appears it is sending/connecting to itself at 169.254.84.132 instead of the IP address of the TURN server. Testing on another server running Stable that is setup the same and using the same TURN server, it is sending the media to the TURN server’s IP not a loopback.
JVB 2021-07-08 19:01:57.004 INFO:  [confId=6542dcd7a06b319f gid=103680 stats_id=Angel-Ltn componentId=1 firstname.lastname@example.org ufrag=463ij1fa3nuufa name=stream-087b7219 epId=087b7219 local_ufrag=463ij1fa3nuufa] Component.addUpdateRemoteCandidates#347: Update remote candidate for stream-087b7219.RTP: 169.254.84.132:59332/udp