1904187 - After the last update to 127.0.1, many websites are no longer accessible with Firefox 64-bit.

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[d-kle]

Attachment: Screenshot 2024-06-22 080138.jpg

Steps to reproduce:

Firefox update to 127.0.1

Actual results:

Since the update to 127.0.1, an extremely large number of websites are no longer accessible with Firefox 64bit. This also includes the websites of www.mozilla.org. The error message always appears: Connection failed.

Strangely, the same errors also occur with the Firefox clones Waterfox 64bit (G6.0.16) and PaleMoon 64bit (33.2.0) after the last updates were carried out there too.

The updates were carried out on all of the browsers mentioned on June 21, 2024.

Nothing was changed on the system (Windows 10 Home), the firewall (ZoneAlarm), the antivirus program (Avira) and the network settings before and after the updates.

Only Waterfox Classic (2022.11) and Opera (107.0.5045.21) run without errors. I am using Opera for this bug report.

"Include your browser's user agent string in the error description. This may be helpful for developers working on your issue." Unfortunately, I can't do anything with the 'user agent string'. Sorry!

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Robin Steuber (she/her) [:bytesized]]

I really doubt this is an update issue. I'm going to guess that :flod got it right and revert this.

Comment 3

[Francesco Lodolo [:flod]]

I'm guessing you didn't mean to revert it back to localization. I'll try with Firefox::General to avoid a constant ping pong with bots here.

Personal suggestion would be to start by disabling Zone Alarm.

Comment 4

[d-kle]

I looked into the problem again at the weekend and ran Firefox (127.0.1) under various conditions.
In normal mode and in troubleshooting mode with …

... ZoneAlarm temporarily deactivated. Result: Negative.
... with additional the anti-virus program temporarily deactivated. Result: Negative.

I also subjected Waterfox 64bit (G6.0.16) and PaleMoon 64bit (33.2.0) to the same procedure. Result: Also negative. Many websites are still not displayed on all three browsers and the error message 'Connection failed' keeps appearing.

Various searches on the Internet were also unsuccessful. Overall result: Negative

By the way, since the last update, the update function no longer works in Firefox (127.0.1), as can be seen in the screenshot. On the other hand, it is intact in Waterfox 64bit (G6.0.16) and PaleMoon 64bit (33.2.0).

I don't want to reset or reinstall Firefox, as this would mean losing all of my individual settings, including the add-ons. Setting everything up again would be tedious. And success is not guaranteed.

It wouldn't make sense either, because the exact same problem exists not only in Firefox (127.0.1), but also in the Firefox clones Waterfox 64bit (G6.0.16) and PaleMoon 64bit (33.2.0), after all of them were updated on the same day. That's strange.
All three browsers use the Gecko browser engine.

It is noticeable that the Firefox clone Waterfox Classic (2022.11), on the other hand, works flawlessly. This browser also uses the Gecko browser engine. However, this Waterfox variant receives updates much less frequently and the last one was months ago. !

I'm running out of ideas. It's also annoying that I've already invested so much time without getting any closer to a solution.

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

Moving to Networking. Networking triagers, did we recently change anything that might effect how Firefox on Windows interacts with proxies or firewalls or might otherwise cause this sort of behavior? If not, is there NSPR logging that could help?

Comment 6

[edgul]

Thanks for the report.

1. Can you try the following to see if any of it resolves the issue:

• using about:profiles to create and switch to a new profile
• using private mode
• using a nightly version of firefox
• I see you've tried disabling anti-virus, can you try disabling all other anti-virus again along with any VPNs? I would probably try to startup without anything running, even try booting in safe-mode

2. It might be helpful for us to get some logs of the failures. You can record logs with about:logging, log to a file and send the logs to [e-mail].

Comment 7

[d-kle]

Thank you for all the tips so far.

Basically, I would like to point out the following again: Before and after the simultaneous updates of Firefox (to version 127.0.1) and the two clones Waterfox 64bit (to version G6.0.16) and PaleMoon 64bit (to version 33.2.0), I did not change anything on the system (Windows 10 Home)!

If these three browsers no longer work properly after the updates, then it cannot be the system's fault. In this respect, I think screwing around with the system settings (deactivating the firewall, deactivating all antivirus programs and all VPNs, starting in safe mode, etc.) is the wrong approach. I have already tried everything. Result: Negative. But I wasted a lot of time at the weekend.

I have also already tried using a new profile, using private mode, and restarting in safe mode with Firefox and the two clones. Result: Negative. No change at all. 'Connection failed' appears on a good 50% of all pages accessed. Also on https://bugzilla.mozilla.org/show_bug.cgi?id=1904187

Unfortunately, I don't have the time to spend hours on experimental or beta versions of Firefox, such as Firefox 129 Nightly. I have two children, a job, and a full family schedule. The hassle with the latest Firefox updates and the two clones is enough for me.

Iprobably 'll dispose Firefox at some point, especially since the update function also not anymore works.

Perhaps another important note:

There are lots of people who are faced with the same or a similar problem, but don't get too deeply involved with computer technology and related things. They want clean programs and a quick and understandable solution to errors.

I think I'm still fairly fit in this area. My brother, on the other hand, wouldn't even understand half of what you and the other commentators write. In other words: It is often forgotten to formulate instructions in such a way that people like my brother can understand and use them, i.e. people who are completely unfamiliar with your specific terminology.

Even I can't do anything with terms like „NSPR logging“ or „Networking triagers“. (Dan Mosedale) Sorry. And I also had to research what a „nightly version of firefox“ is. (Ed Guloien)

I don't have time to log the errors that occur now. Maybe later.

Comment 8

[Kershaw Chang [:kershaw]]

Thank you for your detailed explanation and efforts so far. To help us better understand and diagnose the issue you're experiencing, could you please provide an HTTP log? This will give us more insight into what's happening behind the scenes and help us find a solution more efficiently.

In about:logging, Please select logging to a file and send the file to [e-mail]. Thanks!

Comment 9

[d-kle]

On June 27, Firefox performed an automatic update to version 127.0.2. Since then, the browser has been working smoothly again. The same goes for Waterfox and PaleMoon.

What did Mozilla put in the update because the errors suddenly disappeared?

I hope it stays that way.
;-)

Comment 10

[Valentin Gosu [:valentin] (he/him)]

Assuming there haven't been any more issues, I'll close this one as WORKSFORME.
Please reopen of file a different bug if you encounter any more issues.
Thanks!