Display is forwarded from the instance to the web browser via webrtc. If the display doesn't show or is black, 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 instances use Genymotion version 10.0.0 or higher.
Add-ons and extensions
If add-ons, extensions, or blockers are used with the web browser, make sure they do not block webrtc.
Firewall and security
Cloud provider security group or firewall rules
Configure the cloud provider security group or firewall so the instance can be reached from your location. The configuration must use at least the following rules:
https IN TCP 443
webrtc IN TCP 51000-51100
webrtc IN UDP 51000-51100
Local firewall ports
If a local firewall is used, make sure the following ports are open:
https IN TCP 443
webrtc IN TCP 51000-51100
webrtc IN UDP 51000-51100
Company network HTTPS access
If access is from a company network, make sure the company infrastructure has opened the HTTPS port:
https OUT TCP 443
If the company uses a proxy, HTTP CONNECT must be allowed on any ports. If the proxy is a SOCKv5 proxy, UDP ASSOCIATE must be allowed. If the company network uses NAT, either whitelist TURN/STUN IPs or use a own TURN server.
For more details, refer to the Genymotion Device image (PaaS) User guide: Access an instance from an Enterprise network (NAT)
Restart the instance
Restart the instance.
Public IP
This no longer applies since Genymotion Device Image ver. 13.0.0.Android 8.0 and above need access to the Internet to reach the TURN/STUN server. WebRTC communication is broken when Internet access is not available.
This requires a public IP. If public IP usage conflicts with security requirements, use your own TURN/STUN server.
If AWS is used, refer to the tutorial: How to create and setup a STUN/TURN server on AWS?