Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 3 antwoorden
  • 1 heeft dit probleem
  • 63 weergaven
  • Laatste antwoord van DantePasquale

more options

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.

Gekozen oplossing

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

Dit antwoord in context lezen 👍 0

Alle antwoorden (3)

more options

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

more options

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.

more options

Gekozen oplossing

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