For some users, the error happens sporadically, while others report that this issue occurs every time they attempt to launch Google Meet. The following error mostly appears due to an issue with the origin server. The most common causes include an unresolvable domain name, cached data, a change to the DNS server, a network inconsistency, an improper firewall configuration, misconfigured proxy or VPN client, or some script interference. Here’s a list of methods that will help you troubleshoot the issue.
1. Check for a server issue
If you’re beginning to troubleshoot the issue, the ideal way to start is by checking if Google is currently dealing with a server issue. In the past, widespread cases of the 502 error with Google Meed were almost always caused by a Google server outage. You can investigate this possibility using services like Down Detector, Services Down, or Is It Down Right Now. Note: Check both directories and see if other users currently report issues with Google Meet. Scroll down to the Social Media feed and see if any affected users face the same 502 error code. If your investigation has not revealed any Google server issue beyond your control, move down to the next method below.
2. Restart or reset the router
With a simple router restart, you can reset your network’s parts without changing your login information or other settings. Note: This procedure will only clear temporary files without touching anything else. To initiate a router restart, see if your router model has a dedicated restart button (don’t confuse it with reset). Press it once and wait for your router to restart. If your router doesn’t have a dedicated restart button, press the ON/OFF button once to cut off the power, then unplug your router’s power cord and wait for a full minute. Important: Disconnecting your router from the power supply and waiting for a minute is important because it allows the power capacitors to discharge ensuring that no temporary data is used at the next startup. Note: Don’t press the RESET button, as that will start the process of resetting the device. If you’ve already restarted your router and the 502 error still occurs when accessing Google Meet, you can try to reset your router. But note that this process will also reset your modem’s custom credentials and default address. Even more, both your username and password will be changed back to admin. To initiate a router reset, press and hold the reset button for at least 10 seconds. Note: Depending on the model of the router, you may need a small, pointed tool (or a needle) to get to the reset button. When the process is done, all the LEDs on the router will start to blink at once. If you have already tried both the reset and the restart procedure and the issue is still not fixed, move down to the next method below.
3. Change DNS to Google
502 Google Meet error appears for people with Internet access from an ISP using Level 3 nodes. You will eventually run into issues like this unless you migrate to a more stable DNS Range. Our recommendation to avoid this issue is to use the DNS server provided by Google. Note: Even though Google Meet uses IPv4, we’ll show you how to adjust your IPv6 DNS range to Google’s equivalents to avoid getting this issue with other applications. Here’s what you need to do: If you still see the 502 error when opening Google Meet, move down to the next method.
4. Clear browser cache & cookies
In case you only experience this problem with Google Meet, try using the application on a different browser. If you see this error on Chrome, use Firefox, Edge, or any other browser to check if the 502 error still occurs. If Google Meet doesn’t display the 502 error on any other browser, it’s very likely that you are experiencing this issue due to saved cache and cookie data. Refer to our guide on clearing the cache & cookies on any Windows browser for detailed instructions. Once you clear the cache and all cookies related to Google Meet, reboot your PC and relaunch your browser to see if the 502 error is now fixed. If the issue is still not fixed, move to the next method below.
5. Reset Windows Firewall Settings (if applicable)
Another scenario that might prevent your PC from connecting to the Google Meet server is an inconsistent firewall. This is likely if you get the same kind of issue regardless of the browser that you’re using. Note: Only follow this method if you are using the default security suite (Windows Defender + Windows Firewall). DO NOT skip this method if you previously established custom firewall rules that might have affected communications between your browser and external servers. If you are using the default Windows Firewall settings and have modified the default settings, you might be able to fix the 502 error by reverting the built-in firewall to the default. Here’s what you need to do: If the issue is still unresolved, move to the next method below.
6. Disable / Uninstall 3rd party firewall (if applicable)
If you’ve come this far without a resolution and are using a 3rd party antivirus, you should investigate and see if it’s responsible for terminating the connection with the Google Meet server. A series of overprotective suites might indirectly cause the 502 error as they terminate the connection with a cloud app server due to a false positive. Norton and Comodo Antivirus are two frequent AV suites known to cause this issue. To verify whether a 3rd party suite is causing the issue, start by attempting to disable it – most 3rd party security suites will allow you to do this directly from the tray bar icon. Once the firewall is disabled, reboot your PC and open up Google Meet again to see if the problem is now fixed. Important: With certain firewalls, network-specific rules will remain in place even after you disable the real-time protection. So if you previously configured your firewall to disallow certain communications with external servers, there’s a likelihood that this role will be upheld after you disable the firewall protection. If this scenario is applicable, follow the instructions below to uninstall the 3rd party firewall and see if the 502 error stops occurring. Here’s what you need to do: If the 503 error is still occurring, move on to the final solution below.
7. Disable Proxy or VPN service (if applicable)
A proxy or VPN client is another 3rd party component that could stop your Windows end-user version from communicating with Google Meet servers. Most of the time, this problem was caused by a VPN client or a proxy server set up on Windows itself. If your situation is like the one above, try uninstalling your VPN client or turning off the Proxy server. We made two guides to cover both of these situations, so choose the one applicable to you.
7.1. Disable VPN client
If you have already set up a proxy server locally, you can easily turn it off by going to the Settings menu and clicking on the Proxy tab. Here’s what you need to do:
7.2 Disable Proxy Server
Turning off a VPN service on a Windows computer depends on whether it was set up natively or with a separate program. Note: If you are using a stand-alone app, you must go to the VPN interface and end the connection. If you set up your VPN using the built-in feature, on the other hand, follow the steps below to turn it off:
Google Rolls Out New Google Assistant “Snapshot”: A Revamped Version of Google…Google Adds Background Blur & Replace To Its G Suit Video Client, “Google…Google Makes Testing and Integration of Google Pay With Test Suite API That…Fix: ERR_CONNECTION_TIMED_OUT on Google Chrome
