Seeing Zoom Error Code 104124 usually means the app cannot keep a stable connection to Zoom’s servers. In practice, the trigger is often network reachability: a firewall rule, a proxy, a VPN route, or a filtered Wi-Fi that interrupts the connection at the exact moment Zoom tries to sign in or join a meeting.
This guide focuses on direct fixes that you can apply safely. You will also find admin-ready network details when the issue depends on corporate policies. The goal is simple: restore a clean path between your device and Zoom services without weakening your overall security.
Start With Two Safe Checks
- If you are on office or school Wi-Fi, quickly try a mobile hotspot for one test. If it works there, the issue is almost certainly policy or filtering on the original network.
- Make sure your device date and time are correct. A wrong clock can break secure connections even when the internet looks fine.
Table of Contents
What Error Code 104124 Means
Error Code 104124 is grouped with other 1041xx codes that indicate connectivity issues with Zoom’s servers. The immediate fix is rarely “one button”; instead, you remove the one element that blocks Zoom from reaching required endpoints (network rules, proxy behavior, or local security filtering).[✅Source-1]
When this happens, Zoom is typically failing during service handshake (sign-in, meeting join, or initial audio/video negotiation). That is why you can sometimes browse websites normally while Zoom still fails.
Common Patterns
- Works on hotspot, fails on a specific Wi-Fi (network filtering).
- Fails only on office VPN (routing or inspection).
- Fails after security software changes (local firewall rules).
- Fails right after a system time change (TLS validation).
What It Usually Is Not
- A wrong meeting ID (that typically shows a different message).
- A camera or microphone permission issue.
- A hardware limitation on a modern device.
- A problem fixed by random “cleanup” tools (avoid risky changes).
Fast Checks Before You Change Settings
These checks are low-risk and often enough to clear a temporary block. Keep one idea in mind: you are testing for consistency—Zoom should connect the same way every time on the same network.
- Fully quit Zoom, then reopen it (on Windows, confirm it is not still running in the tray). Use Task Manager if needed.
- Restart your router or switch networks once. A clean network session can remove a stuck state in DNS or routing.
- Try joining from the Zoom desktop app instead of the browser (or the other way around). This isolates a web restriction vs an app restriction.
- If you use a VPN, disconnect it for one test. If you must keep a VPN, continue later with split tunneling guidance.
- Check that your system clock is correct (automatic time is usually the safest choice).
Check Zoom Service Status
If Zoom is experiencing an incident, your local fixes may not change the outcome. A fast verification is to open the official status page and confirm that core components are operational. This is especially helpful when multiple devices fail on different networks at the same time.[✅Source-2]
A Simple Interpretation
- If the status page shows an active incident for meetings or sign-in, expect intermittent failures until it is resolved.
- If the status page is normal, focus on your path to Zoom: network rules, proxy, VPN, or local firewall.
Verify Network and Firewall Access
On many networks, Zoom needs specific outbound ports and allowed destinations. If a firewall or security gateway blocks them, Zoom can show Error Code 104124 even though normal browsing works. The official Zoom firewall and proxy guidance includes ports, protocols, and destination patterns for Meetings and Webinars.[✅Source-3]
For most environments, the practical goal is: allow Zoom to reach its services over TCP 443 and allow real-time media over UDP where possible. If UDP is blocked, Zoom may still connect on TCP, but it can be less stable depending on the network.
| What You Check | Why It Matters | What To Do |
|---|---|---|
| Outbound TCP (especially 443, plus Zoom meeting ports used by your environment) | Zoom sign-in and meeting setup rely on reliable TCP paths | Confirm your firewall allows Zoom-related outbound traffic and return connections |
| Outbound UDP (real-time media) | Audio/video flows work best when UDP is not blocked | If blocked by policy, ask IT whether Zoom UDP ranges can be enabled |
| Allowed destinations like *.zoom.us and *.zoom.com | Some gateways block by domain category even when ports are open | Allow-list Zoom domains on web filters, SSL gateways, and DNS filters |
| Captive portal Wi-Fi (hotel, airport, guest networks) | Until you complete the portal login, Zoom can look “offline” | Open a browser, complete the portal step, then retry Zoom |
Windows Fix Path
On Windows, the most reliable approach is to confirm Zoom is allowed as an application (not by opening random ports). Microsoft documents the process for allowing an app through Windows Defender Firewall, including where the setting lives in Windows Security.[✅Source-4]
Step-By-Step Checks
- Open Windows Security → Firewall & network protection → Allow an app through firewall.
- Find Zoom (often listed as Zoom or Zoom Workplace) and allow it on the network type you use (Private/Public).
- If Zoom is not listed, use Allow another app and point to the installed Zoom executable.
- Temporarily disconnect from VPN for a test. If Zoom works without VPN, the fix is usually routing or inspection on the VPN path.
- If you are on a managed network, check whether a proxy is set at the system level. A proxy that blocks or rewrites traffic can trigger 104124.
A Practical Rule
If Zoom starts working the moment you change networks, treat it as a network policy issue rather than a Zoom installation issue. That single test saves a lot of time and keeps troubleshooting targeted.
macOS Fix Path
On macOS, Zoom may be affected by Firewall and network-level settings. Apple documents where Firewall settings live and how to manage allowed incoming connections. This is useful if Zoom is being silently blocked on your Mac while other apps are fine.[✅Source-5]
Clean, Safe Checks
- Open macOS Firewall settings and confirm it is not set to block incoming connections for Zoom-related apps.
- If you have security software that includes web filtering, try a single test with it paused (only for a short check), then revert. The goal is to confirm causality, not to keep protections off.
- Try a different network once. If Zoom works on a hotspot, prioritize network allow-listing over reinstalling.
Proxy and VPN and Inspection Notes
If your network uses a proxy, a common cause is SSL/TLS inspection or a proxy path that is not designed for real-time traffic. Zoom’s technical guidance highlights that packet inspection and SSL/TLS inspection can introduce delay and impact connectivity, and it also describes VPN split tunneling as a way to prevent degraded Zoom media and overloaded VPN paths.[✅Source-6]
When you suspect proxy involvement, focus on one question: does Zoom traffic go direct to the internet, or is it forced through a proxy gateway? Forcing Zoom through a strict proxy can trigger 104124 during sign-in or meeting join.
What To Ask IT For (If You Are Not an Admin)
- Confirm whether Zoom domains are allow-listed on web filters and DNS filters.
- Confirm whether Zoom is excluded from SSL/TLS inspection rules.
- If VPN is mandatory, ask whether split tunneling is available for Zoom traffic.
On macOS specifically, Apple documents where to view and change system proxy settings. If you are on a managed network, the correct proxy values may be required; if you are on a personal device, an unintended proxy setting can be removed.[✅Source-7]
Clean Reinstall and Reset
If network tests look normal and the issue persists on multiple networks, a clean reinstall is the next reasonable step. Zoom’s troubleshooting guidance includes uninstalling and reinstalling the app as a standard fix path when joining fails, and it also points to CleanZoom for a full removal on Windows before reinstalling.[✅Source-8]
A Reliable Reinstall Sequence
- Sign out of Zoom (if the app opens) and fully quit it.
- Uninstall Zoom from your system.
- Restart your device to clear leftover background components.
- Install the latest Zoom app version, then test on a known-good network (a hotspot is ideal for one test).
Admin-Ready Details
If you need to hand this to IT, a short, precise note gets faster results. Keep it observable and include the minimum technical context that matters for 104124: connectivity to Zoom services, firewall rules, proxy behavior, and VPN routing.
Copy-Friendly Checklist For IT
- Issue: Zoom Error Code 104124 (connectivity to Zoom services fails).
- Scope: happens on this device on this network; confirm whether it works on hotspot.
- Network controls present: proxy, SSL inspection, DNS filtering, VPN, web gateway (yes/no).
- Request: validate outbound access for Zoom ports/protocols and allow-list Zoom domains; confirm whether Zoom is exempt from SSL/TLS inspection.
A Quick Symptom Map
| Symptom | Most Likely Area | Best Next Test |
|---|---|---|
| Works on hotspot, fails on office Wi-Fi | Firewall / proxy / filtering | Ask IT to verify Zoom allow-listing and inspection exceptions |
| Fails only when VPN is on | VPN routing or inspection | Test without VPN; request split tunneling if required |
| Fails on every network, even hotspot | Local device stack or install state | Clean reinstall, then test on hotspot again |
| Fails right after network security changes | Policy update | Roll back the specific rule change or exempt Zoom traffic |
FAQ
Does Zoom Error Code 104124 mean my internet is down?
Not always. The code usually indicates Zoom-specific connectivity trouble. You can have normal browsing while Zoom fails because a firewall, proxy, VPN route, or filtered network blocks the connection path Zoom needs.
Why does it work on a mobile hotspot but not on my Wi-Fi?
This is one of the clearest signals of a network policy difference. Guest Wi-Fi and corporate Wi-Fi often apply web gateways, DNS filters, or proxy routing that can interfere with Zoom domains and required ports.
Should I open ports manually to fix 104124?
Prefer allowing Zoom as an application in your firewall rather than opening broad ports. In managed environments, ask IT to apply Zoom’s official firewall guidance so access remains controlled and consistent.
Can a proxy or SSL inspection cause Error Code 104124?
Yes. Some proxies and SSL/TLS inspection policies can disrupt secure handshakes or add latency. The most effective fix is usually an inspection exception for Zoom traffic, paired with correct allow-listing.
If Zoom status is normal, what should I test next?
Run one clean network swap test: try a hotspot. If Zoom connects there, prioritize network rules (firewall, proxy, VPN). If it fails everywhere, treat it as a device-side issue and proceed to a clean reinstall.
When is a clean reinstall worth doing?
When the issue persists across multiple networks, or after system changes that may have altered Zoom components. A clean reinstall can restore a stable baseline without needing risky system tweaks.