How to Fix “502 Error” in Google Meets?

The “502. That’s an error” message appears in Google Meet when the page cannot load or refresh while you are trying to join or stay in a meeting. This error is called a Bad Gateway error, which means one server received an incorrect response from another server.

502 Error in Google Meets
502 Error in Google Meets Fix

The most common reason for this issue is a temporary problem with Google’s servers. However, it can also happen because of problems with your browser’s cache, issues with your internet settings (such as DNS misrouting), or strict firewall settings.

Below, you will find a step-by-step guide to troubleshooting and resolving this error.

1. Check for a Server Issue

When troubleshooting this issue, the best first step is to check whether Google is currently experiencing a server-side problem. 

Historically, widespread occurrences of the 502 error with Google Meet have been closely tied to Google server outages.

To confirm this, you can use services such as Down Detector, Services Down, or Is It Down Right Now

Checking for a Server issue
Checking for a Server issue

Note: Review the reports and check if other users are currently experiencing issues with Google Meet. Explore the social media feeds on these pages for updates about the 502 error. 

2. Restart or Reset Your Router

A simple router restart can resolve many network-related issues, including 502 errors, without affecting your Wi-Fi settings or login credentials.

Note: Restarting your router will clear temporary network data and cache, which may help re-establish a fresh connection to Google Meet. 

To restart your router, look for a restart button on your device (do not confuse this with a reset button). Press it once, and allow your router time to reboot. 

If your router does not feature a dedicated restart button, press the ON/OFF button to power off your device, then unplug the power supply and wait for a full minute. 

Important: Waiting for a minute ensures the power capacitors are fully discharged, eliminating any residual or temporary data that could affect your network connection upon restart. 

Restarting the router
Restarting the router

Note: Do not press the RESET button unless necessary, as this will restore your router to factory settings.

If restarting your router does not resolve the 502 error, consider resetting your router. Please note that this will restore all settings to their factory defaults, including personalized Wi-Fi names and passwords.

To reset your router, press and hold the reset button for at least 10 seconds. Consult your router’s manual for specific instructions; a pointed object may be needed to access the reset button. Upon reset, all LEDs will typically blink.

Resetting the router
Resetting the router

3. Change DNS to Google 

The 502 error may occur if your Internet Service Provider uses less reliable Level 3 nodes for DNS resolution. Switching to Google Public DNS often provides improved reliability and may resolve connectivity issues.

We recommend configuring both IPv4 and IPv6 DNS settings to point to Google’s DNS servers for optimal compatibility.

Note: Although Google Meet primarily uses IPv4, updating IPv6 settings ensures maximum compatibility with other services.

  1. Press the Windows + R keys to open the Run dialog box. 
  2. Type “ncpa.cpl” and press Enter to open the Network Connections window.
    Access the Network Settings menu
    Access the Network Connections menu
  3. Right-click on Wi-Fi (Wireless Network Connection) or Ethernet (Local Area Connection), depending on your connection type.
  4. Select Properties.
    Accessing the Properties menu
    Accessing the Properties menu
  5. In the Networking tab, scroll through the list named This connection uses the following items.
  6. Select Internet Protocol Version 4 (TCP/IPv4), check the box next to it if necessary, then click Properties.
    Accessing the Properties screen of IPv4
    Accessing the Properties screen of IPv4
  7. Enter 8.8.8.8 as the Preferred DNS server and 8.8.4.4 as the Alternate DNS server.
  8. Repeat these steps for Internet Protocol Version 6 (TCP/IPv6), setting the Preferred DNS server to 2001:4860:4860::8888 and the Alternate DNS server to 2001:4860:4860::8844.
  9. Restart your PC and attempt to open Google Meet again.

4. Clear Browser Cache & Cookies

If you only encounter the 502 error in Google Meet when using a particular browser, try accessing the service in a different browser (such as Firefox or Edge). If the error does not occur there, your current browser may have corrupted cache or cookie data.

Clearing your browser’s cache and cookies can resolve this issue. Please refer to our comprehensive guide on clearing the cache & cookies on any Windows browser for step-by-step instructions. 

Clearing Cookies on any browser
Clearing Cookies on any browser

After clearing cache and cookies, restart your PC and relaunch the browser to check if Google Meet functions correctly.

5. Flush DNS Cache and Reset Winsock

If you’re still encountering the 502 error after switching to Google’s DNS servers, your local resolver cache may be corrupted. Flushing the DNS and resetting the Winsock catalog can resolve connection problems caused by outdated or broken TCP/IP settings.

  1. Press Windows + R to open the Run dialog box.
  2. Type “cmd”, then press Ctrl + Shift + Enter to launch Command Prompt as administrator.
  3. In the Command Prompt window, type the following command and press Enter:
    ipconfig /flushdns
  4. Next, type the following command and press Enter to reset the Winsock catalog:
    netsh winsock reset
  5. After both commands execute successfully, restart your PC.

Note: This will clear cached DNS entries and reset your TCP/IP stack to default settings, which may fix hidden network misconfigurations that prevent access to Google Meet. 

6. Reset Windows Firewall Settings (if applicable)

A misconfigured or overly restrictive Windows Firewall can sometimes block access to Google Meet servers, causing error 502. This is especially likely if you encounter this error across all browsers.

Note: Follow these steps only if you are using Windows Defender and have previously created custom firewall rules, as such customizations can inadvertently block internet access for certain services.

  1. Press Windows + R to open the Run dialog.
  2. Type “firewall.cpl” and press Ctrl + Shift + Enter to run the Windows Defender Firewall as an administrator.
    Access the Firewall component
    Access the Firewall component
  3. Select Yes at the User Account Control prompt.
  4. In the Windows Firewall window, click Restore Defaults from the sidebar.
    Restore firewall defaults
    Restore firewall defaults
  5. Confirm your action by selecting Yes. The firewall will now revert to its default settings.
  6. Restart your PC and check whether you can access Google Meet without encountering the 502 error.

7. Disable or Uninstall Third-Party Firewalls (if applicable)

Third-party antivirus and firewall software, such as Norton or Comodo Antivirus, may block connections to cloud-based services due to false positives, resulting in a 502 error.

  1. Temporarily disable it using the tray icon or within the application’s settings.
  2. Reboot your computer, then try to access Google Meet.
Disable the firewall
Disable the firewall

Important: Some firewalls enforce network rules even after real-time protection is disabled. If you have set up custom firewall rules, the restriction may persist unless the software is completely uninstalled.

If disabling the firewall does not resolve the issue, completely uninstall it as follows:

  1. Press Windows + R, type “appwiz.cpl”, and press Enter to open the Programs and Features window.
    Open the Program & Files menu
    Open the Program & Files menu
  2. Locate the third-party firewall or antivirus suite in the list.
  3. Right-click it and choose Uninstall.
    Uninstall 3rd party firewall
    Uninstall 3rd party firewall
  4. Follow the prompts to complete the uninstallation and restart your computer.

8. Disable Proxy or VPN Service (if applicable)

Proxy servers and VPN clients are additional third-party components that may prevent Windows from successfully connecting to Google Meet servers. Disabling or uninstalling these services can help determine whether they are causing the issue.

8.1. Disable Proxy Server

If a proxy server has been set up locally, you can disable it through the Settings menu.

  1. Press Windows + R to launch the Run box.
  2. Type “ms-settings:network-proxy” and press Enter to open the Proxy settings.
    Open the Proxy component
    Open the Proxy component
  3. Locate the Manual Proxy Setup section.
  4. Uncheck “Use a proxy server” to disable the proxy.
    Disable the proxy component
    Disable the proxy component
  5. Restart your computer and try accessing Google Meet again.

8.2. Disable VPN Client

Disabling a VPN depends on whether you use a stand-alone app or Windows’ built-in VPN settings.

Note: If you use a standalone VPN app, disconnect from the VPN within the application interface.

  1. Press Windows + R to open the Run dialog.
  2. Type “ms-settings:network-vpn” and press Enter to access the VPN settings.
    Access the VPN connection menu
    Access the VPN connection menu
  3. Select your VPN connection from the right pane.
  4. Click Remove to disconnect and uninstall the VPN configuration.
    Disable the VPN suite
    Disable the VPN suite
  5. Once disabled, restart your device and try accessing Google Meet.
ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.