Home Bridge Connectors & Networking Configuring enterprise network firewalls for SoLoPrint WebRTC/UDP traffic

Configuring enterprise network firewalls for SoLoPrint WebRTC/UDP traffic

Last updated on Mar 31, 2026

Commercial Print Farms

If your SoLoPrint array is deployed in a school or enterprise locked behind an aggressive firewall (e.g., SonicWall, Fortinet), your camera feeds may fail to connect, showing a perpetual spinning wheel.

Why?

Enterprise firewalls often block non-standard outbound UDP ports, which are required for WebRTC peer-to-peer tunnels.

The Solution

You must whitelist the outbound traffic to ensure the Bridge and your Browser can successfully negotiate the tunnel.

  1. Whitelist Domains: Ensure that wildcard domains *.soloprint.app and *.solovisionllc.com are allowed outbound HTTP/HTTPS.
  2. STUN/TURN Servers: Our signaling infrastructure operates out of standard WebRTC ports. Please ask your IT administrator to allow outbound UDP traffic on ports 3478 and 443 directed toward standard AWS STUN ranges.

If strict UDP blocking remains in place, SoLoPrint will fall back to deeply routed TCP relays (TURN), which will function but may result in slightly higher latency.