搜尋 Mozilla 技術支援網站

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

Learn More

Firefox 125.0.1 update breaks all self signed certificates

  • 5 回覆
  • 0 有這個問題
  • 4 次檢視
  • 最近回覆由 mzla.cm

more options

Firefox 125.0.1 update breaks all self signed certificates

After the latest auto update I can no longer access any of my management screens on my private network with self signed certificates. This is a real problem. I have attached a couple error screen grabs, but ALL of themn are the same. The information link says there is no workaround!

So how do I recover access? Chrome works just fine ... so it is def. a Firefox problem.

Firefox 125.0.1 update breaks all self signed certificates After the latest auto update I can no longer access any of my management screens on my private network with self signed certificates. This is a real problem. I have attached a couple error screen grabs, but ALL of themn are the same. The information link says there is no workaround! So how do I recover access? Chrome works just fine ... so it is def. a Firefox problem.
附加的畫面擷圖

被選擇的解決方法

Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile. Make sure you stay signed out of your sync account when testing.

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

所有回覆 (5)

more options

I can't see how to edit this Q, so I will have to update - but I was mistaken. It is actually breaking all wildcard letsencrypt certificates, not slef signed ones. The self signed ones seem to be OK.

有幫助嗎?

more options

選擇的解決方法

Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile. Make sure you stay signed out of your sync account when testing.

有幫助嗎?

more options

I have tried using a private session and doing a cold reboot, but not tried a completely different profile.

This Q did make me wonder though if it was OS dependant, so I have just tried accessing one of the 'broken' URLs via a Linux VM running Firefox 125.0.1 and that worked fine.

I'll try to install a developer edition (not done that before, but I am assuming it is straight forward) and report back when I have done so.

Thanks for the help so far.

有幫助嗎?

more options

I have installed the developer edition version 126.0b3 and that seems to work perfectly.

Hmmm ... I'll go see about creating a new profile too ... moving forward ...

有幫助嗎?

more options

Thank you zeroknight. Your Qs led me to the (somewhat embarrasing) solution.

In case anyone else is looking for something similar, the fix was simple and in the end nothing to do with firefox directly. Once I found that the dev edition worked, I tried creating a new profile and that worked too - so I started looking at the differences. It was then that I noticed that when I started the original profile the embedded VPN plug-in was starting - which was configured to not recognise local addresses.

I can only assume that as the ones that did work were directly referenced by the local IP addresses that the VPN was being by-passed.

So, basically - I right royally screwed up by starting the VPN for something and then not realising that turning it off would not stop it restarting on the opening of any new tabs and didn't notice it was doing so.

Why is it always the simple things that are so difficult to find and fix?

Thank you again zeroknight - you asked me exactly the right Qs (which I should have thought of myself) and pointed me indirectly in the right directions with those tests. Very grateful. All working as it should now.

有幫助嗎?

問個問題

如果您還沒有帳號,您必須先登入帳號 來回覆文章。還沒有帳號的話,只能發問新問題