Network & Firewall Requirements
When deploying Vū in a managed network environment (corporate offices, universities, venues), your IT team may need to whitelist specific ports and domains to allow Vū to function correctly.
If you're on a standard home or small business network without a managed firewall, everything should work without any configuration.
Required Ports
| Port | Protocol | Purpose |
|---|---|---|
| 80 | TCP | HTTP (general web traffic) |
| 443 | TCP | HTTPS (Vū Studio, Supabase, APIs) |
| 1883 | TCP | MQTT (unencrypted — development/local use only) |
| 8084 | TCP | MQTT over WebSocket/TLS (browser clients) |
| 8883 | TCP | MQTT over TLS (production command bus) |
| 3478 | TCP/UDP | STUN/TURN (WebRTC ICE negotiation) |
| 5349 | TCP/UDP | TURN over TLS (WebRTC fallback) |
| 49152–65535 | UDP | WebRTC media (dynamically assigned) |
Required Domains
All of the following domains must be reachable from both the Windows media server and any controlling devices (phones, tablets, laptops):
| Domain | Purpose |
|---|---|
one.vu.studio | Vū Studio web application |
vu.studio | Vū marketing site |
docs.vu.studio | Vū support and documentation |
supabase.vu.studio | Authentication and database |
ic7c613e.ala.dedicated.aws.emqxcloud.com | MQTT broker (EMQX) — command bus (ports 8883/8084) |
s11378.nyc1.piesocket.com | WebSocket relay for command delivery |
4b17db9c10460d3ab1f82a6f4e9b335e.r2.cloudflarestorage.com | Media storage (Cloudflare R2) |
api.sendgrid.com | Email notifications |
How Vū Communicates
Understanding the communication channels helps with firewall configuration:
MQTT (Ports 1883, 8084, 8883)
The primary command bus. The Vū Studio web app and the Vū Media Server software both connect to a cloud MQTT broker (EMQX). All playback commands, scene changes, lighting commands, and state updates travel over MQTT. If MQTT is blocked, the system cannot be controlled remotely.
WebSocket
Used as a secondary signaling channel and fallback for WebRTC connection setup. The Vū Media Server software maintains a persistent WebSocket connection to channels named after your wall ID.
WebRTC
Used for camera preview streaming — when you view a live camera feed from a PTZ or other camera connected to the Vū Media Server software, the video travels over WebRTC directly between the browser and the Windows machine using peer-to-peer data channels. WebRTC requires STUN/TURN servers and UDP ports to be open for optimal performance.
HTTPS (Port 443)
Used for all API calls — fetching media, authenticating users, managing wall settings, and communicating with Supabase for real-time database updates.
Troubleshooting Connectivity
If your system shows as offline or commands aren't reaching the display:
- Verify the Windows machine has outbound internet access on port 443, 8084, and 8883
- Check that
one.vu.studioands11378.nyc1.piesocket.comare not blocked by a content filter - On the Windows machine, open a browser and navigate to one.vu.studio — if it doesn't load, there's a network-level block
- See the full Connection Troubleshooting guide →