# mediasoup-client:Transport ICE candidate error

**URL:** <https://mediasoup.discourse.group/t/mediasoup-client-transport-ice-candidate-error/6738>\
**Category:** mediasoup libraries\
**Created:** [June 25, 2025, 6:44am UTC](https://mediasoup.discourse.group/t/mediasoup-client-transport-ice-candidate-error/6738 "2025-06-25T06:44:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Astagor](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/astagor/32/2515_2.png) [@Astagor](https://mediasoup.discourse.group/u/Astagor)\
**Post date:** [June 25, 2025, 6:44am UTC](https://mediasoup.discourse.group/t/mediasoup-client-transport-ice-candidate-error/6738/1 "2025-06-25T06:44:29Z")

</div>

Hi,

On Monday I moved our Node.JS/REACT application from

mediasoup-client 3.10.1 to 3.11.0

mediasoup 3.5.18 to 3.16.0

and sometimes I’m getting the following warning in Chrome, which as far as I know was never printed out before:

mediasoup-client:WARN:Transport ICE candidate error [url:turn:turn1.webrtc.xxxx.xx:443?transport=tcp, localAddress:192.168.2.x, localPort:63362]: 701 “Address not associated with the desired network interface.”

I have obfuscated the turn server address in the log to xxx.xx.

The application seems to work without problems, but of course the warning worries me. I have tested it from various geographical distributed networks to eleiminate routing or network issues, and the warning keeps popping up. Anybody sees similar problems?

Thanks!

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [June 25, 2025, 7:09am UTC](https://mediasoup.discourse.group/t/mediasoup-client-transport-ice-candidate-error/6738/2 "2025-06-25T07:09:48Z")

</div>

Those logs were introduced in a recent version. BTW those messages come from your coturn server.

---

<div class="post-metadata">

**Author:** ![Astagor](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/astagor/32/2515_2.png) [@Astagor](https://mediasoup.discourse.group/u/Astagor)\
**Post date:** [June 25, 2025, 8:10am UTC](https://mediasoup.discourse.group/t/mediasoup-client-transport-ice-candidate-error/6738/3 "2025-06-25T08:10:45Z")

</div>

Thanks. I do not see anything strange in my coturn logs. I will try to observe this in more detail.

---

<div class="post-metadata">

**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\
**Post date:** [June 26, 2025, 1:34pm UTC](https://mediasoup.discourse.group/t/mediasoup-client-transport-ice-candidate-error/6738/4 "2025-06-26T13:34:09Z")

</div>

I’m guessing that you have multiple network interfaces and some won’t successfully connect. If not mistaken all interfaces get checked so that warning is just a heads up for testing purposes. It’s not an error.

---

<div class="post-metadata">

**Author:** ![Astagor](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/astagor/32/2515_2.png) [@Astagor](https://mediasoup.discourse.group/u/Astagor)\
**Post date:** [June 26, 2025, 3:56pm UTC](https://mediasoup.discourse.group/t/mediasoup-client-transport-ice-candidate-error/6738/5 "2025-06-26T15:56:28Z")

</div>

> [@BronzedBroth](#):
>
> at you have multiple network interfaces and some won’t successfully connect. If not mistaken all interfaces get checked so that warning is just a heads up for testing purposes. It’s not an error.

Got it, thanks!

---

<div class="post-metadata">

**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\
**Post date:** [June 29, 2025, 12:55pm UTC](https://mediasoup.discourse.group/t/mediasoup-client-transport-ice-candidate-error/6738/6 "2025-06-29T12:55:32Z")

</div>

No worries, sounds like you’ve got things working and are concerned which is reasonable. You can turn these warnings off if your development/testing phase is over with.

Full send brother! 🙂