Meraki captive portal - Not working in Chrome

[eem-olsed]

Hey all,

We have a Meraki Wifi.

When connecting to the Wifi it used to go "www.msftconnecttest.com " and then redirect to "apac.network-auth.com".
Recently this stopped working on Chrome. It shows "Site can't be reached" ERR_TIMED_OUT

On Edge it still works beautifully.

Are you familiar with any issues on Chrome?

Thanks 

[marce1000]

 - You may post that in https://community.meraki.com/t5/Wireless/bd-p/wireless-lan

 M.

[Haydn Andrews]

Could be certificate related to the captive portal, as Chrome sometimes has more restrictions on invalid certificates compated to Edge.

I have also seen if proxies are configured on some devices that the captive portal redirect tries to get sent to the proxy so also recommend testing with proxies disabled on the client device

[eem-olsed]

Posted now also there Marc.

Haydn: it doesn't even open http://neverssl.com
Not even when entering IP instead of hostname.
So I'm thinking maybe the issue is not certificate/DNS

On Edge, when trying to reach http://neverssl.com it immediately redirects to the Google OAuth sign in page.
Then if copy+pasting splash page url from Edge to Chrome, still doesn't reach the page, times out with "Site can't be reached

[eem-olsed]

It got resolved by its own.

Perhaps it was a Google Chrome version, not sure.