Network and security

Recommended stage network

1. Use a router or hotspot owned and administered by the band.
2. Set a strong Wi-Fi password.
3. Connect the DAW host by Ethernet where the stage setup permits.
4. Connect only approved control devices.
5. Keep guest access and client sharing with untrusted users disabled.
6. Rehearse with the same router, cabling, and device set used at the show.

Why isolation matters

Prest is intentionally unauthenticated and uses local HTTP/WebSocket traffic. A reachable client can control transport and open projects. Network isolation, not a Prest login, enforces access.

Unsafe networks

Never expose Prest on public Wi-Fi, shared venue Wi-Fi, or a network where audience or venue devices can reach the host.

Discovery

Prest advertises _http._tcp with the canonical hostname prest.local when mDNS is enabled and available. Local DNS and multicast behavior varies by router. Keep the integration-reported host address as the fallback.

Firewalls

The runtime listens for local connections. A host firewall can block browsers even when mDNS resolves. Exact firewall prompts and approved rules remain unpublished until clean-install validation defines them for each supported platform.

Diagnostic checklist

• Confirm host and browser are on the same private network.
• Confirm the host integration is running.
• Try the exact reported IP address if prest.local fails.
• Check client isolation or guest-network settings on the router.
• Check whether the host firewall blocked the runtime.
• Record the host, browser, address, and visible connection state for support.