Member Avatar for norman.allen.948

I use Chrome as my default browser. Until recently I had no problem using it to access my online banking site. Now after I enter the user/password it goes to the second authentication page (input three characters from memorable word), but when I click OK on this page it goes straight back to the user/password screen.
It works happily in Firefox and IE11.
I am running Windows 7 Ultimate 32-bit and I have the latest version of Chrome. I tried it on my son's laptop running Vista Home Premium (same version of Chrome) and it worked correctly on that.

  • 4 Contributors
  • 3 Replies
  • 377 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by ishaan3731

Dani AI

Generated

A short expert summary and focused diagnostics to complement the suggestions from and : the fact that the bank flow works in Firefox/IE and on a different laptop points to a Chrome-specific problem on the affected PC (profile, extension, cookie/SSL handling, or local security/proxy), not a site-wide outage.

Useful tests and checks (in order of effort and what they reveal):

  • Incognito/extensions: test the login in Incognito (disables extensions). Success there implicates an extension; disable all at chrome://extensions and re-enable one-at-a-time to isolate the offender.
  • Profile corruption: a temporary profile rules out profile damage. Command to launch Chrome with a disposable profile on Windows:
    chrome.exe --user-data-dir="%TEMP%\chrome-test-profile"
  • DevTools investigation: open DevTools (F12) → Network (enable “Preserve log”) and Console. Perform the login and look for redirect chains (302/303), missing or blocked Set-Cookie headers, JS errors, or mixed-content/mime errors. In Application/Storage check whether the session cookie for the bank domain is being written and then lost on redirects.
  • Cookie/site permissions: confirm site-level cookie blocking or strict third-party cookie policies aren’t preventing session cookies from persisting (check the lock/icon by the address bar → site cookies/permissions).

Other common causes not yet mentioned in the thread: incorrect system time, system proxy or hosts-file entries, and antivirus/HTTPS‑inspection that intercepts TLS and breaks bank sessions. Temporarily disabling HTTPS-scanning in security software (with caution) or testing on a network without the proxy can confirm this.

If the flow works in a fresh profile or Incognito, the fix is to remove the offending extension or recreate the profile. If none of the above isolates the issue, capture a HAR from DevTools (Network → Save as HAR with content) and provide it to the bank’s support or IT for deeper analysis.

Recommended Answers

All 3 Replies

Member Avatar for rubberman

I am running the most recent versions of Chrome and Windows 7 Ultimate (corporate system - IT keeps them patched almost daily). No problems here, though if it has changed since Friday last (2 days ago) I wouldn't know. I'll be updating tomorrow, so if it has broken, I'll report it here. If not, then you have to think that possibly you have become infected with some virus.

Member Avatar for Rik_

Clearing Chrome's cash should solve the problem.

Member Avatar for ishaan3731

use ccleaner and remove temp data,cache , history etc..

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.