Zoom Error Code 1142 appears when you try to join a meeting and Zoom decides your current location is not allowed for that session. It is not a camera or audio bug; it is an access rule that gets evaluated before you enter.
Shows Up When
Joining A Meeting
Core Reason
Region/Country Not Allowed
Who Can Fix It
Host Or Zoom Admin
Keep In Mind Error 1142 is typically caused by either a host-enabled region allow/block rule or a network path that makes your connection look like it originates elsewhere.
Fixing it is mostly about identifying which rule is being triggered and then matching the meeting’s allowed regions with your real egress location.
Table Of Contents
What Error Code 1142 Means
Error Code 1142 indicates that Zoom is blocking entry because the meeting is not accessible from your current country/region, or because the host has restricted the meeting to participants from selected locations. This check happens at join time, so you can see it even if the meeting ID and passcode are correct.[✅Source-1]
- It is access control, not a device crash.
- It can be intentional (host policy) or accidental (your network appears to be elsewhere).
- You cannot override it as an attendee without a change on the host/admin side.
Why It Happens In Real Life
Cause 1: Host Or Account Uses Region Rules
If the host enabled Approve/Block Entry By Region, Zoom evaluates your join request against that list. The same setting can be enabled at account, group, or user level, and it can also be locked so hosts can’t change it.
Cause 2: Your Network Looks Like Another Location
A VPN, a corporate proxy/SASE gateway, or even a mobile carrier route can make your public IP appear to be in a different region than your physical device.
Zoom determines your region using your IP address, not your device GPS. That detail matters because it explains why switching from home Wi-Fi to mobile data can instantly change the outcome for the same meeting link.[✅Source-2]
Hosts often use this feature to reduce unwanted attendance. Zoom itself describes this as a geofencing control that can block unexpected joins from VPNs or outside the expected area.[✅Source-3]
Fast Diagnosis Without Guesswork
The fastest way to troubleshoot Error 1142 is to test whether the restriction follows your network or follows the meeting itself.
| Signal | What It Usually Points To | Best Next Check |
|---|---|---|
| Works on mobile data, fails on Wi-Fi | Corporate/ISP egress is mapped to a restricted region | Disable VPN/proxy, try a different Wi-Fi |
| Fails on every network and device | Host/account restriction likely blocks your region | Ask host to review region allow/block setting |
| Only this one meeting fails | Meeting-specific policy is stricter than others | Host checks the meeting’s security options |
| Many users from same office fail | Shared egress IP is the trigger | IT checks corporate egress and inspection |
One simple test: try joining from a second network (mobile hotspot is enough). If the error disappears, the meeting is not “broken”; your original network path is being classified differently.
Fixes For Attendees
As an attendee, your goal is to make sure Zoom sees the join request from your actual region and to collect clean information for the host if a policy change is needed. Keep each step short, then retest the meeting link.
- Turn Off VPN and any “secure browsing” features that route traffic through another location. If you are on a managed corporate device, confirm whether a system-wide proxy is always on.
- Switch Networks: try mobile data, a different Wi-Fi, or a wired connection. If one path works, you’ve isolated the issue to egress location.
- Try Another Zoom Entry Point: desktop app vs web client vs mobile app. This is not a “fix” by itself, but it confirms whether the problem is account/session based or network based.
- Message The Host With Useful Details: your approximate region (not your exact address), whether VPN was on, whether mobile data worked, and the time of the attempt. This makes it easy for the host to adjust the allow/block list.
What To Send The Host (Copy-Friendly)
- Meeting ID and the time you tried to join (include time zone).
- Network Type (home Wi-Fi, office Wi-Fi, mobile data).
- VPN/Proxy Status (on/off; corporate gateway name if you know it).
- Result Differences (example: “works on mobile data, fails on office Wi-Fi”).
Fixes For Hosts and Admins
If you host the meeting (or administer the account), you can resolve Error 1142 by adjusting the Approve or Block Entry setting and choosing the correct allow/block mode for your meeting’s audience.
Two safe patterns work well in practice:
- Allow List: best when the audience is clearly limited to a few regions.
- Block List: best when you want broad access but need to exclude a small set of locations.
- Check Scope First: determine whether the rule is set at account, group, or user level. If the toggle is grayed out, it is locked at a higher level.
- Select Allow Or Block Mode, then add the needed countries/regions in the list and save.
- Retest With The Attendee on the same network that previously failed, so you confirm the policy matches real join conditions.
Zoom documents the steps to enable or disable this control at the account, group, and user levels, including the option to lock it so it can’t be changed by others.[✅Source-4]
Corporate Network Notes That Often Explain “Random” 1142 Errors
In offices, many users share a single public IP through a firewall, proxy, or secure web gateway. If that egress IP is associated with an unexpected region, Zoom’s location check can fail for everyone on that network, while the same people succeed instantly on mobile data.
- TLS/SSL inspection or web filtering can route traffic through centralized gateways.
- Split tunneling settings can send Zoom traffic through a different exit than normal browsing.
- Proxy auto-config (PAC) may apply only to some apps or some domains.
Zoom provides detailed guidance for configuring firewall and proxy environments, including required domains and ports. This is the right reference for IT teams when Zoom access behaves differently across networks.[✅Source-5]
When It Still Fails After Host Changes
If the host confirmed the meeting’s region settings are correct, yet attendees still see Error 1142, focus on reproducible evidence. A clean, repeatable test case is more useful than repeated reinstall attempts, because this error is driven by join classification, not local files.
Zoom’s Network Connectivity Tool can help identify detected proxy connections and export logs that are relevant for troubleshooting, making it easier to confirm what the client sees on your network.[✅Source-6]
If you involve IT or support, share the smallest set of facts that can be verified: meeting ID, time of test, network type, VPN status, and whether a second network succeeds. That combination usually isolates whether the root is policy or egress.
In rare situations, access can be unavailable from certain locations due to regulatory requirements. If your tests suggest a broader access limitation that is not meeting-specific, Zoom’s official note on regional availability is the right starting point for confirming whether a location is supported.[✅Source-7]
FAQ
Is Error Code 1142 A Password Or Meeting ID Problem?
No. 1142 is evaluated after Zoom recognizes the meeting but before it lets you in. It indicates a location-based entry restriction, not an incorrect passcode.
Why Does It Work On Mobile Data But Not On Office Wi-Fi?
Your office network likely exits the internet through a shared gateway. Zoom’s location check is based on public IP, so the office egress can be mapped differently than your mobile carrier.
Does Zoom Use GPS To Decide My Country/Region?
Zoom’s region decision for this feature is tied to IP-based location. That is why VPNs, proxies, and centralized gateways can change outcomes even when your device stays in the same place.
Can The Host Allow One Person Without Opening The Meeting To Everyone?
Yes, in most setups the host/admin can adjust the allowed countries/regions list so it includes the attendee’s region while keeping the rest of the policy intact. The cleanest approach is to add only what is needed and then retest with that attendee.
Should I Use A VPN To Fix 1142?
A VPN often makes 1142 worse because it changes where your traffic appears to originate. If the meeting is restricted by region, the correct fix is a host/admin setting change or using an approved network path, not trying to bypass restrictions.
What Is The Most Helpful Evidence For Support Or IT?
Provide meeting ID, exact test time, the network you used, VPN/proxy status, and whether a second network works. If available, export diagnostics from the client so investigators can see proxy detection and network path details.