Google Drive Proxy Whitelist

Whitelisting Google Drive Through a Corporate Proxy or Firewall

If Google Drive’s desktop sync client is failing to connect from inside a corporate network, the usual culprit is a proxy or firewall blocking the domains and ports the client needs to reach Google’s infrastructure.

At a minimum, make sure outbound HTTPS (443) is permitted to:

• *.google.com
• *.googleapis.com
• *.googleusercontent.com
• *.gstatic.com

If your proxy does SSL/TLS inspection, Google Drive’s sync client can be particularly sensitive to that — man-in-the-middle interception of the TLS connection is a common cause of sync clients failing to authenticate even when the domains themselves are allowed. If you’re still having trouble after whitelisting the above, try adding an SSL-inspection bypass rule specifically for the Google domains and retest.

Because Google can and does adjust the specific subdomains and endpoints its services use over time, it’s worth checking Google Workspace’s own current network requirements documentation if you want the fully up-to-date and exhaustive list for your firewall rules.

Where That Documentation Actually Lives Now (2026)

Worth a specific mention since Google has restructured its help site: the old numbered support.google.com admin help articles have moved to Google’s newer Workspace Admin Help knowledge base. The two pages worth bookmarking are “Drive and Sites firewall and proxy settings” and the broader “Firewall and proxy settings” page, both under knowledge.workspace.google.com/admin/ — they list the exact hosts and ports (for example drive.google.com:443) Google currently recommends allowlisting, which is the definitive source over any third-party list (including this one) if Google has adjusted anything since this guide was last updated.

If you’re running split-tunnel VPN alongside a proxy, it’s also worth confirming Google Drive traffic isn’t being routed through the VPN tunnel unnecessarily — Google explicitly recommends allowing its bulk/high-volume traffic to bypass VPN tunnels where possible, since routing sync traffic through a VPN concentrator can itself introduce the same kind of interception or latency issues as an inspecting proxy.