Server Settings
Configures the application server’s network settings. Some settings can only be changed when connected via localhost (the server machine itself), since changing the port remotely would immediately break the connection.
Server Port
Section titled “Server Port”The TCP port the CueCollab web server listens on. Changing this requires a server restart to take effect — all bookmarks and links to the server must be updated with the new port number. This setting is only editable when connected via localhost.
Ports below 1024 (e.g. 80) may require elevated system privileges to bind.
mDNS (Multicast DNS)
Section titled “mDNS (Multicast DNS)”mDNS allows devices on the local network to discover the CueCollab server by hostname (e.g. cuecollab.local) without needing to know the IP address. Particularly useful when the server’s IP changes or when setting up new client devices.
Enable mDNS Responder
Section titled “Enable mDNS Responder”Turns the mDNS discovery service on or off. When enabled, other devices on the same network can reach CueCollab at <hostname>.local.
mDNS Hostname
Section titled “mDNS Hostname”The hostname used for mDNS discovery (without .local). Default is typically cuecollab, reachable at cuecollab.local. Change this if you have multiple CueCollab servers on the same network.
HTTPS Access
Section titled “HTTPS Access”Enables an HTTPS server alongside the standard HTTP server, so clients can connect using an encrypted https:// connection. Required to provide a secure context for browser-based features like audio recording or prevent-sleep.
Enable HTTPS Server
Section titled “Enable HTTPS Server”Turns the HTTPS listener on or off. When enabled, CueCollab serves on the configured HTTPS port in addition to the regular HTTP port.
HTTPS Port
Section titled “HTTPS Port”The port the HTTPS server listens on. Defaults to 443 (standard HTTPS). Ports below 1024 may require elevated system privileges.
Certificate Type
Section titled “Certificate Type”Two modes are available:
Self-Signed Certificate — CueCollab generates its own certificate automatically. Browsers will show a security warning on first access because the certificate is not issued by a trusted authority. Download the certificate from the UI and install it as a trusted root on each client device to suppress the warning.
Manual Upload — Upload your own private key (.key or .pem) and certificate (.crt, .cer, or .pem). Use this if you have a certificate from a real CA or your own internal PKI.
Additional Hostnames
Section titled “Additional Hostnames”Extra hostnames or IP addresses to include in the self-signed certificate’s Subject Alternative Names. Add any hostname or IP clients will use to reach the server. Changing this field generates a new certificate — clients that trusted the previous one will need to re-trust the new one.