Captive portal access failure using google chrome

[User-checkpoint]

Hi Team,

One of the customer environment having R80.30 take 217 distributed architecture. When accessing captive portal via google chrome we are getting error but captive portal can be accessed via other browsers like Firefox or internet explorer. Even if I'm accessing  captive portal URL error persist.

We have identified while accessing captive portal via google chrome, chrome initiates the traffic to gstatic generate_204 page it was blocked by Internet/computer category, once we allow this category captive portal is accessible via chrome browser.

So to access internet user must login to the captive portal but if user wants to access captive portal via chrome that required internet access??😜

Herewith I have attached screenshots as well.

'

[G_W_Albrecht]

I would suggest to contact TAC about this !

[Mithu]

I have opened TAC but we are clueless, TAC suggested some adware is running on the machine, but I don't think so. Since this issue persists from most laptops and mobile phones as well.

[Chris_Atkinson]

Can you confirm if chrome is using the Data saver or Quic options and if those have any bearing on your symptoms?

[Mithu]

Quic protocol is disabled on a browser level, we are facing the same on laptops and mobile phones as well.

[PhoneBoy]

Please show the log card where the gateway is dropping this connection, redacting sensitive details.
I suspect you can create an allow for the specific URL/host being accessed.

[User-checkpoint]

Herewith I have attached rule base which is created for test PC which is 172.16.30.254 , In the block message We have instructed to users to click here to authenticate, once user click the hyperlink captive portal will open in new tab.

Although if I enabled 4th rule captive portal can be accessible in the meantime some other websites like google can be accessible.

[PhoneBoy]

That's not the question I asked.
Please show the precise entry in the logs where the page is blocked.
Click on the line in SmartView and bring up the log card.
Based on this we can change Rule 4 so it’s more precise.

[User-checkpoint]

Herewith I have attached requested traffic log, in the mean time we can see google chrome trying to access URL-  gstatic.com/generate_204