Since you use NoScript, you may want to check for possible auxiliary domains being blocked (partial block symbol on the S icon) when you're on the Chase site. As sites are modernized, the number of different hosts involved seems to grow...

Some parts of the site may use Flash and if you have Flash set to "Ask to Activate," sometimes sites are impatient with the delayed activation and accuse you of having disabled JavaScript.

Other than that, if you haven't already, I suggest clearing the cache: How to clear the Firefox cache.

Note: If you have a large hard drive, this might take a few minutes. If you do not see the number going down on the page, you can reload it using Ctrl+r to check progress.

checked NS, flash is ok, cache cleared, and still no fix. *mutter*. Thx however.

Do you use Chase in a private window?

There could be an issue with Tracking Protection. This article has more information on what it does and how to make a temporary exception: What happened to Tracking Protection?.

If the page that triggers this goes by too quickly to make a site-specific exception, you could try using the site in a regular window. If you use "automatic" private browsing to make all windows private, you could turn the feature off temporarily to see whether that helps. That's covered in the above article (the part about using the Options page).

Hmm, another user said there's an intermediate page:

I figured out what the problem was; by watching carefully, I could see that a script was getting blocked momentarily and then going away on the follow-up website which told me to turn on javascript. The problem is that I can't get to the option to enable the blocked script in time - it's gone in less than a second, and I'm left with the completely unhelpful page which notifies me that there's a problem.

Over at: getting javascript error with www.chase.com

If the intermediate page is too "impatient" then this is going to be difficult to unblock in a step-by-step manner. You could turn on "Allow Scripts Globally (dangerous)" (bottom of the NoScript menu) to get into the site, then check the menu for what servers are actually being used and see whether you then can create the necessary permissions before turning NoScript back on.

cant find the intermediate page, but when disabling scripts globally, it is accessable. however, i am not able to identify which script it is to 'allow'. For the obvious reasons, I dont wish to allow globally full time, nor do i wish to 'turn off/turn on' when i wish to check the bank. My luck I will forget to turn to a more 'safe' position.

If you switch NoScript back on after getting to that next page, does everything work normally from there, or does the error page come back?

Anyway, I agree it's painful to think about running wide open once you are used to NoScript!

Switching back (once inside the site) it goes back to the error page, (as opposed to working normally).

Sorry, I forgot to have you turn off the auto-reload for this test.

(1) While viewing the Chase site, temporarily disable NoScript using "Allow Scripts Globally (dangerous)" so the target page will load normally.

(2) Open the NoScript Options dialog and select the General tab. Uncheck the box for "Automatically reload affected pages" and OK the change.

(3) Then switch NoScript back to forbidding scripts globally and the menu should flip to showing sites that are not allowed.

Some screenshots (from this site, obviously not matching what you'll see) attached for reference.

I personally keep auto-reload off and reload manually but that is more work for the fingers.

Ahh, that worked. There was a script inside the site (past the sign in) that I could not access to give its script permission. Once I disabled the auto-reload, I could give it permission and am able to access the inner site and its data. TYVM Jscher, you were very helpful (and thankfully persistent).