ICE failed, your TURN server appears to be broken

[fuatberk]

Hello,

I have a problem

Broadcast is not working via chrome-firefox - Sometimes they connect, sometimes not connect The broadcast does not work with firefox-opera Broadcast is not working with opera-chrome

But

Works with Chrome-Chrome, Firefox-Firefox, Opera-Opera

Can you help me?

My Server(https://github.com/andyet/signalmaster) : https://instreamservers.com:8888/socket.io/ My JS : https://www.berkfuat.com/assets/theme/video/latest_stream.js

[Zythyr]

Are the two peers trying to connect on the same local network or on two different networks?

I was having the same issue when two peers trying to connect were on the same local network. However, I realized one of my browser privacy extensions, Privacy Badger, was the culprit. See more details; https://github.com/EFForg/privacybadger/issues/1967

[fuatberk]

Dear @Zythyr ;

• yes over two different networks.
• I'm sorry my English is a little bad.
• I did not understand exactly what I was supposed to do

I use SSL : https://www.berkfuat.com

"media.peerconnection.ice.default_address_only;true " "media.peerconnection.ice.no_host;true "

Where do I add the above codes?

[Zythyr]

@BR9 I think you misunderstood me. You do NOT need to do anything with media.peerconnection.ice.default_address_only;true and media.peerconnection.ice.no_host;true. They are Firefox's configuration variables. Do NOT modify these.

Since the two peers you're testing are on two different networks, I am not really sure what is causing your issue. For me, the ICE Failed issue was occurring on the same network. I resolved my issue by disabling Privacy Badger extension.

I suggest the following for troubleshooting:

1) Use this SimpleWebRTC Filetransfer demo . In this demo there is is no TURN server. There is only a STUN server. If two peers are able to connect directly and transfer files using WebRTC, then you can be confident there is not browser/network specific issues between the two peers.

2) I am assuming you're using signalmaster as your signalling server. Make sure you have properly configured the STUN/TURN server in the signalmaster/config/development.json and signalmaster/config/production.json 3) You can check if your own personal STUN/TURN servers are working correctly by using this tool: https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/

4) Check out this article on how how to debug some of the WebRTC issues in your browser: https://testrtc.com/webrtc-api-trace/

[fuatberk]

@Zythyr thanks for the answers :)

But

I do not have a turn server I only use SignalMaster (https://github.com/andyet/signalmaster)

[JakeTrock]

@BR9 it's fine that you use the public turn server now, but if you want to do anything other than going on the app yourself as a hobbyist then you MUST install a TURN extension on your server, I recommend socket.io

[RamyaAshika]

But I dont't have any privacy Badger in firefox but still I'm getting this error on same network @Zythyr