搜尋 Mozilla 技術支援網站

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

Learn More

此討論串已經關閉並封存。 如果您有需要幫助,請新增一個新問題

Weird "Insecure Connection" behavior

  • 4 回覆
  • 1 有這個問題
  • 14 次檢視
  • 最近回覆由 Chris Ilias

more options

Hello,

Starting Firefox and going to https://www.israelweather.co.il/week.asp - I get the "Insecure Connection" page. If, however, I go to a different site and then go to https://www.israelweather.co.il/week.asp - Firefox displays the page.

Any explanation or a way to solve the issue?

Thank you.

Hello, Starting Firefox and going to https://www.israelweather.co.il/week.asp - I get the "Insecure Connection" page. If, however, I go to a different site and then go to https://www.israelweather.co.il/week.asp - Firefox displays the page. Any explanation or a way to solve the issue? Thank you.

被選擇的解決方法

Maybe there is a perfectly logical explanation?

When I check the site using this diagnostic page --

https://www.ssllabs.com/ssltest/analyze.html?d=www.israelweather.co.il&latest

-- it says there is an incomplete chain. Firefox requires sites to send not just their own certificate, but any intermediate certificates required to prove that their certificate can be verified all the way back to a trusted root certificate included with Firefox.

When sites don't do that, you sometimes know and you sometimes don't know. As you browse, Firefox receives and caches intermediate certificate, so if you have visited a site that happens to have the same chain before visiting the weather site, no problem, Firefox uses its cache.

By the way, the certificates are cached in a file named cert9.db in your Firefox profile folder. If for any reason that file is deleted, Firefox will start a new one with the trusted root certificates, but your previously cached intermediate certificates will be gone.

Incidentally, that diagnostic page gives the weather site a terrible grade. Hopefully it doesn't require you to submit any sensitive information, or display any personal data back.

從原來的回覆中察看解決方案 👍 1

所有回覆 (4)

more options

選擇的解決方法

Maybe there is a perfectly logical explanation?

When I check the site using this diagnostic page --

https://www.ssllabs.com/ssltest/analyze.html?d=www.israelweather.co.il&latest

-- it says there is an incomplete chain. Firefox requires sites to send not just their own certificate, but any intermediate certificates required to prove that their certificate can be verified all the way back to a trusted root certificate included with Firefox.

When sites don't do that, you sometimes know and you sometimes don't know. As you browse, Firefox receives and caches intermediate certificate, so if you have visited a site that happens to have the same chain before visiting the weather site, no problem, Firefox uses its cache.

By the way, the certificates are cached in a file named cert9.db in your Firefox profile folder. If for any reason that file is deleted, Firefox will start a new one with the trusted root certificates, but your previously cached intermediate certificates will be gone.

Incidentally, that diagnostic page gives the weather site a terrible grade. Hopefully it doesn't require you to submit any sensitive information, or display any personal data back.

由 jscher2000 - Support Volunteer 於 修改

more options

Hello jscher2000,

Thank you for the detailed explanation. I appreciate it.

I've recently upgrades from FF 52 to FF 64 (had a lot of modifications I didn't want to lose) and mainly used its private window.

Thanks to your explanation I used a non-private window, FF cached the certificate and all is well now. No sensitive data. :)

Best regards.

more options

Its fresh Installation Mozilla firefox on Windows 10, Installed FF 60.5 esr successfully unable to browser Internet in FF, Getting the error seems like below Your connection was not secure , it is not possible to add an exception for this site. What can be reason in FF Browsers, is somthing help on this?

more options

Hi chaitu, jscher2000's post was marked as the solution by the person who asked the original question (Yaron). Your issue may have similar symptoms, but it is likely a different cause/solution. You should use https://support.mozilla.org/en-US/questions/new where volunteers can get more details about your setup.

Because this thread is solved and more people might start using it for their own questions, I'm going to lock it.