How can I diagnose WebRTC connection problems?

Home > Resources > Knowledge Base > How can I diagnose WebRTC connection problems?

How can I diagnose WebRTC connection problems?

Important remark: make sure to use the Chrome browser. Other browsers may have limited support for WebRTC but in the future compatibility will get better. Check http://iswebrtcreadyyet.com/legacy.html to see if your browser supports this open source development. We currently only test Chrome.

 

For remote connections (rtc.iqunet.be for software versions up to 1.2.14 and connect.iqunet.com for software versions from 1.3.1 on) we do not require any setup of port-forwarding or related technologies. The Server will make an outgoing connection to announce itself to our signaling server (peer.iqunet.lu, SSL port 80 and 443).

From there on the built-in WebRTC technology in your browser will take over and try to establish a direct or relayed connection. Data traffic will not pass our systems any more (apart from encrypted traffic over the fallback relay server that we cannot access).

 

If the connection fails, it could be a problem of:

  1. Signaling: your browser (or iQunet Server) is not allowed to contact peer.iqunet.lu SSL port 80/443.
  2. WebRTC data traffic: your computer (or iQunet Server) are behind a very strict firewall that drops all UDP, STUN, TURN etc.

 

You can check these connection problems here.

Click on “Gather Candidates” at the bottom of the page. You should have at least 1 candidate appearing.

 

Check webrtc connection

 

 

You can find more info on connection issues here: Troubleshooting WebRTC connection issues.