What actually breaks when you build a WebRTC SFU in Go

Deploying a WebRTC SFU in Go using Pion involves challenges beyond basic examples. While signaling via WebSockets on port 443 typically works through reverse proxies, media paths often fail, causing issues where connections establish but video remains absent. Common failures include publisher connection drops, viewers joining mid-stream, and socket reaping. These infrastructure-level problems often mimic code bugs, making them difficult to diagnose when moving from local laptops to cloud VM server environments.