Thanks — you're asking whether a self‑hosted LiveKit server will work over a mobile hotspot and whether you’ll see connectivity issues. Short answer: it can work, but you should expect reliability limitations and take a few precautions. Why problems happen • Mobile hotspots use NAT, carrier restrictions, and dynamic IPs; incoming ports may be blocked or change. • Mobile networks can block or throttle UDP, which WebRTC prefers for media, and have higher latency and variable bandwidth. What to do to improve reliability • Run a TURN relay over TLS (port 443). TURN over TLS is most likely to pass through hotspot/firewall restrictions and is the best fallback when UDP is blocked. • Ensure your TURN server is publicly reachable (static public IP / DNS) rather than relying on the hotspot’s IP. • Open and forward the required server ports if the hotspot/router allows it (media UDP/TCP and LiveKit ports), though many hotspots won’t support this. • Use LiveKit’s congestion control / adaptive bitrate — it helps media quality on variable mobile links. • For production, avoid hosting the LiveKit server on a mobile hotspot. Use a stable cloud or datacenter host and let clients connect from mobile hotspots. If you want, tell me whether you plan to run the server on the hotspot device itself or have clients join a LiveKit instance hosted elsewhere — I can give concrete setup steps for TURN, ports, or recommended deployment. Sources: Deploying LiveKit | LiveKit docs | Firewall Tips | Bringing Zoom's end-to-end optimizations to WebRTC