Hi,

I understand that Firefox Sync did not connect to your mobile device on this occasion, but hopefully I should be able to help you force a Sync event to take place.

Assuming you have connected the same Sync account on both your mobile and desktop copies of Firefox:

In Firefox on your mobile device:

1. Go into the Settings menu and select Firefox Account.
2. Tap on Synchronise now.

This will “force” a synchronisation of the data that is on the local device storage.

Hello

These similar discussions. https://connect.mozilla.org/t5/discussions/dear-brilliant-mozilla-engineers-your-newest-firefox-browser/td-p/120599 https://connect.mozilla.org/t5/discussions/latest-firefox-browser-extended-support-release-115-33-0esr-64/td-p/120024

I have had an actual reply from an Akamai community post:

Based on the Reference Error: #18.d00e2017.1774501997.9b9fca73

The request matching the error page was denied by Akamai Bot Manager on www.airindia.com / with BOT: UNKNOWN BOTS (SCRAPER ANOMALY), Bot Score: 72, and Response Segment: Aggressive Response. In Akamai’s model, Aggressive Response is the highest bot-score bucket, where stronger actions such as Deny can be applied, which is why the request returned HTTP 403.

The WSA report shows the following triggers:

   3903002 - Outdated Browser Version Anomaly (36+ months)
   3903009 - Comes from Linux Systems

This indicates that the request was evaluated based on browser fingerprinting and request characteristics, and not solely on IP reputation.

Why some Firefox versions work and others do not:

This behavior is consistent with how Bot Manager evaluates requests. Different Firefox versions can produce different request signatures such as user-agent and browser fingerprint characteristics.

Based on the WSA entry reviewed for this specific reference error, the request was scored into the Aggressive Response segment and denied with 403. This suggests that certain Firefox/Linux request patterns are being scored differently under the site’s Bot Manager policy, which explains why some versions work while others do not.

=

As I understand, each Akamai customer (website operator) has their own controls and dashboard, so you won't get the same errors for every website or browser version.

I have solved my immediate problem by installing Firefox 140.8.0esr from the Rocky 8 Linux distribution.

Advax, how do you do that on a window system please? Thank you.

Advax, how do you do that on a window system please? Thank you.

Linux users can easily use the current Firefox versions like Fx 149.0 release and the Fx 140.9.0esr as they can get internal Firefox updates if they use the tarball version from Mozilla.

For Windows 7, 8, 8.1 OS users however the most current you can run is Firefox 115.34.0esr as 116.0 and later requires Windows 10, 11 to run.

Re. Windows, I suspect James is correct. For me, the latest RPM I could find that just installs with the package manager was Firefox 140.8.0esr. Later versions built for Fedora require later libraries, which I was able to test in a chroot environment. I haven't looked at the tarball version; in general those can conflict with installed software and can't be easily updated or removed.

To run the latest Firefox version in a virtual machine on Windows, of course you'd need to get a newer version of Windows to put in the VM. Or, perhaps, a small current Linux installation. In Linux, there are things like Flatpak and Appimage that allow programs bundled with all their libraries to run in an OS that doesn't natively have the correct environment.