On managed networks, Error Code 104113 often comes from proxy rules, SSL inspection, or outbound traffic policies that do not include Zoom’s required ports and destinations. The most efficient approach is to share a clear checklist with the network administrator and test again after each change.
| Area | What To Allow (Outbound) | Why It Matters | How To Validate |
|---|---|---|---|
| Zoom Website Access | TCP 80/443 and UDP 443 to *.zoom.us and *.zoom.com | Sign-in, meeting join flows, and basic web reachability | Open zoom.us on the same network, then retry Zoom |
| Zoom Meetings Media Path | TCP 443, 8801, 8802 (plus Zoom’s published IP ranges) | Required for meeting connectivity on restrictive networks | Test joining a meeting after changes; confirm logs show allowed connections |
| Zoom Meetings Real-Time Traffic | UDP 3478, 3479 and UDP 8801–8810 (plus Zoom’s published IP ranges) | Commonly required for stable real-time connectivity | Join a meeting and verify the connection does not stick on “Connecting” |
| Proxy And Inspection | Support for HTTPS/SSL proxy via port 443; bypass zoom.us and *.zoom.us from proxy or SSL inspection when inspection breaks sessions | Inspection can interfere with certificate validation or session negotiation | Compare results: direct path vs inspected path |
Admin Tip If your policy uses IP allowlists, rely on Zoom’s published IP ranges and keep them updated. A stale allowlist can look exactly like Error Code 104113 during join attempts.
App-Level Fixes That Often Finish The Job
Once the network path looks clean, the remaining causes are often client corruption, stale components, or a local install that needs a clean refresh. The goal is to remove the app fully, then install a fresh version.
Clean Reinstall The Official Way
- Quit Zoom completely (make sure it is not still running in the background).
- Uninstall Zoom.
- On Windows, use the official cleanup tool to remove leftover components, then reinstall a fresh build.
- Retry joining by entering the meeting ID and passcode manually to avoid link-handling quirks.
Zoom documents this uninstall-and-reinstall approach for stubborn join issues, including using the cleanup utility when a standard uninstall is not enough.[✅Source-3]
Update From The Official Download Center
When you reinstall, use the official Download Center to avoid outdated installers. Keeping Zoom current reduces install mismatches that can surface as Error Code 104113 during join flows.[✅Source-4]
- Update Zoom first, then retest on the same network.
- If it still fails, do the clean reinstall (removal + fresh install).
A Simple Diagnostic Flow You Can Follow
- Check service status, then retry if there is an active incident.
- Try the same meeting on a different network (hotspot is the quickest test).
- Disable VPN and any enforced proxy, then test again.
- If a managed network is involved, ask for a quick review of firewall/proxy rules (ports and SSL inspection exceptions).
- Update Zoom. If the issue persists, perform a clean reinstall.
- If the problem happens only on one device, test with another user profile on that device (basic isolation without deep system changes).
Time Saver If switching networks fixes it instantly, focus on the network path. If switching networks does not help, focus on the app reinstall and local security software.
FAQ
Is Error Code 104113 an account problem?
Most of the time, no. Error Code 104113 usually points to connectivity to Zoom servers rather than account permissions. Start with network path checks before changing account settings.
Why does it work on mobile data but not on Wi-Fi?
This pattern strongly suggests a Wi-Fi router or network policy issue: DNS, VPN routing, filtering, proxy rules, or security gateway inspection. Treat hotspot success as a clear clue that the app itself is likely fine.
Can a proxy or SSL inspection trigger Error Code 104113?
Yes, it can. When session negotiation or certificate checks are disrupted, the Zoom client may fail to connect and surface Error Code 104113. In managed environments, exceptions for Zoom domains and a clean outbound path often restore stability.
Which ports should be open for Zoom meetings?
The exact rules depend on your environment, yet a typical baseline includes allowing TCP 443 and the Zoom meeting media ports used by your policy. If your organization uses allowlists, your network team should align ports and IP ranges with Zoom’s published requirements.
Does reinstalling Zoom really help?
It helps when the install has stale components or local corruption. A clean reinstall removes cached pieces that a standard update may keep, which can be enough to stop repeated Error Code 104113 failures.
What should I try right before an important meeting?
Use the fastest isolation steps: switch to a mobile hotspot, disable VPN, restart Zoom, then join by entering the meeting ID manually. These actions quickly separate network path issues from app issues.
Zoom Error Code 104113 is a connection-related sign that the Zoom app cannot reach the Zoom service reliably. In practice, it usually comes down to network routing, firewall/proxy rules, VPNs, DNS issues, or security software blocking the required traffic. This guide focuses on fast diagnosis and repeatable fixes you can apply on home Wi-Fi or managed networks.
If the message appears right when you click a meeting link, treat it as a connectivity path problem first. When the path is clean, Error Code 104113 typically disappears without any special account changes.
Table of Contents
What Error Code 104113 Means
What You’ll Notice
- A join attempt stalls at Connecting or fails quickly.
- The same meeting works on another network, or with a different device.
- Switching between Wi-Fi and mobile data changes the result.
What It Usually Points To
Error Code 104113 sits in a group of Zoom error codes that indicate connection problems to Zoom servers. When it appears, the most productive approach is to verify the network path (DNS, firewall, proxy, VPN, security gateway) before assuming the meeting link or your account is the issue.[✅Source-1]
Fast Checks Before Deeper Changes
Check Zoom Service Status
Start with a quick sanity check: if there is an ongoing incident, local fixes won’t help until service is stable again. Look for current incidents and maintenance updates on the official status page.[✅Source-5]
- If status is green, move on to network checks.
- If an incident is active, retry later and avoid repeated reinstalls.
Helpful Clue If Zoom works on mobile hotspot but fails on Wi-Fi, the issue is almost always the Wi-Fi network path (router DNS, VPN, firewall rules, or filtering).
Do A Clean Network Path Test
Close Zoom completely, then test the simplest path: no VPN, no proxy overrides, and a stable network connection. If you are on a managed network, Zoom recommends confirming basic reachability in a browser (for example, ensuring you can access zoom.us) and reviewing firewall or gateway settings when connectivity errors appear.[✅Source-2]
- Try a different network (home Wi-Fi → hotspot, or hotspot → home Wi-Fi).
- Switch to Ethernet if possible, even for a quick test.
- Disable VPN and any “secure browsing” web gateways temporarily to isolate the cause.
Fixes For Home Networks
Router And DNS Fixes
- Restart your modem/router, then restart your device. This resets stale routes that can trigger Error Code 104113.
- Forget the Wi-Fi network and reconnect (new DHCP lease, fresh routing).
- Change DNS to a reputable public DNS provider in your router or device settings if name resolution feels unreliable. Keep it consistent across devices for testing.
If the problem changes after DNS updates, keep the working DNS and avoid frequent switching. Stability matters more than experimentation.
VPN And Security App Checks
- Turn off VPN and try again. Some VPN routes block or reshape real-time traffic, leading to connectivity failures.
- Temporarily disable “web protection” or “HTTPS scanning” in security suites and retest. If Zoom works, add Zoom to the allowlist and re-enable protection.
- On routers with parental controls or filtering, ensure Zoom domains are not filtered.
If you prefer not to disable protection, the better long-term fix is allowlisting the Zoom app and required domains so secure browsing stays enabled without breaking meetings.
Fixes For Work Or School Networks
On managed networks, Error Code 104113 often comes from proxy rules, SSL inspection, or outbound traffic policies that do not include Zoom’s required ports and destinations. The most efficient approach is to share a clear checklist with the network administrator and test again after each change.
| Area | What To Allow (Outbound) | Why It Matters | How To Validate |
|---|---|---|---|
| Zoom Website Access | TCP 80/443 and UDP 443 to *.zoom.us and *.zoom.com | Sign-in, meeting join flows, and basic web reachability | Open zoom.us on the same network, then retry Zoom |
| Zoom Meetings Media Path | TCP 443, 8801, 8802 (plus Zoom’s published IP ranges) | Required for meeting connectivity on restrictive networks | Test joining a meeting after changes; confirm logs show allowed connections |
| Zoom Meetings Real-Time Traffic | UDP 3478, 3479 and UDP 8801–8810 (plus Zoom’s published IP ranges) | Commonly required for stable real-time connectivity | Join a meeting and verify the connection does not stick on “Connecting” |
| Proxy And Inspection | Support for HTTPS/SSL proxy via port 443; bypass zoom.us and *.zoom.us from proxy or SSL inspection when inspection breaks sessions | Inspection can interfere with certificate validation or session negotiation | Compare results: direct path vs inspected path |
Admin Tip If your policy uses IP allowlists, rely on Zoom’s published IP ranges and keep them updated. A stale allowlist can look exactly like Error Code 104113 during join attempts.
App-Level Fixes That Often Finish The Job
Once the network path looks clean, the remaining causes are often client corruption, stale components, or a local install that needs a clean refresh. The goal is to remove the app fully, then install a fresh version.
Clean Reinstall The Official Way
- Quit Zoom completely (make sure it is not still running in the background).
- Uninstall Zoom.
- On Windows, use the official cleanup tool to remove leftover components, then reinstall a fresh build.
- Retry joining by entering the meeting ID and passcode manually to avoid link-handling quirks.
Zoom documents this uninstall-and-reinstall approach for stubborn join issues, including using the cleanup utility when a standard uninstall is not enough.[✅Source-3]
Update From The Official Download Center
When you reinstall, use the official Download Center to avoid outdated installers. Keeping Zoom current reduces install mismatches that can surface as Error Code 104113 during join flows.[✅Source-4]
- Update Zoom first, then retest on the same network.
- If it still fails, do the clean reinstall (removal + fresh install).
A Simple Diagnostic Flow You Can Follow
- Check service status, then retry if there is an active incident.
- Try the same meeting on a different network (hotspot is the quickest test).
- Disable VPN and any enforced proxy, then test again.
- If a managed network is involved, ask for a quick review of firewall/proxy rules (ports and SSL inspection exceptions).
- Update Zoom. If the issue persists, perform a clean reinstall.
- If the problem happens only on one device, test with another user profile on that device (basic isolation without deep system changes).
Time Saver If switching networks fixes it instantly, focus on the network path. If switching networks does not help, focus on the app reinstall and local security software.
FAQ
Is Error Code 104113 an account problem?
Most of the time, no. Error Code 104113 usually points to connectivity to Zoom servers rather than account permissions. Start with network path checks before changing account settings.
Why does it work on mobile data but not on Wi-Fi?
This pattern strongly suggests a Wi-Fi router or network policy issue: DNS, VPN routing, filtering, proxy rules, or security gateway inspection. Treat hotspot success as a clear clue that the app itself is likely fine.
Can a proxy or SSL inspection trigger Error Code 104113?
Yes, it can. When session negotiation or certificate checks are disrupted, the Zoom client may fail to connect and surface Error Code 104113. In managed environments, exceptions for Zoom domains and a clean outbound path often restore stability.
Which ports should be open for Zoom meetings?
The exact rules depend on your environment, yet a typical baseline includes allowing TCP 443 and the Zoom meeting media ports used by your policy. If your organization uses allowlists, your network team should align ports and IP ranges with Zoom’s published requirements.
Does reinstalling Zoom really help?
It helps when the install has stale components or local corruption. A clean reinstall removes cached pieces that a standard update may keep, which can be enough to stop repeated Error Code 104113 failures.
What should I try right before an important meeting?
Use the fastest isolation steps: switch to a mobile hotspot, disable VPN, restart Zoom, then join by entering the meeting ID manually. These actions quickly separate network path issues from app issues.