If you encounter this error, it means that you had trouble connecting to your instance using the real-time communication protocol used to display Genymotion.
To fix this error, you can check several things:
1. Check that you authorized your IP address to connect to your instance using the webrtc port range: 51000-51100 (UDP & TCP) using security group or networking tags.
2. Check that your local network allows you to connect to the webrtc port range 51000-51100 on your Genymotion instance IP address.
3. If you cannot really change security group or your own firewall, you will need to configure a TURN server. See our tutorial for the documentation on how to setup a TURN server.
If configuring your instance network did not fix your issue or if you cannot modify it, you can contact the support.
ICE is a framework used by Genymotion Cloud that allows you to overcome the complexities of real-world networking. It’s ICE’s job to find the best path to connect you to your Genymotion instance. It may be able to do that with a direct connection, but it also works for clients where a direct connection is not possible (i.e. behind NATs).
In the case of asymmetric NAT, ICE will use a STUN (Session Traversal Utilities for NAT) server. A STUN server allows clients to discover their public IP address and the type of NAT they are behind. This information is used to establish the media connection. The STUN protocol is defined in RFC 3489.
If a STUN server cannot establish the connection, ICE can use TURN. Traversal Using Relay NAT (TURN) is an extension to STUN that allows media traversal over a NAT that does not do the “consistent hole punch” required by STUN traffic. TURN servers are often used in the case of a symmetric NAT.
Unlike STUN, a TURN server remains in the media path after the connection has been established. That is why the term “relay” is used to define TURN. A TURN server literally relays the media between you and your Genymotion instance. That is the reason why we do not provide TURN server by default.
Clearly, not having to use TURN is desirable, but not always possible. In some situations, you will be forced to configure a valid TURN server for having the connection to work.
You can check Temasys documentation for more information about TURN/STUN and why it is needed