Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

What configuration needs to be changed to permit Secure Connections in Firefox 40.0.2?

  • 3 odgovora
  • 6 ima ovaj problem
  • 16 prikaza
  • Posljednji odgovor od FredMcD

more options

Firefox Version: 40.0.2 labeled up to date; OS: Windows 7/64 bit (Home Premium); Banking site fails to connect to a secure site with a message "Secure Connection Required"; Another site that uses simple htaccess to require password fails with "Authorization Required" message; Both of these sites open properly with Google Chrome;

I have been through the configuration options, and nothing seems to make any difference. Is there something that has changed in this new version that needs to be configured to make this work? I had not problems with this last week, presumably before and automatic 'upgrade'. Thanks, Steve

Firefox Version: 40.0.2 labeled up to date; OS: Windows 7/64 bit (Home Premium); Banking site fails to connect to a secure site with a message "Secure Connection Required"; Another site that uses simple htaccess to require password fails with "Authorization Required" message; Both of these sites open properly with Google Chrome; I have been through the configuration options, and nothing seems to make any difference. Is there something that has changed in this new version that needs to be configured to make this work? I had not problems with this last week, presumably before and automatic 'upgrade'. Thanks, Steve

Izabrano rješenje

That was good to hear. Please flag your last post as Solved Problem so others will know.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (3)

more options
more options

In addition to posting this here, I sent a note to my bank. It turns out that there was a problem on their end. Their support folks made the requisite change and the secure connection is again working. Whatever problem they had was apparently Firefox specific, but not a Firefox problem. Thanks, Steve

more options

Odabrano rješenje

That was good to hear. Please flag your last post as Solved Problem so others will know.