Network configuration
Last updated: 26 October 2026 16:36 BSTThe VU.CITY Hub allows users to run VU.CITY through a web browser without the need for high-spec computer hardware or a traditional desktop installation. Real-time streaming and WebSocket technology are used to deliver this interactive design environment via our cloud infrastructure.
VU.CITY Hub requires a modern operating system and web browser to function.
Supported operating systems
- Windows 10 or later
- macOS 14 or later
Mobile devices running iOS or Android are not currently supported.
Supported browsers
- Chrome, Firefox, Edge, Brave, Safari.
Internet Explorer is not supported.
Hardware acceleration
Modern browsers can use the device’s GPU to decode the VU.CITY video stream and render graphics, which reduces CPU load and keeps navigation smooth. This makes the biggest difference on devices with integrated graphics, where turning it off can cause choppy or delayed navigation.
Recommendation: Keep hardware acceleration enabled unless troubleshooting a specific graphics or driver issue.
To enable hardware acceleration:
- Chrome, Edge and Brave: Settings → System → enable Use graphics acceleration when available → relaunch the browser.
- Firefox: Settings → General → Performance → disable Use recommended performance settings → enable Use hardware acceleration when available → restart the browser.
- Safari: Hardware acceleration is always on and does not need to be changed.
Network requirements
These requirements are standard for browser-based streaming applications and are similar to those used by video conferencing tools such as Microsoft Teams or Zoom. Outbound connections to the following are required.
Domains
- *.vu.city
VU.CITY also interacts with the following third-party domains:
- *.auth0.com
- *.posthog.com
- api.hsforms.com
Required ports
TCP 80
TCP 443
TCP / UDP 19303
Ports 80 and 443 are standard web ports - if general browsing works on the network, these are likely already open. Port 19303 (TCP and UDP) is the relay used to route live video when a direct connection is not available.
Proxy, inspection, and filtering
- All traffic between the end user and VU.CITY infrastructure is encrypted.
- Explicit proxy servers (proxy servers that the web browser is aware of) are supported.
- Transparent proxy servers (proxy servers that the web browser is unaware of) may interfere with WebSockets and should be bypassed for the above domains.
- If SSL inspection / HTTPS interception is in use, the listed domains should be exempted. Inspecting authentication or long-lived WebSocket traffic can disrupt session loading.
- Where a proxy or deep-packet inspection is in use, WebSocket connections over port 443 will also need to be permitted.
Testing the connection
The VU.CITY Network Connectivity Test can be used to check whether a device and network meet the requirements for using VU.CITY. It checks connectivity, WebRTC, video streaming and network performance, and can help identify potential issues before using VU.CITY or when troubleshooting connection or streaming problems.
Learn more about the Network Connectivity Test
Additional third-party requirements
Further detailed third-party requirements can be found here, if required:
Need help?
If connectivity issues persist after reviewing these requirements, this article should be shared with the relevant IT administrator. If the issue remains unresolved, contact VU.CITY Technical support for further assistance.