6/6/18

Original Poster

Sava333

Chrome 67 and captive portal at 1.1.1.1

Using 67 stable, Google Pixel 2XL and also Windows 10. Chrome decides to redirect http://1.1.1.1 to https which means I can no longer access my company's guest wifi portal. I realize this probably stems from the fact that 1.1.1.1 is now a legit site but Chrome should check for captive portals before redirecting to the CloudFlare DNS site.

On my Windows PC I can use another browser as a workaround but on my phone I cannot do that.

Community content may not be verified or up-to-date. Learn more.

Recommended Answer

8/1/18

LarryLACa

Tips and Summary:

A Chrome update to accomodate 1.1.1.1 captive web portals is available. After the 'Connection not private' warning, use the Advanced, Proceed to unsafe.. option at the bottom to reach the signin portal. The update is available for:

Desktop stable 67.0.3396.99 and beta 68.0.3440.42
Android beta 68.0.3440.40 from the PlayStore here.
Chromebooks, Pixel, Chrome OS beta 68.0.3440.40
iPhones and iOS tablets: waiting for feedback on recent updates

The 1.1.1.1 internet address was repurposed earlier this year for CloudFlare secure DNS. Unfortunately, the way Chrome handled the new 1.1.1.1 usage broke some captive web portals beginning with Chrome 67, ~June 1. Google reverted the change and the Chrome updates began to appear June 25, depending on device type and release channel. See CR 853934 for details.

Portals should be reconfigured for the new 1.1.1.1 allocation to use another address. In some cases, 1.1.1.1 can be retained by adding an external DNS record (for the portal (guest) wifi network) that maps 1.1.1.1 to the captive portal page i.e. guest.xxxxx.net. (Sava333 6/27). Cisco (now) recommends using 192.0.2.1 instead of 1.1.1.1 (Shawn 6/7).

Android users may be able to use a temporary fix for immediate relief:

disable cellular data,
connect to the guest wireless,
access 1.1.1.1 in a browser, sign in,
re-enable cellular data - now you are on the wireless. (jnewton 6/20)

History: The story begins with the CloudFlare HSTS secure DNS reallocation of 1.1.1.1, dating back to the beginning of the year. The Chrome 67 change (and portal problem) was publicly visible since early March in the dev channel. CloudFlare was already working the portal issue with ISPs and router vendors (CloudFlare blog 4/10) - including Cisco, at that time. For more history, follow the links, scan this blog (here), or use this search for related posts.

Recommended by Original Poster

Was this answer helpful?

How can we improve it?

All Replies (43)

6/7/18

Pearl - Community Specialist

Hi Sava,

Thanks for posting on the Google Chrome Help Forum.

Could you confirm if you’re on a domain or a managed system? If yes, are you the administrator? If yes, please let me know and I’ll have this post redirected to the appropriate forum for further assistance.

If you're not the administrator, then please get in touch with the domain administrator for further assistance.

Keep me posted.

Regards,
Pearl

6/7/18

Krim Tastic

We're seeing the same issue, we're a public library and are getting more and more reports of user access to the captive web portal having issues and getting net::ERR_CONNECTION_REFUSED when redirected to 1.1.1.1, this is only affecting Android and Chrome users. Would be nice to get a fix from Google on this so we don't have to re-engineer our whole wireless network to fix the problem.

-Krim

6/7/18

Shawn Babinyecz

Same here, having issues with Chrome 67 and the cisco captive portal at 1.1.1.1. If anyone has a fix, that would be greatly appreciated! Thanks!

6/8/18

Shawn Babinyecz

We were able to fix this issue by changing the captive portal IP address to something other than 1.1.1.1. We used 192.0.2.1 which was a recommended IP address from Cisco. It would still be nice for Chrome to work with 1.1.1.1 as our fix was a workaround. You can check out RFC5737 for more details on the 192.0.2.0/24 network. https://tools.ietf.org/html/rfc5737

6/15/18

JohnL533

Cisco TAC provided our organization the same workaround. Chrome on mobile and windows redirects correctly. Firefox, IE, Edge on windows also. However, I have had an issue during testing in which safari on iOS 11.4 would not redirect to the new IP. Dumped cached, restarted, and forgot network and it has persisted. I’m wondering if anyone else has seen this after changing the portal IP
This is halting us for now.

I would like to note that having to reboot the controller(s) is going to cause a ton of work to avoid downtime.(Migrating APs to backup/alternate WLCs)
Cisco tech remarked that “Google is working on it..”
This makes me curious if there is some change coming to Chrome. I’d have to say I’d be irritated if all of this was for a temporary situation.

37 MORE

7/3/18

LarryLACa

Lester:

Were you able to add the External DNS record as suggested above for your portal?

This question is locked and replying has been disabled. Still have questions? Ask the Help Community.

Badges

Some community members might have badges that indicate their identity or level of participation in a community.

Google Employee — Google product team members and community managers

Community Specialist — Google partners who help ensure the quality of community content

Platinum Product Expert — Community members with advanced product knowledge who help other Google users and Product Experts

Gold Product Expert — Community members with in-depth product knowledge who help other Google users by answering questions

Silver Product Expert — Community members with intermediate product knowledge who help other Google users by answering questions

Product Expert Alumni — Former Product Experts who are no longer members of the program

Community content may not be verified or up-to-date. Learn more.

Levels

Member levels indicate a user's level of participation in a forum. The greater the participation, the higher the level. Everyone starts at level 1 and can rise to level 10. These activities can increase your level in a forum:

Post an answer.
Having your answer selected as the best answer.
Having your post rated as helpful.
Vote up a post.
Correctly mark a topic or post as abuse.

Having a post marked and removed as abuse will slow a user's advance in levels.

View profile in forum?

To view this member's profile, you need to leave the current Help page.

Reply in forum?

This comment originated in the Google Product Forum. To reply, you need to leave the current Help page.

Chrome 67 and captive portal at 1.1.1.1

Badges

Levels

View profile in forum?

Report abuse in forum?

Reply in forum?