The Virtual Device display doesn't show in web browser with Genymotion PaaS/Device image

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

Rules to connect from your location

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

Rules for a local firewall

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

Rules for a company network

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 this article: How to create and setup a STUN/TURN server on AWS?

Restart the instance

4. Restart the instance

Public IP

If your instance does not have any public IP and you are getting a black display when connecting to the instance private IP, you are probably using an old deprecated Genymotion AMI/image.

Make sure to use the latest available stable version Genymotion AMI/image.

Please refer to Genymotion PaaS changelog for reference.

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.

If you are using AWS, you can refer to our tutorial: How to create and setup a STUN/TURN server on AWS?

Related articles