The short version
- 01Check whether your network is one of the types Google says may not work.
- 02Power cycle the speaker by unplugging it and plugging it back in.
- 03Move it within 15 to 20 feet of the router for setup, even if it lives elsewhere.
- 04Turn Wi-Fi off and back on on your phone, and update the Google Home app.
- 05Retype the password somewhere visible first, watching upper and lower case.
- 06Try setup on both the 2.4 GHz and 5 GHz bands.
Start here
Some networks simply will not work, and that is documented
Before troubleshooting, check whether your network is one Google says may not work at all. It lists public Wi-Fi, business networks, shared apartment networks, school and dorm networks, mobile hotspots and pocket Wi-Fi devices as connections you might not be able to use. If your network is an ordinary home one, the first three steps are to power cycle the speaker, move it within 15 to 20 feet of the router, and toggle Wi-Fi off and on on your phone.
Applies to: Google Nest and Google Home smart speakers and displays being set up or reconnected through the Google Home app. Menu paths and setup flows change as the app is redesigned, and Google publishes separate guidance for Seamless setup devices.
Where does setup fail?
Google smart speakers fail to connect for two very different reasons: something ordinary — distance, a mistyped password, a phone that needs its Wi-Fi bounced — or something structural, where the network itself is a type Google says may not work. The second group is not a fault and cannot be fixed by troubleshooting, so it is worth checking which you have before spending an evening on it.
It is a shared, work or public network
Is this a network type Google supports?
Check the networkSetup fails partway through
Have you power cycled and moved it closer?
Do the basicsIt rejects the password
Is the case exactly right?
Retype itIt connects then drops off
Is the band or router the problem?
Try the other band1. The networks Google says may not work
Google lists network types you might not be able to connect a speaker or display to, and it is worth reading before anything else: public Wi-Fi networks, business networks, shared apartment networks, school dorm networks, school networks, mobile hotspots and pocket Wi-Fi devices.
The common thread is that these networks either isolate clients from each other or require a login through a web page. Setup needs your phone and the speaker to talk to each other directly on the same network, and client isolation — which is the point of a public network — prevents exactly that. A captive portal is worse, because the speaker has no browser to accept terms in.
If your network is on that list, the honest answer is that troubleshooting will not help. Where it is a shared or managed network, the route is through whoever administers it; where it is a hotspot, a different connection is the answer.
This matters most for people setting a speaker up in a dorm, an office or a rented room, where every step below will appear to work and setup will still fail at the last moment.
If you are on a network you do not control, check this first. It is the difference between a fixable problem and one that is not yours to fix.
2. The three cheap steps, in Google's order
Google's opening steps are quick and they resolve a good share of cases. Disconnect the power cable from the speaker or display, then plug it back in. Place the speaker or display within 15 to 20 feet, or 4 to 6 metres, of the Wi-Fi router. And on your mobile device, turn Wi-Fi off and then back on.
The distance figure is worth taking literally during setup even if the speaker will live further away afterwards. Setup involves a handshake that is less tolerant than everyday use, and a speaker two rooms away can complete setup unreliably and then work perfectly once it is done.
Toggling Wi-Fi on the phone is not superstition either. The Google Home app needs the phone on the same network at the right moment, and phones drift onto mobile data or onto a different band without saying so — the toggle forces a clean rejoin.
Google also asks you to download the most recent version of the Google Home app. Setup flows change, and an old app talking to new speaker firmware is a genuine source of failures that look like network problems.
3. The password, and the part that catches everyone
Google's instruction is to check you have the correct Wi-Fi password and that the upper and lowercase letters are correct, because the password is case sensitive. That reads as obvious advice and it is the single most common cause of a setup that fails at the last step.
Phone keyboards make it worse. Autocapitalisation on the first character, autocorrect on a password that looks like a word, and the ambiguity between a capital I, a lowercase l and a digit 1 all conspire against you — and the speaker cannot tell you that the password was wrong rather than the network unreachable.
Type it somewhere you can see it first, in a notes app, then copy it across. It takes a few seconds and it eliminates a possibility that otherwise stays open through every other step.
If the network was set up by someone else, or by an installer, confirm the password rather than assuming the one on the router's label is still current — a changed Wi-Fi password is a common and invisible reason for a device that used to work to stop connecting.
4. Dual-band routers, and trying both
Google's guidance for a dual-band router is direct: try to set up your speaker or display on both the 2.4 GHz and 5 GHz bands. That is worth following literally rather than assuming one is correct.
The two bands behave differently. 2.4 GHz reaches further through walls and is more congested; 5 GHz is faster and shorter-ranged. A speaker at the edge of the house may be reachable on one and not the other, and which one works is a property of your home rather than a rule.
Routers that present both bands under a single network name complicate this, because you cannot choose which one the speaker joins. If setup keeps failing on such a network, temporarily splitting the bands into separate names — or disabling one during setup — gives you control that a merged network does not.
2.4 GHz
Better range through walls, more congested. Often the one that works at distance.
5 GHz
Faster, shorter range. Try both, as Google suggests, rather than assuming.
5. Confirming the network is actually working
Google's step is to confirm your Wi-Fi works by checking that other devices can connect to it, and to reboot the router if the network is unavailable. That sounds obvious and it is the check that stops you troubleshooting a speaker when the fault is upstream.
Use a device that was not already connected. A phone that joined the network hours ago may be holding a connection that a new device cannot establish, so a laptop or a visitor's phone is a better test than the one in your hand.
When rebooting the router, give it time to come fully up before retrying setup. A router that is still bringing up its wireless radios will accept some connections and refuse others, which produces a setup failure that looks like the speaker's fault and is not.
6. What to establish before contacting Google
Four answers cover almost every case. Is the network one of the types Google names as possibly unsupported? Was the speaker within 15 to 20 feet of the router during setup? Has the password been verified character by character, including case? And has setup been attempted on both bands?
Work them in that order, because the first can make the rest irrelevant. There is no point testing bands on a network whose client isolation was always going to prevent setup.
When you contact support, say what kind of network it is and whether you control the router, how far the speaker was from it during setup, whether other devices connect to the same network without trouble, whether both bands were tried, and at which point in the setup flow it fails. Those five answers separate an unsupported network from a distance problem from a password from a router that needs a restart.
Frequently asked questions
Why won’t my Google Nest speaker connect to Wi-Fi?
Start with the network type. Google lists public Wi-Fi, business networks, shared apartment networks, school and dorm networks, mobile hotspots and pocket Wi-Fi as connections you might not be able to use. If it's an ordinary home network, power cycle the speaker, move it within 15–20 ft of the router, and toggle Wi-Fi on your phone.
Can I set up a Google speaker on hotel or dorm Wi-Fi?
Often not. Google names public, business, shared apartment, school and dorm networks among those that might not work. Those networks isolate clients from each other or need a browser login, and setup requires the phone and speaker to talk directly on the same network.
How close does the speaker need to be during setup?
Google says within 15 to 20 feet — 4 to 6 metres — of the router. Take that literally for setup even if the speaker will live further away afterwards; the setup handshake is less tolerant than everyday use, so a speaker that struggles to set up may run fine once it's done.
Should I use 2.4 GHz or 5 GHz?
Google's advice for a dual-band router is to try both. 2.4 GHz reaches further through walls but is more congested; 5 GHz is faster and shorter-ranged. Which works is a property of your home. If both bands share one network name, splitting them temporarily gives you the control to choose.
It keeps rejecting my Wi-Fi password. Why?
Google notes the password is case sensitive and asks you to check the upper and lowercase letters. Phone keyboards autocapitalise and autocorrect, and capital I, lowercase l and digit 1 look alike. Type it into a notes app where you can see it, then copy it across.
How do I know the problem isn’t my router?
Connect a device that isn't already on the network — a laptop or a visitor's phone rather than the one in your hand. Google's step is to confirm other devices can connect and reboot the router if not. After a reboot, let it come fully up before retrying setup.
Sources and review notes
Checked on . Compiled by Glitchary from Google's help documentation on Wi-Fi connection problems with smart speakers and displays. The unsupported network types, the 15–20 ft distance, the case-sensitivity note and the dual-band advice are Google's. Google Home app setup flows change frequently, and Google publishes separate guidance for Seamless setup devices. The explanation of client isolation and captive portals, and the advice to test with a device not already connected, are editorial. Glitchary is independent of Google.