rmiyai said

I tried the following, but will this workaround still be effective after 2025/3/14? I changed the OS date setting to 2025/3/15, confirmed that the extension was disabled, and then changed xpinstall.signatures.required to false. The extension was re-enabled.

addon signing is enforced in firefox release builds since version 48 - the mentioned preference is no longer in use: https://wiki.mozilla.org/Addons/Extension_Signing

if you want to run unsigned addons, please use firefox developer edition instead: https://developer.mozilla.org/en-US/Firefox/Developer_Edition

I am using Firefox ESR. In this case, if I set xpinstall.signatures.required:false, does that mean the extensions will not be disabled?

Axelotl644, this questions should have been posted as a new thread as it is off-topic for this thread. https://support.mozilla.org/en-US/questions/new/firefox/form

Axelotl644 said

I have tried getting the official launcher using this link https://www.mozilla.org/en-US/firefox/all/desktop-release/linux64/en-GB/. Howver the file just sits in my computor in "files" and does not do anything when pressed on.

There is no package or installer with the tarball version as you just extract and run the firefox-bin in the firefox folder to start Firefox is the basics. Never used a Chromebook before however make sure the Firefox folder has read/write permissions for the user to get internal Firefox updates.

Thank you for the reply. As I mentioned, the actual metods for updating Firefox were not working and my core issue was not being able to upgrade my firefox to get more recent versions required to not have a problem with the root certificate. Here is a direct qoute from the main page I got directed to by the in browser warning about the update: "If you have any trouble with the update or need further assistance, we’ve set up a special thread in the Firefox Community Forum to focus on this topic. Head over to ask questions and find answers from both the Mozilla team and the community. We’re here to help!". This thread is outright called "(...)Questions & Tips for Updating". I was having problems updating firefox to a version that would not have the root certificate issue. I would greatly appreciate if you could expand your reasoning as to why a problem with updating firefox to fix the root certificate is not fitting for a thread about helping others with updating to fix the root certificate.

For reasons I genuenly do not understand, my firefox has been update to version 135, and yes I did try restarting firefox previously. So my technical issue has been solved for now even if I do not understand it.

However I would also like you to elaborate on that last part. I can find the firefox bin but is labled as an archive by the file-system of chrome, and when clicked it only opens google chrome to download itself. I can open the tar and it causes a new folder to open itself that is labled firefox and contains everything from "defaults" to "omni.ja" and the "firefox-bin". Howver this folder is read-only and can not be edited. Thus I can not find a way to open firefox using this method.

I am currently using a mozilla fork, floorp. Don't ask why, I have my reasons. What's important is that 1) it has different update channel because it's a fork, 2) its developers have not yet released an update with the fix, I am on the most recent version, 3) looks like they also haven't cut the functionality to show this stupid warning "Update now, end-of-the-world is near blah blah".

So it is still one month before the cert expires and the problem actually happens, but I, as a user, have to see this stupid Update message every day. That is extremely irritating, and the update button is useless.

Is it possible to disable this update warning anyhow? I have played with several flags, but no luck atm. Big sincere thank you from my side to anyone who figures out and shares!

Adding my plea to Mozilla to please continue backward functionality of Firefox for Windows 7. Neither of my two low-mileage Win7 laptops can be upgraded; they don't have the hardware. They still run perfectly and provide all the functionality I need. Ending Win7 support -- and breaking the browser -- would require me to not only replace my laptops (one for daily use, one for travel), but also two printers (a multi-function and a larger photoprinter), and all the software I currently use. Upgrading to Win 11 would be a huge learning curve, and would entail an enormous expense for someone on a fixed income. I know from other forums that I belong to that many people still use Windows 7. I, and many others, have been loyal users of Firefox for over 20 years. Please show some loyalty to us, your long-time supporters. As some other people have suggested, I would be happy to contribute to the expense of Mozilla extending support for Win 7. Thank you.

When is the expiration date for certificates after Firefox 128?

I have a MBP 2015 running Mojave, and am on Firefox 115.20esr, can I upgrade to 115.3.1esr on Mojave and avoid the certificate expiration issue? I can't go past Mojave on my computer because I have software I use for work that isn't 64 bit. Thank you

I have a MBP 2015 running Mojave, and am on Firefox 115.20esr, can I upgrade to 115.3.1esr on Mojave and avoid the certificate expiration issue? I can't go past Mojave on my computer because I have software I use for work that isn't 64 bit. Thank you

The Firefox 115.20.0esr (115.twenty.0esr) is the current update (released Feb 4, 2025) for 115 ESR. The Fx 115.3.1esr (115.three.one esr) was released back on September 28, 2023. https://www.mozilla.org/firefox/releases/

So Fx 115.3.1esr would be a downgrade and not meet the minimum requirements of Firefox 115.13.0esr (115.thirteen.0esr) to not be affected by the root certificate expiration.

Sorry I got it backwards I am on I have a MBP 2015 running Mojave, and am on Firefox 115.3.1esr, can I upgrade to 115.20esr on Mojave and avoid the certificate expiration issue? Thank you!