Troubleshooting
Firewall Blocking Video Calls? Why It Happens and What to Try
A firewall blocking video calls usually means the network you're on only lets ordinary web browsing through and drops the direct traffic that live video uses. The quickest test is to switch to mobile data or your home network: if the call connects there, the original network is the cause.
That's common on work, hotel, airport, café and other managed networks, and sometimes it's deliberate. This guide explains what's being blocked, how relay servers help calls get through, and what you can reasonably try, without working around rules that aren't yours to change.
Signs a network is blocking your video calls
- Websites load fine, but calls never start, or start and drop within seconds.
- The same device connects instantly on mobile data or at home.
- Your camera preview works, so permissions aren't the issue.
- Other video calling apps or sites also fail on that network.
- On Omlet, you get matched but keep seeing Couldn't connect to that person. Trying someone else…
If calls fail on every network, the cause is more likely your device or browser. Start with video chat stuck on connecting instead.
Why networks block peer-to-peer video
Browser video calls use WebRTC, a web standard for live audio and video. To keep delay low, WebRTC tries to send your video straight to the other person's device, usually over UDP and on ports chosen on the fly.
Many managed networks are set up the other way round. They allow normal secure web traffic and little else, so unfamiliar UDP traffic heading to random addresses gets dropped. Some networks go further:
- Category filtering: blocking whole types of sites, such as chat or video, by policy.
- Traffic inspection: devices that look at connections and stop the ones they don't recognize.
- Captive portals: hotel and venue Wi-Fi that blocks everything until you accept terms on a sign-in page.
- Bandwidth rules: limits on streaming or video to keep a shared connection usable for everyone.
When a network blocks WebRTC like this, it isn't personal. It's how organizations keep their networks secure and stop a few people using up everyone's bandwidth.
How relay servers help (and where they stop)
When a direct path doesn't work, WebRTC can fall back to a relay, called a TURN server, that forwards the call's audio and video between the two people. Relays can also run over the same kind of secure connection ordinary websites use, so they often get through networks that block direct traffic.
Omlet works this way. It tries a direct connection first, and when that isn't possible, relays the call through its network provider. The call stays encrypted either way, and Omlet doesn't record or store calls.
Relays have limits, though. If a network deliberately blocks video chat or the relay's addresses, nothing gets through. A relayed call can also add a little delay compared with a direct one. For the full explanation, read what a TURN server is.
What to try, in order
- Finish any Wi-Fi sign-in. On hotel, airport or café Wi-Fi, open a new tab. If a sign-in or terms page appears, complete it, then reload the chat.
- Switch to mobile data or a personal hotspot. It's the fastest way to confirm the network is the cause. Video uses a fair amount of data, so check your allowance first; our guide to video call data usage has the details.
- Try your home network. If it fails there too, keep going down this list.
- Check your own security software. Some antivirus suites have a firewall or web protection that can block a browser's call traffic. Look for your browser in the blocked list and allow it.
- Check your home router. Parental controls, security filters or DNS blocklists can block chat sites or the servers calls rely on. If you run one, look for blocked chat or video categories.
- Turn off your VPN for a test. VPN servers can restrict the same traffic a firewall does; see VPN causing video chat problems.
- Ask the network owner. On a work or venue network, IT staff can tell you whether video calls are allowed at all.
You don't need to open or forward ports on your router for browser video calls. WebRTC is designed to work without it, so skip any guide that tells you to.
Video chat blocked on Wi-Fi you don't control? Respect the rules
Video calls not working on a work network is often by design. On a workplace, hotel, library or venue network, a block may be exactly what the owner intended. Trying to get around it can break the network's terms of use, and on a work network it can cause real trouble for you.
- Use your own connection, such as mobile data, for personal calls.
- Keep personal chats off work devices, which are often monitored.
- If you think a block is a mistake, ask the network's IT team rather than looking for a workaround.
Public Wi-Fi has its own privacy questions beyond blocking. Our guide on whether it's safe to video chat on public Wi-Fi covers them.
Network types at a glance
| Where you are | What's usually going on | Best move |
|---|---|---|
| Home Wi-Fi | Rarely blocked; check router filters or security software | Steps 4 and 5 above |
| Work or office network | Strict firewall or deliberate policy | Use your own mobile data |
| Hotel, airport or café | Sign-in page, or limits on video | Finish the sign-in, or use mobile data |
| Mobile data | Usually works; some carriers restrict certain traffic | Try Wi-Fi to compare |
| Any network with a VPN on | The VPN server may block call traffic | Change server or protocol, or test without it |
When the call connects but struggles
Sometimes a restrictive network lets a call through only via a relay or with limited bandwidth. You'll see it connect, then stutter. If the picture keeps stopping while you can still hear each other, see video freezes but audio keeps going.
Once you're on a network that works, you can start a random video chat on Omlet with no account or download.