Network Connectivity

💡

This is the network documentation of VisualRadioAssist 4, follow this doc to make sure VRA is able to access all the right resources via public internet (Cloud) and locally via configured ports (Server applications)

Cloud connectivity

VRA applications and player-contents have to stay in contact with VisualRadioAssist Cloud (”VRA Cloud”) 24/7 in order to facilitate all data to be up to date time-sync.

The following domains (DNS) have to be accessible over port 443 TCP over public internet at all times:

visualradio.cloud [HTTPS]

cloud.visualradioassist.live [HTTPS]

loki.cloud.visualradioassist.live [HTTPS]

api.cloud.visualradioassist.live [HTTPS]

socket.api.cloud.visualradioassist.live [HTTPS/WSS]

If you want to use beta or dev versions of VRA, the following domains should be added to the list;

dev.cloud.visualradioassist.live [HTTPS]

dev.api.cloud.visualradioassist.live [HTTPS]

socket.dev.api.cloud.visualradioassist.live [HTTPS/WSS]

Public (LB) IP for all connectivity: 51.158.130.138

Cloud Live connectivity

For low latency Cloud Live Output Players the machines where the Output Player app is running must be able to access the following port range to the outside world (internet);

55000 – 60000 to all destinations

⚠️ Proxy Note

Using VRA Cloud behind a strict proxy can cause instabilities. Whitelisting the above domains will work for basic usage of the Cloud Dashboard.

Using VRA Server applications behind a proxy could introduce new challenges. You have to configure your proxy to allow bi-directional websocket traffic behind the proxy. HTTPS Traffic to the following domains should also be allowed:

customer-k9rjbgcrkvgq9ya1.cloudflarestream.com

app-dl.s3.nl-ams.scw.cloud

*.ingest.sentry.io

🐞 Note on error reporting

We make use of the widely known and industry standard application monitoring software Sentry.io. To make sure we can deliver the best support whitelist *.ingest.sentry.io as well for use behind a proxy or WAF related security software.

🛡️ SSL Note

All communication over HTTPS is always done via industry-standard mTLS, providing a even better secure socket layer than a initial SSL set-up. Further mTLS via EV / OV authorized certificates is on the Roadmap.

API Data Sources (Cloud Proxied)

When using the Cloud Proxied API Data Sources the VRA Cloud will initiate requests to your API from ip’s in the following IPv4 and IPv6 ranges;

62.210.0.0/16

195.154.0.0/16

212.129.0.0/18

62.4.0.0/19

212.83.128.0/19

212.83.160.0/19

212.47.224.0/19

163.172.0.0/16

51.15.0.0/16

151.115.0.0/16

51.158.0.0/15

2001:bc8::/32

Local Server Applications

The three locally installable applications (see machine specs) have to be able to communicate with each other over LAN and with Cloud (👆)

By default VRA Server Core is configured to host this local HTTP server on TCP port 3002 with host 0.0.0.0 in order to maximize discoverability at set-up.

Within an constrained environment you can minimize the Server Core’ host availability by making this a specific LAN-range IP (192.168. , 10.10. e.d.)

VisualRadioAssist Server Software should access local (video/audio) hardware equipment as well besides the Cloud and Server Core API. Be aware that this hardware is usually not configured in the same network as VRA Cloud is accessible.