As always feel free to add to this thread if you see other news or common problems popping up with the release as it goes live to more users. If you're a user yourself looking for help though, post in the support forum instead pls :))
Tomorrow, April 16, is the release date for Firefox 125.
These links will contain the usual bits of information for the new version once the release is live:
* release notes: https://www.mozilla.org/firefox/125.0/releasenotes/
* sec advisories: [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox125]
* complete list of changes: [https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&f1=target_milestone&o3=equals&v3=Firefox%20125&o1=equals&resolution=FIXED&o2=anyexact&query_format=advanced&f3=target_milestone&f2=cf_status_firefox125&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&v1=mozilla125&v2=fixed%2Cverified&limit=0]
* developer notes: [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/125]
As always feel free to add to this thread if you see other news or common problems popping up with the release as it goes live to more users. If you're a user yourself looking for help though, [https://support.mozilla.org/questions/new post in the support forum instead] pls :))
Thanks for starting this thread as always, Philipp!
@Everybody please note that the release of Firefox 125 is postponed to an undetermined date due to a late-breaking bug that affect macOS users running non-admin accounts being potentially unable to update after they install Firefox 125 (bug1890764).
The team is currently building version 125.0.1 as soon as they can to address this delay. We'll update as we know more.
Thanks for starting this thread as always, Philipp!
@Everybody please note that the release of Firefox 125 is postponed to an undetermined date due to a late-breaking bug that affect macOS users running non-admin accounts being potentially unable to update after they install Firefox 125 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1890764 bug1890764]).
The team is currently building version 125.0.1 as soon as they can to address this delay. We'll update as we know more.
We ended up releasing 125.0.1 today. Please always advise people to update to 125.0.1 instead of 125. And if you see any trending issues, please raise it here.
We ended up releasing 125.0.1 [https://twitter.com/FirefoxSupport/status/1780272821329068412 today]. Please always advise people to update to 125.0.1 instead of 125. And if you see any trending issues, please raise it here.
Thanks for flagging this, James! The update issues from Monday/Tuesday were Mac-only, so any Windows issues would be unrelated. I chatted with our Release managers and wanted to share some notes from them in case we want to try troubleshooting with the users reporting this:
A recent Reddit post indicated that NordVPN IIRC interfered with Fx updates
In the past we have seen various antivirus software interfering with Fx updates
Hope this helps!
Thanks for flagging this, James! The update issues from Monday/Tuesday were Mac-only, so any Windows issues would be unrelated. I chatted with our Release managers and wanted to share some notes from them in case we want to try troubleshooting with the users reporting this:
* A recent Reddit post indicated that NordVPN IIRC interfered with Fx updates
* In the past we have seen various antivirus software interfering with Fx updates
Hope this helps!
If you see users having problem with download on 125.0.1, please see the Unresolved section from the 125.0.1 release note which I quote below:
The recently-shipped functionality more proactively blocking downloads from untrusted sources is not working as intended and causing impaired ability to download files in legitimate situations. We are working to address this ASAP via disabling the feature remotely for existing installs and will also revert the change for the upcoming Firefox 125.0.2 release.
Hey folks,
If you see users having problem with download on 125.0.1, please see the Unresolved section from the [https://www.mozilla.org/firefox/125.0.1/releasenotes/ 125.0.1 release note] which I quote below:
<blockquote>The recently-shipped functionality more proactively blocking downloads from untrusted sources is not working as intended and causing impaired ability to download files in legitimate situations. We are working to address this ASAP via disabling the feature remotely for existing installs and will also revert the change for the upcoming Firefox 125.0.2 release.
</blockquote>
Hey folks,
If you see users having problem with download on 125.0.1, please see the Unresolved section from the 125.0.1 release note which I quote below:
The recently-shipped functionality more proactively blocking downloads from untrusted sources is not working as intended and causing impaired ability to download files in legitimate situations. We are working to address this ASAP via disabling the feature remotely for existing installs and will also revert the change for the upcoming Firefox 125.0.2 release.
Users can disable the extra protection by toggling dom.block_download_insecure to false in about:config. It's possible that's what will get pushed out, but I don't know.
Meanwhile, any download that has these characteristics is likely to contain the wrong content after using the "Allow download" button:
Insecure HTTP protocol
POST request (user typically will not know the form submission method)
As of 3:48PM Pacific, I have the pref flip "study" installed. I'm not sure how often Firefox pulls these changes, but assuming it is at least a couple times a day, this should generally mitigate the problem for now.
''Kiki [[#post-87395|said]]''
<blockquote>
Hey folks,
If you see users having problem with download on 125.0.1, please see the Unresolved section from the [https://www.mozilla.org/firefox/125.0.1/releasenotes/ 125.0.1 release note] which I quote below:
<blockquote>The recently-shipped functionality more proactively blocking downloads from untrusted sources is not working as intended and causing impaired ability to download files in legitimate situations. We are working to address this ASAP via disabling the feature remotely for existing installs and will also revert the change for the upcoming Firefox 125.0.2 release.
</blockquote>
</blockquote>
Users can disable the extra protection by toggling '''dom.block_download_insecure''' to false in about:config. It's possible that's what will get pushed out, but I don't know.
Meanwhile, any download that has these characteristics is likely to contain the wrong content after using the "Allow download" button:
* Insecure HTTP protocol
* POST request (user typically will not know the form submission method)
Open bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1892069
'''EDIT'''
As of 3:48PM Pacific, I have the pref flip "study" installed. I'm not sure how often Firefox pulls these changes, but assuming it is at least a couple times a day, this should generally mitigate the problem for now.
[[Image:Remote pref flip for dom.block_download_insecure]]
''Mandy [[#post-87394|said]]''
<blockquote>* A recent Reddit post indicated that NordVPN IIRC interfered with Fx updates
</blockquote>
More specifically when the NordVPN "Web Protection" is turned on.
example from [/questions/1445030]
Hey everyone. Thanks to James & Mandy, I started investigating deeper into the Windows cases of auto-updates failing. Most of them turned out be caused by NordVPN's Web Protection feature (huge shoutout to Mandy for the tip!) & disabling it fixed the broken updates.
I had a suspicion the problem was going on for longer than we thought so I went back 2 weeks to try to find any missed cases. I replied to all the ones I could find but I feel like there might be more. But funny enough, the Windows users seem to be appearing more often since 125's Mac auto-update bug. Maybe they're related somehow.
Hey everyone. Thanks to James & Mandy, I started investigating deeper into the Windows cases of auto-updates failing. Most of them turned out be caused by NordVPN's Web Protection feature (huge shoutout to Mandy for the tip!) & disabling it fixed the broken updates.
I had a suspicion the problem was going on for longer than we thought so I went back 2 weeks to try to find any missed cases. I replied to all the ones I could find but I feel like there might be more. But funny enough, the Windows users seem to be appearing more often since 125's Mac auto-update bug. Maybe they're related somehow.
I filed [https://bugzil.la/1892521 Bug 1892521 - NordVPN's Web Protection feature is breaking Firefox auto-updates on a massive scale] for this issue. And included everything I could find. I CCed Kiki on it, just so she could track it. I couldn't find Mandy or JR on Bugzilla so I wasn't able to CC y'all. I also got one of the Release managers, RyanVM, CCed on it too. I hope this one gets resolved soon.
Someone reported this problem back on Feb 26, so its been happening in the wild since then.
[https://bugzil.la/1882059 Bug 1882059 - Firefox reports "Update check failed", potentially due to NordVPN Threat Protection]
In addition the ongoing issue with NordVPN, please be on the lookout for https://bugzilla.mozilla.org/show_bug.cgi?id=1892612 and tag as:
Bug1892612
Thank you!
Noah, thanks a lot for your investigation on the NordVPN issue. And Paul, thanks for tagging those conversation so we can track back on this issue easily in the future.
There's another incident with higher severity that the product team is investigating:
Firefox opens tab with IP address 0.0.0.1. Bug 1892612 is where you can find more information about it. If you see any mention of this problem, please tag the question with bug1892612.
Noah, thanks a lot for your investigation on the NordVPN issue. And Paul, thanks for tagging those conversation so we can track back on this issue easily in the future.
There's another incident with higher severity that the product team is investigating:
Firefox opens tab with IP address 0.0.0.1. [https://bugzilla.mozilla.org/show_bug.cgi?id=1892612 Bug 1892612] is where you can find more information about it. If you see any mention of this problem, please tag the question with bug1892612.
Hey folks,
please be aware of 125.0.2 that we are releasing today. Android 125.2.0 dot release is also coming in response to [https://bugzilla.mozilla.org/show_bug.cgi?id=1892069 Bug 1892069].
Desktop release note: https://www.mozilla.org/firefox/125.0.2/releasenotes/
Our [https://wiki.mozilla.org/Support/Firefox125 Fx125 wikipage] should be updated with this info as well.
Hopefully NordVPN removes the *.mozilla.org urls from blocklist soon as I wonder why they were even added in first place.
There is a KB article for the NordVPN Web Protection issue.
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-auto-update-issues
Hopefully NordVPN removes the *.mozilla.org urls from blocklist soon as I wonder why they were even added in first place.
We are continuing to make efforts to reach out to NordVPN (something I am involved in directly).
In other news: https://support.avast.com/en-us/article/aosp-firefox-discontinuation-faq/
Thanks Paul. Are you climbing NordVPN's corporate ladder to reach someone? I'm convinced that's the only way to raise the priority of fixing this issue. Short of getting the main @Firefox twitter account to @ NordVPN itself & @ their co-founder & their head of PR, Laura Tyrell.
And nice find on Avast ending their Firefox addon. Good riddance. One less antivirus addon for us to troubleshoot when it inevitably breaks browsing on Firefox.
Thanks Paul. Are you climbing NordVPN's corporate ladder to reach someone? I'm convinced that's the only way to raise the priority of fixing this issue. Short of getting the main @Firefox twitter account to @ NordVPN itself & @ their [https://twitter.com/tom_okman co-founder] & their head of PR, [https://twitter.com/laura_tyrell Laura Tyrell].
And nice find on Avast ending their Firefox addon. Good riddance. One less antivirus addon for us to troubleshoot when it inevitably breaks browsing on Firefox.
Hi,
I just found this thread about this error with NordVPN and Firefox updates, after I uploaded in anther support line.
https://support.mozilla.org/en-US/kb/update-failed-error-message-when-updating/discuss/12185
I just reported to NordVPN too.
Thanks!!
Hey folks, 125.0.3 is out yesterday which include the fix for bug1892612. Thanks to Soren for raising this issue so the team can take a quick action on this and thank you to everybody for your support on this release. I know this has been a difficult release so thank you all for being so patient and understanding. You all rock!
Hey folks, [https://www.mozilla.org/firefox/125.0.3/releasenotes/ 125.0.3] is out yesterday which include the fix for [https://bugzilla.mozilla.org/show_bug.cgi?id=1892612 bug1892612]. Thanks to Soren for raising this issue so the team can take a quick action on this and thank you to everybody for your support on this release. I know this has been a difficult release so thank you all for being so patient and understanding. You all rock!