Network Connectivity
Ensure that your network allows communication between the CueCollab server and client devices.
Never publish the server to the internet without additional security measures.
Incoming Connections
Section titled “Incoming Connections”The following ports must be accessible on the CueCollab server machine:
| Port | Protocol | Description |
|---|---|---|
| 3000 | TCP (HTTP) | CueCollab Server (required) |
| 3333 | UDP (OSC) | OSC remote control (port can be customized) |
| 6454 | UDP (ArtNet) | ArtNet timecode input |
Port 3000 - CueCollab Server
Section titled “Port 3000 - CueCollab Server”This is the main HTTP port for the CueCollab web interface and realtime server connection using HTTP WebSockets. Client devices connect to this port to access the application and realtime features.
Firewall rules: Allow incoming TCP connections on port 3000 from client devices on your network.
Port 3001 - CueCollab Realtime (removed since v0.13)
Section titled “Port 3001 - CueCollab Realtime (removed since v0.13)”This WebSocket connection provides real-time updates between the server and client devices, ensuring synchronized data across all connected users.
Firewall rules: Allow incoming TCP connections on port 3001 from client devices on your network.
Port 3333 - OSC Remote Control
Section titled “Port 3333 - OSC Remote Control”This UDP port receives OSC remote control data. Required only if using OSC to remote control CueCollab.
This port can be customized in the application settings if needed to avoid conflicts with other software.
Firewall rules: Allow incoming UDP packets on port 3333 from your OSC remote control source.
Port 6454 - ArtNet Timecode
Section titled “Port 6454 - ArtNet Timecode”This UDP port receives ArtNet timecode data. Required only if using ArtNet as your timecode source.
Firewall rules: Allow incoming UDP packets on port 6454 from your ArtNet timecode source.
Outgoing Connections
Section titled “Outgoing Connections”For license activation and updates, ensure that the application can access the internet:
| Server | Protocol | Description |
|---|---|---|
| api.mschoeffmann.com | TCP/443 (HTTPS) | License activation and validation (required) |
| files.mschoeffmann.com | TCP/443 (HTTPS) | Update check and downloads |
License Server (api.mschoeffmann.com)
Section titled “License Server (api.mschoeffmann.com)”Required for license activation and periodic validation. The application must be able to reach this server at least once every 30 days (depending on license type).
Firewall rules: Allow outgoing HTTPS connections to api.mschoeffmann.com on port 443.
Update Server (files.mschoeffmann.com)
Section titled “Update Server (files.mschoeffmann.com)”Used to check for application updates and download new versions.
Firewall rules: Allow outgoing HTTPS connections to files.mschoeffmann.com on port 443.
Network Topology Considerations
Section titled “Network Topology Considerations”Local Network Setup
Section titled “Local Network Setup”For optimal performance, connect the CueCollab server and all client devices to the same local network using wired (Ethernet) connections.
Recommended:
- Gigabit Ethernet (1000 Mbps) or faster
- Dedicated VLAN for production systems (optional but recommended for larger setups)
- Quality of Service (QoS) configuration to prioritize CueCollab traffic
Wi-Fi Clients
Section titled “Wi-Fi Clients”While CueCollab can work with Wi-Fi clients, wired connections are strongly recommended for:
- The CueCollab server machine
- Devices used for critical operations (e.g., showcallers)
Wi-Fi may be acceptable for monitoring-only clients or non-critical users.
Remote Access
Section titled “Remote Access”Remote access is technically possible but not recommended, as CueCollab currently lacks authentication mechanisms. Additionally, internet connections introduce latency, which is problematic when timecode accuracy is critical.
For secure remote access, Tailscale (a VPN that enables computer sharing similar to file sharing on Dropbox) has proven effective for sharing the server machine with team members.
Remote access may be used experimentally, but only at your own risk.
Never publish the server to the internet without additional security measures.