Can't login to chase.com anymore

[lindend]

I'm on Waterfox (aka 64-bit Firefox) 47.0. I've been using Noscript for many years on chase.com without a problem. Within the last few months, whenever I go to chase.com, I get an error message page rather than a login page. chase.com (and all its variants are whitelisted). If I enable scripts globally, I'm able to see the login page. But there are no additional sites to whitelist. If I disable the global enable, the error message page is instantly displayed. Any suggestions on what I can enable to fix this?

[barbaz]

Waterfox is not a supported browser, nor is it simply 64-bit Firefox. Does the problem occur on official 64-bit Firefox?

[therube]

I get an error message page

?

chase.com (and all its variants are whitelisted).

Which are?

[lindend]

The error page says the chase web site is currently unavailable. Call an 800 # etc if you need to speak with someone immediately.

The two chase sites in the whitelist are

chase.com
chasebonus.com

[lindend]

I just tried it on another machine. The problem only seems to happen once you login once.

The error page is titled "Outage Chase"

We'll be back shortly. Then a whole series of 800 #s if immediate help is required.

[lindend]

Waterfox is not a supported browser, nor is it simply 64-bit Firefox. Does the problem occur on official 64-bit Firefox?

The behavior is identical with the official 64-bit Firefox. I get the outage page once I login a single time.

[gmccollam]

I have the same problem, it happened when Chase updated their website. I do get the login page, but when loading the website it switches to the outage page. If I allow scripts globally it works, but I don't want to do that.

[gmccollam]

I clicked on the No Script icon, where you can allow globally, and saw the recently blocked sites. Included was chasecdn.com. I clicked allow and now the site works! By the way, when I type in a site to whitelist manually, the allow box stays grayed out, whay am I doing wrong?

[therube]

the allow box stays grayed out

Presumably the domain you want to allow (or some variation of it) is already whitelisted.

[barbaz]

I clicked on the No Script icon, where you can allow globally, and saw the recently blocked sites. Included was chasecdn.com. I clicked allow and now the site works!

Hmm in that case try NoRedirect configured to block all redirects (Regex: .*, check only "Source") maybe you'll see this extra site in NoScript somewhere along the line?

[lindend]

I clicked on the No Script icon, where you can allow globally, and saw the recently blocked sites. Included was chasecdn.com. I clicked allow and now the site works! By the way, when I type in a site to whitelist manually, the allow box stays grayed out, whay am I doing wrong?

Adding chasecdn.com worked. Thanks. I didn't think to check on the recently blocked site list. Had assumed it would show on the list of active sites that needed to be enabled.

[Straspey]

I tried logging in to Chase this morning via Firefox 47.01

My first login attempt was looped back to the original login page. After logging in again, I received a page which told me I needed to activate javascript in order to access the website, which I found odd because I uninstalled java years ago and have been getting along quite well without it.

However, I decided to run a test, so I made sure my version of FF and Flash were current, and then downloaded and installed a fresh copy of the latest version of Java for my system. Rebooted and all that - and then tried again to login to Chase.com.

Still no joy.

After speaking with Chase tech support and being told it wasn't their problem, but it was on my end, I remembered that I have NoScript, so I made sure the site was whitelisted - which it was.

I finally went into the Firefox add-ons menu and disabled NoScript -- (later starting FF in safe mode) and that worked and I was able to login to Chase normally.

Then - I ran a Google search for this issue and discovered this thread, and am happy to report that when I added chasecdn.com to the whitelist it solved the problem and I am now able to login. Hopefully this will be of some help to other users who experience this problem.

Many thanks for sharing that solution -- and no thanks to Chase for doing a major update of their website without informing their customers and making us all spend our time figuring it out on our own.

PS - I went back and uninstalled java from my system, and it still works this way.

[therube]

I went back and uninstalled java from my system

A smart thing to do.
PS: JavaScript is not Java.

[Guest]

PS: JavaScript is not Java.

Yeah - thanks for clarifying that. I was still a bit frazzled this morning when I posted because it was right after having a web support CSR talk to me like a newbie while I was trying to explain the problem. After adding chasecdn.com to the whitelist, the website still loops back to the login page upon my initial attempt, but then accepts the second login attempt and takes me to the page.

Chase has just implemented a total and major upgrade and reconfiguration of their website - so it's not surprising to see this happen. As a smart tech guy from my ISP pointed out - as soon as enough people start calling Chase to complain about this, they'll do something to tweak it on their end.

Glad I found this place, and thanks again for the help and input.

[therube]

as soon as enough people start calling Chase to complain about this, they'll do something to tweak it on their end

No they won't, but it sure can't hurt to complain, http://forums.mozillazine.org/viewtopic ... #p14638259.
Actually they might change. But if you don't complain, they never will.