This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

can't access sub pages at chase.com FF 37.0.1 on Ubuntu 14.04

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 63 views
  • Last reply by DantePasquale

I can login to my account on chase.com (https). However, when I go to try to transfer funds I get this: https://payments.chase.com/PnT/Transfer/AddTransfer/Entry Secure Connection Failed

The connection to the server was reset while the page was loading.

   The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
   Please contact the website owners to inform them of this problem.

That's pretty messed up.

I can login to my account on chase.com (https). However, when I go to try to transfer funds I get this: https://payments.chase.com/PnT/Transfer/AddTransfer/Entry Secure Connection Failed The connection to the server was reset while the page was loading. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. That's pretty messed up.

தீர்வு தேர்ந்தெடுக்கப்பட்டது

But now it seems to be working again -- guess the error message from FF was inaccurate

Read this answer in context 👍 0

All Replies (3)

Did you contact Chase regarding the problem? This sounds like it is probably the result of outdated security settings on their payments.chase.com server.

For more information see TLS Error Reports

Yes, I called their CTO and he was very understanding and said that even though he had no clue who I was he would have that fixed immediately ;)

No, I'm not going to report it to them because they won't care and just tell me they no longer support FF.

If that's indeed the problem, then wildcard certs no longer work with FF? That's pretty messed up.

தீர்வு தேர்ந்தெடுக்கப்பட்டது

But now it seems to be working again -- guess the error message from FF was inaccurate