為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

certificate

  • 3 回覆
  • 33 有這個問題
  • 15 次檢視
  • 最近回覆由 glenj2000

more options

I can not access email. when they want to access the information appears "This Connection is Untrusted, login.yahoo.com or login.gmail.com uses an invalid security certificate. The certificate is not trusted Because it is self-signed". please help me

I can not access email. when they want to access the information appears "This Connection is Untrusted, login.yahoo.com or login.gmail.com uses an invalid security certificate. The certificate is not trusted Because it is self-signed". please help me

所有回覆 (3)

more options

Who is the issuer of that certificate?

You can retrieve the certificate and check details like who issued certificates and expiration dates of certificates.

  • Click the link at the bottom of the error page: "I Understand the Risks"

Let Firefox retrieve the certificate: "Add Exception" -> "Get Certificate".

  • Click the "View..." button and inspect the certificate and check who is the issuer of the certificate.

You can see more Details like intermediate certificates that are used in the Details pane.

If "I Understand the Risks" is missing then this page may be opened in an (i)frame and in that case try the right-click context menu and use "This Frame: Open Frame in New Tab".

Note that some firewalls monitor secure (https) connections and send their own certificate instead of the website's certificate.

more options

I have had the same issue with sites like "https://myaccount.yak.ca/" I suspect the certificates that Firefox use have been modified. Have you tried another browser on the same workstation?

more options

It is possible that your system clock has been reset not allowing the certificates to be updated. Open your date and time file and check that the date is correct. This corrected the problem for me. I believe that the 'conduit search' problem was a factor in causing the clock change.