Error Code 104111 usually appears when the Zoom desktop or mobile app can’t complete a connection to Zoom services. That connection can fail for simple reasons (a temporary network glitch) or for more structured reasons (a firewall rule, proxy, or security gateway that blocks the required traffic). The good news: with a few targeted checks, you can pinpoint whether the issue is service-wide, network-based, or device-specific—and fix it without guesswork.
Most Common Message
You may see text like “Can’t connect to our service” or a repeating connecting screen. In practice, this is Zoom telling you the app can’t reliably reach the servers it needs to join a meeting.
What The Code Points To
Error codes in the 104101–104118 range (including 104111) are listed by Zoom as connectivity issues with Zoom servers. [✅Source-1]
Table of Contents
What Error Code 104111 Means
Zoom needs to establish several outbound connections to join meetings, authenticate, and exchange audio/video. Error Code 104111 appears when the app can’t complete those connections. In many environments, the underlying cause is a network control: a firewall, proxy, or web security gateway that blocks Zoom traffic or changes it in a way the app can’t use.
A practical translation: If the Zoom app is stuck on Connecting, times out, or shows “Can’t connect to our service,” Zoom highlights three likely areas: network connection, network firewall settings, or web security gateway settings. [✅Source-2]
The Fastest Way To Narrow It Down
You will get to the right fix faster if you separate global service status from your local setup. Start with this sequence.
- Check Zoom’s cloud status first. If there is an active incident, local troubleshooting can look “random” even on a healthy device. [✅Source-3]
- Try joining the same meeting in two ways:
- Zoom desktop app
- Browser/web join (if available for your meeting)
- Switch networks briefly. If it fails only on one network (office Wi-Fi, school network), you likely need a network rule adjustment. If it fails everywhere on the same device, focus on local settings and a clean reinstall.
A Simple Diagnostic Table
| What You Observe | What It Usually Means | Most Relevant Fix |
|---|---|---|
| Desktop app fails with 104111, browser join works | App traffic is being filtered, inspected, or blocked; browser traffic is taking a different allowed path | Run the Network Connectivity Tool, then review firewall/proxy behavior |
| Fails only on one Wi-Fi/network | Network firewall/proxy rules need adjustment for Zoom | Apply the ports and proxy guidance under “Network Rules” |
| Fails on every network for one device | Local firewall/security software rule or a damaged install/cache | Allow Zoom in the firewall, then reinstall if needed |
| Fails on public Wi-Fi, works on mobile data | Captive portal or restricted network policy | Open a browser to complete Wi-Fi sign-in, or switch networks |
Network Rules That Commonly Block Zoom
This is where many guides stay too vague. If you (or your IT team) manage a firewall, proxy, or secure web gateway, the exact ports and behaviors matter. If only “turn it off” advice has been tried, a precise allow rule is usually the cleaner path.
Ports And Protocols Worth Checking
Zoom publishes specific firewall and proxy guidance, including common requirements for web access (TCP 80/443) and for meetings/webinars (including TCP 443 and UDP ranges used for real-time media). If UDP is blocked, the desktop app may struggle to establish the path it prefers, especially on managed networks. [✅Source-4]
- On managed networks, ask for outbound rules to be reviewed first (Zoom calls out outbound traffic behavior in its firewall guidance).
- If there is a “web filter” or “security gateway,” confirm Zoom is not being categorized in a restrictive policy.
- If meetings connect but audio/video fails later, that often points to real-time media being restricted (not just basic web access).
Proxy, SSL Inspection, And Secure Gateways
Zoom notes that if your app is stuck connecting or shows “can’t connect,” the cause can be firewall settings or web security gateway behavior. A common trigger is SSL inspection (sometimes called HTTPS inspection) on corporate networks. If inspection breaks the app’s expected TLS behavior, the desktop client may fail even when a browser appears fine.
- Confirm whether your network performs SSL inspection on app traffic.
- If it does, request an exception for Zoom’s domains per your organization’s security policy (many environments treat “bypass inspection for trusted conferencing traffic” as a standard exception pattern).
- If a proxy is required, verify the Zoom app is using the correct proxy method and credentials, not an outdated or inherited setting from another profile.
Run The Zoom Network Connectivity Tool
This is one of the most efficient ways to move from “try random fixes” to actionable evidence. Zoom provides a built-in Network Connectivity Tool that runs tests and reports results for network info, traceroute-style checks, and service connectivity.
How To Open It And What To Look For
- Open the Zoom desktop app on Windows or macOS.
- Use the built-in shortcut to open diagnostics:
- Windows: Ctrl + Alt + Shift + D
- macOS: Cmd + Option + Shift + D
- Run the Smart Test (Network Test). Review:
- Network Information (adapter/IP/proxy detection)
- MTR (path quality toward Zoom services)
- Service Status connectivity checks
- If you’re working with IT or Support, use the tool’s export option so you can share a clear log instead of describing symptoms.
Zoom documents these shortcuts, test types, and the sections the tool reports (including Service Status checks and exporting logs). [✅Source-5]
Windows Fixes That Keep Security Intact
On Windows, the most reliable approach is to allow the Zoom app through the firewall rather than turning protection off. This keeps your system’s baseline security while removing a block that can trigger 104111.
Allow Zoom In Microsoft Defender Firewall
- Open the Windows Security app.
- Go to Firewall & network protection.
- Select Allow an app through firewall, then Change settings.
- Find Zoom and allow it on the appropriate network types (Private/Public) for your environment.
- If Zoom is not listed, use Allow another app and point to the Zoom executable path.
Microsoft describes adding an app to the allowed list as the safer method compared to opening ports, and outlines the same navigation flow above. [✅Source-6]
If It Works In Browser but Not In The App
When the browser join works but the desktop app shows 104111, treat it as a strong hint that something is filtering app-originated traffic. In addition to firewall allow rules, check for these common patterns:
- Security suites with “web shield” or “encrypted traffic scanning” features that apply to apps.
- VPN or corporate proxy clients that route only some traffic through a tunnel.
- Multiple network adapters (Ethernet, Wi-Fi, virtual adapters) where the app binds to a restricted path.
macOS Fixes That Keep Security Intact
On macOS, Firewall settings can block app connections depending on how strict the configuration is. The goal is not to weaken your setup, but to ensure Zoom is not being treated as an app that should be blocked from network access.
Check Firewall Settings And App Allow List
- Open System Settings on your Mac.
- Go to Network and open Firewall settings.
- If Firewall is on, open Options and confirm Zoom is not blocked.
- Avoid enabling “block all incoming connections” unless you specifically need it for your environment; it can interfere with apps that expect inbound responses on certain paths.
Apple documents where to find Firewall settings, what “Block all incoming connections” does, and how to add or remove an app from the allowed list. [✅Source-7]
Mobile And Tablet Checks
On iOS and Android, Error Code 104111 still points to connectivity. The difference is where the block usually lives: mobile networks, Wi-Fi restrictions, or device-level VPN/profile rules.
- Switch Wi-Fi to mobile data (or the reverse). If one works reliably, the issue is usually a network policy on the failing connection.
- Check for a captive portal on Wi-Fi. Open a browser and confirm you can load a normal webpage; some networks require a sign-in page first.
- Temporarily disable VPN profiles if your organization allows it for testing. Some VPN routes block or reshape real-time traffic.
- Update the Zoom app and restart the device to reset network state cleanly.
When Reinstalling Is Worth It
If multiple networks fail on the same device, and firewall rules look correct, reinstalling can be a high-value step—especially if a local configuration file, cached data, or a partially updated component is causing the app to misbehave.
A Clean Reinstall Path
- Uninstall Zoom fully.
- Install the latest version from the official download center.
- Try joining by manually entering the meeting ID and passcode (this avoids link-handling edge cases).
Zoom’s troubleshooting guidance for joining meetings includes uninstall/reinstall and manually entering the meeting ID and passcode as standard steps. [✅Source-8]
FAQ
What does Zoom Error Code 104111 indicate?
It indicates the Zoom app can’t complete connectivity to Zoom services. It is commonly associated with network restrictions (firewall, proxy, or secure web gateway) or local security rules that prevent the app from reaching required Zoom endpoints.
Why can the browser join work while the Zoom desktop app fails?
Browsers and desktop apps can take different network paths and can be treated differently by security tools. If the desktop app is blocked by a firewall rule, an inspection gateway, or a security suite that filters app traffic, the browser may still succeed while the app fails with 104111.
What should I check first before changing firewall settings?
Check whether Zoom is experiencing a service incident, then try joining the same meeting from a different network. If it only fails on one network, the fix is usually a network rule adjustment. If it fails on all networks for one device, focus on local firewall/security rules or reinstall.
What information helps IT or Support resolve 104111 faster?
Exported results from Zoom’s Network Connectivity Tool (including proxy detection, traceroute/MTR results, and service connectivity checks) plus the network name (home/office), whether browser join works, and whether the issue is limited to one device or affects multiple devices.
Is disabling the firewall a good idea for testing?
A safer method is to allow the Zoom app through your firewall rather than turning protection off. That approach tests whether the firewall is the blocker while keeping a more controlled security posture.