Notification

Planning your return to office strategy? See how ChromeOS can help.

Η σελίδα που ζητήσατε δεν είναι διαθέσιμη προς το παρόν στη γλώσσα σας. Μπορείτε να επιλέξετε μια άλλη γλώσσα στο κάτω μέρος της σελίδας ή να μεταφράσετε άμεσα οποιαδήποτε ιστοσελίδα στη γλώσσα της επιλογής σας, χρησιμοποιώντας την ενσωματωμένη λειτουργία μετάφρασης του Google Chrome.

Resolve captive portal issue on ChromeOS

If you're running ChromeOS 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 ChromeOS 62 to detect the device as connected to the Internet. If your firewall supports wildcards, you may be able to use a wildcard to allowlist alt*.gstatic.com.

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

Hosts to allowlist

To resolve the captive portal issue with ChromeOS 62, try allowlisting "alt*.gstatic.com". If your firewall doesn't support wildcards, allowlist 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

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
13162808494209601036
true
Search Help Center
true
true
true
true
true
410864
false
false