Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

why won't foxfire let me access www.paypal.com?

more options

I get the following message when I try to access the paypal site to login:

Your connection is not secure.The owner of www.paypal.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.

Clearly, I have accesses it before (since I have an paypal account in the first place) so why can't I even get onto their web page now?

I get the following message when I try to access the paypal site to login: Your connection is not secure.The owner of www.paypal.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website. Clearly, I have accesses it before (since I have an paypal account in the first place) so why can't I even get onto their web page now?

Tüm Yanıtlar (2)

more options

There is security software like Avast, Kaspersky, BitDefender and ESET that intercept secure connections and send their own certificate.

https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can

https://support.mozilla.org/en-US/kb/firefox-and-other-browsers-cant-load-websites

configured their website improperly

How to troubleshoot the error code "SEC_ERROR_UNKNOWN_ISSUER" on secure websites https://support.mozilla.org/en-US/kb/troubleshoot-SEC_ERROR_UNKNOWN_ISSUER

more options

I just want to clarify: when Firefox cannot form a secure connection with a server, that is not an indication that a site is unsafe, it is an indication that the server failed to prove to Firefox's requirements that it actually is the site you want to reach. It could be a fake, or it could have obsolete security which Firefox considers insecure, or there could be a "man in the middle" reading all your communications with that server. You should never need to make exceptions for well run sites.

Is this the only HTTPS address giving you this error? If there is a pattern, that is useful to know.