Zoom Error Code 104110 usually points to a connection path problem between your device and Zoom services. The fix is rarely “one magic button.” It’s almost always about proving where the connection breaks (device, router, VPN/proxy, firewall, or service status) and then removing that block.
Table of Contents
What Error Code 104110 Means
Zoom groups 104110 with other server connectivity error codes (including 104101–104118). In practical terms, the app is failing to complete a network connection to Zoom services, commonly due to firewall rules, proxy behavior, security inspection, or upstream connectivity limits [✅Source-1].
This code can appear while joining a meeting, during sign-in, or when the desktop/mobile app tries to refresh service endpoints. The common thread is that Zoom can’t reach what it needs over the network path you are currently on.
How To Think About The Fix
Instead of guessing, isolate the failing layer. A clean workflow is: service status → basic network → security layers (VPN/proxy/firewall) → app reinstallation.
Fast Checks Before You Change Anything
Goal: confirm it’s not a temporary service-side or local network hiccup.
- Close Zoom completely (on desktop, exit from the system tray/menu bar), then reopen and retry once.
- Restart your Wi-Fi router/modem if you control it. If you don’t, reconnect to the network.
- Try an alternate network: mobile hotspot or another Wi-Fi. A quick switch is a strong signal for firewall/proxy/VPN causes.
- Check Zoom’s official status page for incidents or maintenance that can affect connections [✅Source-4].
If Zoom works on a hotspot but fails on your primary network, focus on network controls (proxy, firewall, VPN) rather than account settings.
Confirm The Break With Built-In Diagnostics
Zoom includes a Network Connectivity Tool that can test connectivity, trace routes to Zoom services, and report service reachability. This is one of the fastest ways to replace “it feels like the internet” with concrete results [✅Source-3].
Open It (Desktop App): use the shortcut Ctrl+Alt+Shift+D on Windows or Cmd+Option+Shift+D on macOS, then run a network test.
- Look for failures in Service Status or obvious timeouts in route tests.
- Export logs if you need to share findings with IT or support.
- If the tool shows a proxy being detected unexpectedly, treat that as a priority lead.
Network Causes And How To Fix Them
Router, DNS, and Captive Portal Issues
Some networks require a browser sign-in (hotel, cafe, guest Wi-Fi). Zoom may fail until you complete that portal step. Open a web page first, confirm you’re truly online, then retry Zoom connectivity with a fresh session.
If your router is under heavy load, a simple reboot can restore stable name resolution and routing. If only one device fails, the issue is more likely local (security software, VPN app, or misconfigured proxy) than router-wide.
Wi-Fi vs Ethernet
When possible, test on Ethernet. It removes wireless interference from the equation and can quickly confirm whether you’re dealing with a Wi-Fi stability issue rather than a firewall/proxy policy.
Signals That Point To The Right Fix
| What You Observe | What It Usually Suggests | What To Do Next |
|---|---|---|
| Works on hotspot, fails on office Wi-Fi | Firewall/proxy policy or SSL inspection | Check proxy/VPN, then review ports/domains in the firewall section |
| Fails only on one device | Local security layer or app state | Disable VPN/proxy on that device, then do a clean reinstall |
| Multiple users fail at the same time | Service incident or ISP routing issue | Check official service status, then retest |
| Connectivity tool shows proxy detected unexpectedly | Transparent proxy or forced network inspection | Request allow-listing for Zoom domains and media paths |
Firewall, Proxy, and VPN Causes
104110 is frequently triggered by security layers that are great for web browsing but unfriendly to real-time media. Deep inspection (including SSL/TLS inspection) can introduce delay or break media signaling, and Zoom advises avoiding heavy inspection for Zoom traffic in enterprise environments [✅Source-6].
If You’re On A Managed Network: ask for allow-listing rather than “turning security off.” This is the cleanest, policy-friendly fix.
- Request that Zoom domains are not filtered or SSL-inspected.
- Confirm outbound rules allow Zoom meeting traffic (especially UDP media).
- If a VPN is required, ask about split tunneling for Zoom traffic.
If You Control Your Device: temporarily pause VPN/proxy apps and retry. If it immediately works, you’ve found the layer to tune properly.
- Disconnect from VPN, retry once, then reconnect.
- Disable “web shield” or “HTTPS scanning” features only if your organization allows it.
- Re-enable protections after testing and prefer allow-listing as the final fix.
Ports And Domains That Matter For Zoom Meetings
On networks with strict egress rules, Zoom meetings typically need standard web ports plus dedicated meeting media paths. Zoom’s official firewall guidance includes TCP 80/443 for web access, TCP 443/8801/8802 for meetings, and UDP 3478/3479 plus UDP 8801–8810 for media flows; it also notes proxy behavior and recommends allowing zoom.us and *.zoom.us from proxy or SSL inspection [✅Source-2].
Practical Tip: if UDP is blocked on your network, Zoom may fall back to TCP, but meeting quality and connection reliability can suffer. Opening the documented UDP media ports is a common turning point for persistent 104110 cases.
App-Level Fixes That Often Help
Once you’ve ruled out an outage and obvious network blocks, clean up the local app state. A corrupted install or stuck network setting can keep Zoom in a bad loop.
- Sign out of Zoom, then sign back in (this refreshes tokens and endpoints).
- Update Zoom to the latest available version in your environment (store-managed devices may require IT approval).
- Uninstall Zoom, restart the device, then reinstall. This resets local networking hooks and cached components.
- If you use multiple network adapters (Ethernet + Wi-Fi + VPN), disable the ones you don’t need for the test and retry. Keep the setup simple.
Test Your Fix Without Risking A Live Meeting
After each change, validate with a controlled join. Zoom provides an official test meeting page, which is useful for confirming whether your device can connect and join successfully on the current network [✅Source-5].
Testing Pattern: make one change → join the test meeting → note the result. This avoids stacking multiple changes and losing the real cause.
When To Involve Your Network Administrator
If you’re on a workplace or campus network, lasting fixes often require policy updates rather than local tweaks. Bring evidence, not guesses.
- Share the exact error: 104110 and the time it occurred.
- Share whether it works on a hotspot (yes/no) and whether it fails on all devices or only one.
- Export results from the Network Connectivity Tool and attach them to your request.
- Ask specifically about proxy/SSL inspection and whether *.zoom.us is excluded from inspection and filtering.
FAQ
Is Zoom Error Code 104110 An Account Problem?
Most of the time, no. 104110 sits in a family of connectivity codes where the app can’t reach Zoom services over the current network path. If signing in works on a hotspot but not on your main network, that pattern strongly supports a network control issue.
Why Does It Work On Mobile Hotspot But Not On My Wi-Fi?
This usually indicates a firewall, proxy, or VPN policy on the Wi-Fi network. The hotspot bypasses those controls, so Zoom can connect normally.
What Should I Send To IT To Fix 104110 Faster?
Send the timestamp of failure, the network name, whether other apps work, and exported results from the connectivity tool. Ask them to confirm outbound rules and any SSL inspection exclusions for Zoom domains.
Can A VPN Trigger Error 104110?
Yes. VPN routing and inspection can interfere with real-time media. If a VPN is required, ask about split tunneling so Zoom media can take a more direct route without overloading the tunnel.
What If Everything Looks Fine But 104110 Still Happens?
Run the test meeting again after a clean reinstall. If it still fails, check service status, then focus on network path evidence: proxy detection, blocked UDP media ports, or DNS filtering. A short, repeatable test record is more useful than trying many changes at once without notes.