ICE failed

[ex]

Hi,

I'm trying to connect to a page using the streaming plugin from a computer behind a different NAT. I am just testing the app by exposing port 80 to the internet using ngrok, and I've set up a STUN and TURN server with Janus. I can connect to the media streams perfectly from the ngrok subdomain from any machine in the same LAN, but it doesn't work for a peer on a different network. A session and handle are created, but I get this error on the Janus side:

ICE failed for component 1 in stream 1, but let's give it some time... (trickle received, answer received, alert not set)

[ERR] [ice.c:janus_ice_check_failed:1544] [410742284103945] ICE failed for component 1 in stream 1...

No errors on the web browser, it stays at the 'starting' stage.

This seems similar to this problem: https://groups.google.com/forum/#!searchin/meetecho-janus/ice$20failure%7Csort:relevance/meetecho-janus/17GFz0C9a9c/8_ZvEmbVDQAJ 

But I don't fully understand how they resolved it.

Thanks for any advice you can provide!

[Lorenzo Miniero]

http://www.meetecho.com/blog/understanding-the-janus-admin-api/

L.

[ex]

Hi Lorenzo, 

Thanks, I've been using the Admin API to debug, and have read your article thoroughly. It is still failing at the DTLS handshake, but unlike the example in the article, the public address of the client is recognized as a remote candidate. I have a STUN (and TURN, for good measure) server configured in janus.cfg and it should also be set up in janus.js

Full handle info: https://pastebin.com/raw/nBW5ta1j

Thanks, any further insight is greatly appreciated!

[Richard Phillips]

What version of libnice are you using? 

I just spent three days debuging before getting to this: 

https://groups.google.com/forum/#!topic/meetecho-janus/UBlvbWiwgMk

https://github.com/meetecho/janus-gateway/issues/788

If using a recent libnice, try rolling back (I went back to  0.1.4.1 but will try and find something more recent that works)

[Richard Phillips]

Might not be your issue - but just to update - latest master of libnice fixed a similar but not identical problem for me.. no need to go back to 0.1.4.1 as I mentioned, just use libnice master or:

git checkout dbaf8f5ccd76089e340883887c7e08e6c04de80a

[ex]

Would my version of libnice-dev matter? 

[uxmaster]

It could matter. But you will never know, until you try.

I suggest using the version mentioned by Richard, since it seems to work well.

[ex]

I was able to get it working by specifying an IP for 1:1 mapping in the configs, even though I am not running my server as an AWS instance. However, the DTLS handshake now takes a pretty long time, even when I connect on a browser within the NAT. Thanks for your help everyone! I'll continue exploring.

On Tuesday, August 1, 2017 at 1:58:18 PM UTC-4, ex wrote:

[Lorenzo Miniero]

Are you trying with our default certificate, or one you generated on your own? If it's too large, it might exceed the MTU, and it might take time for the stack to reduce the fragmentation boundaries. Try setting the DTLS mtu in janus.cfg to something smaller, e.g., 1200. If you're using master, we already use a more conservative value.

L.