Zoom Error Code 104104 typically indicates a connection path problem between your device and Zoom services. The fix is usually found in your network route, a security filter, or an out-of-date app. This guide isolates the most reliable causes and walks through practical checks that restore meeting access without guesswork.
If Error 104104 appears only on one network (office, campus, hotel), that points to a firewall, proxy, or captive portal. If it appears on every network, focus on device settings and the Zoom app.
Table of Contents
What Error Code 104104 Means
Error Code 104104 belongs to a group of Zoom codes commonly associated with connectivity issues to Zoom servers. In practical terms, your app starts the connection, then something on the path blocks, redirects, or fails to complete the secure session. When this happens, Zoom may show 104104 even if your Wi-Fi looks normal and other sites load correctly.✅Source
Common On-Screen Clues
- Connecting that never finishes
- Can’t connect or network error
- 104104 right after clicking Join
Most Likely Areas
- Firewall or proxy rules
- VPN routing or split tunneling
- DNS or TLS certificate validation
A Reliable Pattern
If 104104 stops when you switch to a mobile hotspot, the root cause is usually in the original network’s policy controls or routing.
Fast Checks That Often Clear 104104
These steps are ordered to isolate Zoom-side status first, then narrow down network path and device factors. Keep each test short and clear so you can identify what changed.
- Check whether Zoom is reporting a current service incident or maintenance window. If there is an active event, wait until the status is resolved, then retry Join.✅Source
- Open a browser and confirm you can reach zoom.us without being redirected to a login splash page (common on public Wi-Fi).
- Switch networks: try a mobile hotspot or a different Wi-Fi. If 104104 disappears, treat it as a network policy issue on the original connection.
- Temporarily disconnect VPN and pause any proxy tool you control, then retry. VPN routes often change how Zoom reaches regional servers.
- Restart your Zoom app completely (quit, then reopen). If possible, also restart the router or toggle airplane mode on mobile devices to refresh routes.
- Try joining from the Zoom web app as a comparison test. If the web app works but the desktop app fails, focus on app version and local security controls.
Network And Firewall Settings That Matter
When Error 104104 is driven by a network policy, the usual culprit is blocked signaling or throttled real-time media. Zoom documents the outbound rules and port ranges commonly required for Zoom Meetings and Webinars, including TCP 443 and media-friendly UDP ranges used by clients.✅Source
| Use Case | Protocol | Ports | Why It Matters For 104104 |
|---|---|---|---|
| Web access and core signaling | TCP | 80, 443 | Required to reach Zoom domains and establish secure sessions; blocking can cause immediate connection failure. |
| Meetings and webinars signaling | TCP | 443, 8801, 8802 | If restricted, the client may fail during join/handshake and surface 104104. |
| Real-time media transport | UDP | 3478, 3479, 8801–8810 | Helps audio/video flow efficiently; harsh UDP blocks can force fallbacks and sometimes break session setup on strict networks. |
If You Rely On A Work Or Campus Network
- Ask whether SSL/TLS inspection applies to Zoom traffic. Some inspection profiles interfere with real-time collaboration and can trigger 104104.
- Confirm the environment supports UDP for media and does not force everything through a high-latency proxy chain.
- Check for allow lists that require explicit permission for Zoom domains.
DNS And Name Resolution Fixes
DNS issues can be subtle. Your device may resolve some Zoom endpoints correctly while others point to an outdated address, leading to 104104 during the connection attempt. A clean DNS refresh is a safe step because it resets name resolution without changing your account or meeting settings. Focus on repeatable tests: change one variable, retry, then move on.
Windows DNS Refresh (Local Cache)
Run a DNS flush, then retry Zoom. This is often enough when 104104 appears after switching networks or returning from sleep mode.✅Source
ipconfig /flushdnsDNS Server Swap (If The Problem Is Network-Specific)
- If 104104 happens only on one ISP or one router, test with a different DNS server (router-level or device-level) and retry the join.
- After changing DNS, restart the connection (toggle Wi-Fi off/on) so the new resolver is actually used.
System Time And Certificate Validation
A noticeably wrong system clock can prevent secure connections from completing. If certificate checks fail due to incorrect date/time, the connection may drop early and surface as Error 104104. Set your device to automatic time and ensure the correct time zone is selected. Network Time Protocol (NTP) is the common mechanism used to keep clocks aligned on networks.✅Source
- Windows: enable Set time automatically and Set time zone automatically, then restart Zoom.
- macOS: enable Set time and date automatically, then retry the meeting.
- Mobile: confirm Automatic time is on, then force-close and reopen the Zoom app.
Update Or Reinstall Zoom Workplace
An outdated client can struggle with newer connection routes, modern TLS behaviors, or network-handling fixes. In the Zoom desktop app, sign in, open your profile menu, and use Check for Updates. If updates are managed by your organization, you may need your IT team to provide a current installer. Keeping Zoom Workplace current is a low-risk step that frequently eliminates join failures tied to 104104.✅Source
When A Clean Reinstall Makes Sense
- 104104 started after an OS update or security software update.
- The Zoom app launches, but every meeting fails across multiple networks.
- The web app can join meetings, but the desktop client cannot, even after an update attempt.
Uninstall Zoom, restart the device, then install the latest Zoom Workplace version provided by your standard download channel. After reinstalling, test one meeting link and confirm the join flow completes without 104104.
Managed Networks: Proxies, Inspection, and Captive Portals
On managed networks, a successful Zoom connection depends on how packet inspection, whitelisting, and routing design treat real-time collaboration traffic. Zoom’s network guidance highlights that deep inspection or policy bottlenecks can introduce delay and interfere with signaling and media flows, which can present as meeting join failures like 104104.✅Source
Practical Checks For IT-Managed Environments
- Captive portal: confirm the device is fully authenticated (open a browser and complete any accept/continue flow), then retry Zoom.
- Proxy authentication: confirm the Zoom client is not being forced through a proxy that requires interactive credentials.
- Inspection exceptions: apply policy to avoid heavy inspection on Zoom media, especially where latency is introduced.
- Routing: avoid “hairpin” routes that send local Zoom traffic on long detours through centralized gateways.
A Simple Diagnostic Table
| Observation | Most Likely Cause Area | Next Test |
|---|---|---|
| 104104 only on office Wi-Fi | Firewall/proxy policy | Try hotspot; if it works, review ports, domains, and inspection exceptions with IT. |
| 104104 after changing networks | DNS mismatch or stale route | Flush DNS (Windows), reconnect Wi-Fi, retry join. |
| Other apps work; Zoom fails instantly | Local security filter or outdated client | Update Zoom; test web app vs desktop app; then consider reinstall. |
| Random success/failure on the same network | Unstable path or intermittent inspection | Retry at a different time; test wired connection; check VPN path consistency. |
FAQ
Is Zoom Error Code 104104 An Account Problem?
Most of the time, 104104 is a connectivity issue rather than an account restriction. If you can sign in normally but cannot join meetings, focus on network path, DNS, and client version.
Why Does 104104 Disappear On A Mobile Hotspot?
A hotspot changes your routing and bypasses local firewall or proxy policies. If the hotspot works, your original network likely applies filtering that interferes with Zoom signaling or UDP media.
Which Network Settings Are Most Often Linked To 104104?
The most common triggers are blocked TCP 443 paths, restricted UDP ranges for media, and proxy or inspection policies that add delay to real-time traffic. On managed networks, an allow list approach can also cause failures if Zoom endpoints are not permitted.
Do I Need To Reinstall Zoom To Fix 104104?
Not always. Start with status checks, a network swap, and an app restart. Reinstall is most useful when 104104 happens on every network, or when the web app works but the desktop app fails despite updating.
Can Incorrect Date And Time Really Cause 104104?
Yes, it can. If the system clock is significantly off, secure connections may fail during certificate validation. Set automatic time and the correct time zone, then retry the meeting.
How Do I Tell If It’s A Zoom Outage Or My Network?
If multiple people on different networks report failures at the same time, suspect a service incident. If the issue is isolated to one location or one Wi-Fi, suspect a local network policy. A fast way to separate the two is the hotspot test.