Display is forwarded from the instance to the web browser via webrtc - if the display doesn't show or is black, it is probable that something is blocking webrtc.
Google Chrome
Genymotion v9.0.0 and lower images are no longer compatible with Google Chrome since version 89.
Make sure your instances use Genymotion version 10.0.0 or higher:
Add-ons and extensions
If you use add-ons, extensions or blockers with your web browser, make sure that they don't block webrtc.
Firewall and security
- Make sure you have configured your cloud provider security group or firewall in a way you can connect to the instance from your location with at least the following rules:
https IN TCP 443
webrtc IN TCP 51000-51100
webrtc IN UDP 51000-51100 - If you are using a local firewall, make sure the following ports are open:
https IN TCP 443
webrtc IN TCP 51000-51100
webrtc IN UDP 51000-51100 - If you are accessing from a company network, make sure your company infrastructure has opened the HTTPS port:
https OUT TCP 443
If your company is using a proxy, you also need to allow HTTP CONNECT on any ports. If the proxy is a SOCKv5 proxy, allow UDP ASSOCIATE.
If your company network uses NAT, you will either need to whitelist our TURN/STUN IPs or use your own TURN server. For more details, please refer to Genymotion Device image (PaaS) User guide: Access an instance from an Enterprise network (NAT)
- Restart the instance
Public IP
Note
This no longer applies since Genymotion Device Image ver. 13.0.0.
Android 8.0 and above need to have access to the Internet to reach our TURN/STUN server or webRTC communication will be broken.
This requires a public IP but if this goes against your security requirements, you have to use your own TURN/STUN server. For more details, please refer to Genymotion Device image (PaaS) users' guide: Access an instance from an Enterprise network (NAT)
If you are using AWS, you can refer to our tutorial: How to create and setup a STUN/TURN server on AWS?