Display is forwarded from the server to the web browser via webRTC which uses specific TCP/UDP ports. It is probable that these ports are blocked.
Google regularly changes the way Google Chrome handles webrtc. This sometimes causes webrtc communication to be broken with Genymotion. In that case, try using a different web browser, such as Mozilla Firefox, or downgrade Google Chrome to the previous version.
To fix this:
- Make sure you have configured your security group in EC2 in a way you can connect to the instance from your location:
https IN TCP 443
webrtc IN TCP and UDP 51000-51100
- Make sure your firewall have the following ports open:
ssh IN TCP 22If you are accessing from a company network, make sure your company infrastructure has opened all the required ports on:
http IN TCP 80
https IN TCP 443
webrtc IN TCP and UDP 51003-51100
https OUT TCP 443If your company is using a proxy, please make sure to allow HTTP CONNECT on any ports. If the proxy is a SOCKv5 proxy, you will also need to allow UDP ASSOCIATE.
webrtc OUT TCP and UDP 51000-51100
- If you can't open these ports, you can use a TURN configuration to connect to the remote instance even with strict port opening policy:
- see https://en.wikipedia.org/wiki/Traversal_Using_Relays_around_NAT
- refer to Installing a TURN server on Linux for details and instructions
Since PaaS v8.0, the TURN server is activated by default and set to our own TURN server.
However, it is still possible to install and use a custom TURN server.
Please refer to Accessing a Virtual Device from an entreprise Network for more information.
- Restart the instance