Resolve captive portal issue on Chrome OS

If you're running Chrome OS version 62, and you're seeing the error Device cannot connect to any wireless network or Network not available, you may need to allow access to additional hosts through your firewall. The hosts listed below must be accessible via HTTP port 80 in order for Chrome OS 62 to detect the device as connected to the Internet. If your firewall supports wildcards, you may be able to use a wildcard to whitelist alt*.gstatic.com.

In addition to allowing these hosts through your firewall, if you perform SSL inspection on your network, you’ll need to also follow the instructions on how to Set up a hostname whitelist.

Hosts to whitelist

To resolve the captive portal issue with Chrome OS 62, try whitelisting "alt*.gstatic.com". If your firewall doesn't support wildcards, whitelist the following list of hosts.

alt1.gstatic.com
alt2.gstatic.com
alt3.gstatic.com
alt4.gstatic.com
alt5.gstatic.com
alt6.gstatic.com
alt7.gstatic.com
alt8.gstatic.com
alt9.gstatic.com
alt10.gstatic.com
alt11.gstatic.com
alt12.gstatic.com
alt13.gstatic.com
alt14.gstatic.com
alt15.gstatic.com
alt16.gstatic.com
alt17.gstatic.com
alt18.gstatic.com
alt19.gstatic.com
alt20.gstatic.com
alt21.gstatic.com
alt22.gstatic.com
alt23.gstatic.com
alt24.gstatic.com
alt25.gstatic.com

 

Article last updated on December 22, 2017

Was this article helpful?
How can we improve it?