topic Re: URL not accessible in Chrome and same working in Firefox in General Topics

URL not accessible in Chrome and same working in Firefox

JANARTHANAN1392 — Thu, 12 May 2022 03:03:25 GMT

User trying to access external site, That particular website is not accessible getting "This site can’t be reached".

The same URL is working on Firefox.

Request traffic from chrome not reaching paloalto, the same from Firefox I can see the traffic logs.

Other websites working in chrome browser through paloalto.

The reported site is accessible in same machine, chrome browser outside network(not company LAN).

Re: URL not accessible in Chrome and same working in Firefox

Declan69 — Thu, 12 May 2022 06:31:40 GMT

How is the firewall identifying the traffic when using browser?

When using browser, What is the category you see in the logs ? What is the URL you see in the logs ?

Re: URL not accessible in Chrome and same working in Firefox

batd2 — Thu, 12 May 2022 07:56:56 GMT

@JANARTHANAN1392 Do you use proxy in your environment? Browser can be configured to use or bypass your companies proxy and this would explain different connectivity behaviour when using different browsers.

Re: URL not accessible in Chrome and same working in Firefox

JANARTHANAN1392 — Fri, 13 May 2022 02:39:51 GMT

@batd2 No proxy settings in browser level. As I said I can see other external sites logs in palo.

I want to add one more thing here,

Reported site is accessible if I add the site url in ssl decryption bypass. Before adding it same URL is accessible firefox browser and not on chrome & Edge.

Re: URL not accessible in Chrome and same working in Firefox

batd2 — Fri, 13 May 2022 09:37:54 GMT

@JANARTHANAN1392 Another possible reason for the different browser behaviour could be the Quic protocol used by Chrome and Edge, which is Chrome based.

Please see article below. You can try blocking quic as recommended:

Palo Alto Networks recommends creating a security policy in the firewall to block the QUIC application. With the QUIC traffic getting blocked by the Firewall, the Chrome browser will fall back to using traditional TLS/SSL.

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClarCAC