Nest Hub stuck on "Check Internet Connection"

[McFuzz89]

Hi all,

I've got a 2nd gen Nest Hub that, as of tonight, is continuously stuck on "Check Internet Connection." So far I have:

• Rebooted it
• Reset it (factory default)
• Attempted to connect it to both a 5 GHz and 2.4 GHz networks.
• Rebooted my switch, firewall, router, DNS server.
• Went through logs of all my networking stack but cannot find any evidence of anything blocking it.
• Attempted, as a last resort, to connect it to a neighbors WiFi (with their permission) - same results. 

Any ideas before I chuck it?

Thanks!

[Gehirnfrost]

Same here, 2 second gen Nest Hub displays just stopped working today. Stuck on check internet connection. Nothing changed in the network. I would like to prevent a reset, because they are built in a smart home configuration.

Software Version: 47.9.4.447810048

Cast Firmware: 1.56.309385

[Azarco]

Hey folks,

The team is aware of the issue on Google Nest Hub where it keeps on disconnecting from the network. Rest assured that they are looking into this issue at hand, and I'll update this thread as soon as I have more information to share.

McFuzz89, we need additional information:

1. Swipe up from the bottom of the display screen.
2. Tap Settings and then About device. You should find your "Software version" and "Cast firmware version."
3. Scroll to the bottom to see the “Operating System Version”.

Gehirnfrost, can we also have the operating system version of your Nest Hub?

Keep us posted.

Thanks,

Alex

[Gehirnfrost]

No Operating Version there, just what I posted before.

Solution workflow is here: https://www.reddit.com/r/googlehome/comments/wkrqsf/comment/ijrx3im/

I would say you messed up the DNS resolution, but I am pretty sure that was done on purpose...

[McFuzz89]

It wasn’t mess up - it was done to Adblock but had an adverse effect on the hub 😞

[Azarco]

Hey McFuzz89,

Thanks for updating the Community forum of your resolution — it's a big help! Let us know if you have other questions or concerns so that we can assist you.

Best,
Alex

[Gehirnfrost]

I meant the google guys messed up, not you. 😋

It is just not right, what they did, forcing the use of there servers.

[Azarco]

Hey folks,

We hear you! We're always looking for ways to improve and we appreciate your feedback. I also suggest that you send feedback using your devices by saying, "Hey Google, send feedback," or by following the steps on this link. Let me know if I can assist with anything else.
 

Kind regards,

Alex

[Princesss]

Hi folks,

We just want to check if you have seen our response posted above. Let us know if you have additional questions, otherwise we'll be locking the thread.
 

Best,

Princess

[Princesss]

Hi folks,

Due to inactivity, I'll go ahead and lock this thread in 24 hours. Feel free to start a new thread if you need assistance with your Google speakers and we'd be glad to assist you further.

Best,

Princess

[McFuzz89]

Hi all,

The root cause of this issue is that the Hub insists on using google DNS at 8.8.8.8. I use pi-hole which acts as the DNS server and redirect all external DNS requests via firewall configurations to pi-hole. That apparently broke the hub. After whitelisting the Hubs IP address to allow direct comms to google DNS - it started working. Annoying but relatively easy fix.