STUN and TURN stuff is just a wild guess on the part of browser. You don’t need to pay any particular attention to it. Concentrate on the fact that ICE failed, period. Mediasoup supports ICE-lite: it takes the connections on a publicly announced address and serves as a STUN server itself. Make sure that the clients can connect to it on the supposedly open ports. Look at the browser webrtc internals: do logs show that the browser received any response from the mediasoup server? If not or unclear, bind some simple UDP (or/and TCP) tester like netcat to one of the open ports on the server and make sure that you can reach it from the client computer. Providing this works, mediasoup server should answer ICE binding requests and send back client’s public address that it sees. Look at the ICE candidates: is there any familiar public address, and what happens when the browser pairs it to mediasoup’s own candidates and tries to connect.