How to Fix “There Was a Problem Communicating With Google Servers” on Android

By ErrorFix · Updated October 16, 2026 · 6 min read

What “There was a problem communicating with Google servers” means

This message appears when you add a Google account in Settings, during a phone’s first-time setup, or sometimes when the Play Store tries to verify you. The wording makes it sound like Google’s servers are broken, but in practice that’s almost never the case. What’s really happening is a failed secure handshake between your phone and Google: your phone says “here’s my credentials,” Google’s servers say “that doesn’t check out,” and the phone shows this vague error instead of explaining why.

The most common real cause is surprisingly mundane: your phone’s clock is wrong. The sign-in uses time-sensitive security tokens, and if the phone’s date or time is off by even a few minutes — common after a factory reset, a long time offline, or a dead battery on some phones — Google’s servers reject the handshake outright. That’s why this error shows up so often right after resetting a phone, and why the clock fix below resolves it for the majority of people.

The other frequent culprits live in the network and the account data. Restricted Wi-Fi networks (hotels, offices, some public hotspots), VPNs, and carrier proxies can block or mangle the connection to Google’s authentication servers, which produces the same message. And if the local Google account data or the Google Play Services cache is corrupted — after an update, an interrupted setup, or too many failed sign-in attempts — every attempt will keep failing until that stale data is cleared. The good news is all of these are fixable without touching your actual Google account.

Common causes

• Wrong date, time, or time zone: the most common trigger — Google’s servers reject the sign-in when the phone’s clock doesn’t match, even by a few minutes.
• Blocked or unstable network: hotel Wi-Fi, office firewalls, VPNs, or weak mobile data interfering with the connection to Google’s authentication servers.
• Corrupted Google services cache: stale or damaged cached data in Google Play Services, the Play Store, or Google Services Framework breaking the handshake.
• Stale Google account token: the account’s local sign-in data is out of date or half-written after an interrupted setup, so every retry fails.
• Two-step verification on an older Android version: older sign-in flows can’t complete modern 2-step verification and fail with this generic error instead of asking for the code.

How to fix “There was a problem communicating with Google servers” — step by step

Start with steps 1 and 2 — a network switch and the automatic clock fix resolve the great majority of cases.

1. Check the internet connection and switch networks. Make sure you’re on Wi-Fi or have mobile data turned on, then open a browser and load a web page to confirm the connection actually works. If pages load fine, switch networks anyway — go from Wi-Fi to mobile data or connect to a different Wi-Fi — and try signing in again. This error fires constantly on weak, captive-portal, or restricted networks (hotel Wi-Fi, office firewalls, VPNs), so ruling out the connection first saves a lot of wasted time. Turn off any VPN while you test.
2. Turn on automatic date and time. Go to Settings > System > Date & time and switch on Set time automatically and Set time zone automatically (on Samsung: Settings > General management > Date and time). If the toggles are already on, turn them off, restart the phone, and turn them back on — sometimes the phone claims to be synced when it isn’t. Google’s servers reject the sign-in handshake when the clock is even a few minutes off, and this is the single most common cause of the error.
3. Remove the Google account and add it back. Go to Settings > Passwords & accounts (on Samsung: Settings > Accounts and backup > Manage accounts), tap the Google account, and tap Remove account. Restart the phone, then go back to the same screen, tap Add account > Google, and sign in fresh. This clears any stale authentication token that’s breaking the sign-in and is the fix that works most often after the clock fix. Don’t worry — your emails, contacts, and photos live in your Google account online and sync back automatically.
4. Clear the cache of Google’s system services. Go to Settings > Apps, tap the three-dot menu, and choose Show system apps. Open each of these three apps one at a time and tap Storage & cache > Clear cache: Google Play Services, Google Play Store, and Google Services Framework. Corrupted cached data in these services can block the account handshake. Clear the cache first, restart, and test — only use Clear storage if the error persists, since that resets more data (see the FAQ for what it actually erases).
5. Use an app password if you have 2-step verification. Older Android versions sometimes can’t complete the modern two-step sign-in flow on the phone and fail with this generic error instead of asking for your verification code. On a computer, open your Google account’s security settings, generate an app password for “Mail” on your device, and enter that 16-character code as your password when adding the account on the phone. Alternatively, finish the verification by signing in through the phone’s browser at accounts.google.com first, then add the account in Settings.
6. Factory reset as a last resort. If the error appears even during the phone’s first-time setup and none of the steps above worked, the system software or account framework is damaged beyond a cache clear. Back up your photos, messages, and files to Google Drive or a computer, then go to Settings > System > Reset options > Erase all data (factory reset). After the reset, connect to a strong Wi-Fi network, make sure the date and time are automatic during setup, and sign in — a clean system ends the error in essentially every remaining case.

Did this fix it? Quick checklist

• You can add your Google account in Settings without the error appearing
• Date, time, and time zone are all set to automatic and match your location
• The phone signs in on a different network too (not just your usual Wi-Fi)
• The Play Store opens and shows your account without prompting again

If the error appears only on one specific Wi-Fi network, the network is the problem — try mobile data, a different hotspot, or ask the network admin whether Google services are being filtered. If it appears only during first-time setup on a fresh reset, the clock is almost certainly wrong, so double-check the automatic date and time before the reset wipes again. And if it started the same day as a Google outage reported on the news, just wait a few hours — that’s the one time the servers really are the cause.