CTD - Chrome on WIn10
Discussion
If I try to log on using Chrome on Win 10 as soon as I hit enter with my details in the form it closes Chrome. If I re-open chrome it asks me if I want to re-open the previous pages as it didn't shut down correctly.
I can log in fine with Edge. Is it possibly something to do with corporate Zscaler protection?
I can log in fine with Edge. Is it possibly something to do with corporate Zscaler protection?
Hi RichTT - very strange!
That's certainly not something we can repro or have seen reported elsewhere..
Is it still occurring? Reason I ask is on Friday we rolled out an update to further secure our login flow, and I wonder if the issue that was addressing was what was causing the page to be closed -> see https://www.pistonheads.com/gassing/topic.asp?h=0&...
Otherwise, the standard advice we would give here is to attempt logging in via Chrome in InCognito mode (i.e. no browser extensions) to help track down the cause..
Cheers
That's certainly not something we can repro or have seen reported elsewhere..
Is it still occurring? Reason I ask is on Friday we rolled out an update to further secure our login flow, and I wonder if the issue that was addressing was what was causing the page to be closed -> see https://www.pistonheads.com/gassing/topic.asp?h=0&...
Otherwise, the standard advice we would give here is to attempt logging in via Chrome in InCognito mode (i.e. no browser extensions) to help track down the cause..
Cheers

Yep, given it works fine in Incognito but fails otherwise points to a browser extension (possibly mandated by your corporate IT settings, possibly another that you use personally).
You could play whack-a-mole by disabling your extensions (if possible) one by one to track down the culprit.. it could well be as simple as adding the pistonheads.com domain to whitelist etc..
If you do track it down, and are happy to share, I'd be curious to know what the culprit turned out to be!
You could play whack-a-mole by disabling your extensions (if possible) one by one to track down the culprit.. it could well be as simple as adding the pistonheads.com domain to whitelist etc..
If you do track it down, and are happy to share, I'd be curious to know what the culprit turned out to be!
To try get to the root of the issue I would suggest checking/doing things such as:
- disabling extensions
- clearing site data (cookies etc)
- trying a new Chrome user profile
https://support.google.com/chrome/answer/142063 might have some useful information too.
Hope this helps!
- disabling extensions
- clearing site data (cookies etc)
- trying a new Chrome user profile
https://support.google.com/chrome/answer/142063 might have some useful information too.
Hope this helps!
Gassing Station | Website Feedback | Top of Page | What's New | My Stuff


