Firefox Community Forum

since my last update I am unable to access 4 web sites which I normally use.I have firefox ESR and am on windows 7. Edgesuite is blocking two of my sites, Sephora and Argos and QVC tells me they are unavailable. Scottish Power tells me there is a client error.

Please help.

Suddenly i do not have access to a website and only this. the domain is wetranfer.com Actually i do not have access with any browser. not only mozilla firefox I use the default Microsoft defender but i can't find anything in firewall that blocks access to this site. Any help?

Accessing Planefinder.com. Have done so many times. After checking on a flight multiple times today, I acquired a notice that said I was blocked from accessing. Is this a scam? It says I entered a word or phrase that was unacceptable and thus am blocked. I can still use Planefinder on my cell phone. I only enter the plane information that is called for. What is going on?

I suddenly can no longer get my Gmail to appear in my Firefox browser. (I CAN get to +use Google.com, but when I try to go to https://mail.google.com/mail/u/0/#inbox", I just get a blank white page.) I did not (to my knowledge) change any settings or have some strange thing happen. Please help!

I'm building a website from scratch and its going great. I just tried to implement a CSP and it worked except for one small section of my website that allows a user to upload an image and that image is supposed to be displayed back to the user. Anyways long story short the CSP blocked me so I tried to whitelist data: and it still didn't work. defeated I removed the CSP from Nginx to work on it later but when I went to try and test again I get this error. ``` Content-Security-Policy: The page’s settings blocked the loading of a resource (img-src) at data:image/webp;base64,UklGRqbeAABXRUJQV… because it violates the following directive: “default-src 'self'” ``` I have confirmed with Curl and by inspecting the network tab that there is no CSP included in the headers anymore. I have restarted Firefox, created a new Firefox profile, and cleared my cache to the end of time and yet still the error persists. I don't know where or how Firefox is storing website headers but they persists and also apparently work between profiles an implication I'm not going to delve into here. If someone could point me to the file where the headers are stored so I can delete it that would be wonderful.

specs Qubes OS 4.2 Mozilla Firefox 140.4.0esr

So i have freshly installed firefox, every time i look up something on google i don't get any AI overviews, but when i use google in a private window google's ai overview works in there. what is going on? (keep in mind i have ublock origin activated on both windows but the ai only works in private mode where im not signed in)

Meldung: Lassen Sie challenges.cloudflare.com zu, um fortzufahren. Image Siehe Bild Click auf Erlauben hat keine Auswirkung

Firefox is preventing me from going to certain websites because it is telling me I am using adblocker but I have none installed.. I am trying to play around with the settings but I still can't do it. Is there an inbuilt adblocker? I need help please...

I access Bluesky (bsky.app) for business on my PC. Since the last update, I've been unable to access Bluesky from my regular Firefox browser. I can using other browsers, the mobile app, and, oddly, in Firefox private browsing. I've cleared my browser history, cookies, etc. I restarted the computer. I logged out of Bluesky (and now can't log back on the regular PC account because it claims I'm not connected to the internet). Yet, I had no trouble logging in using private browsing.

I've looked through settings, etc. and can't figure out what could be limiting my ability to access this website.

Our team has already tried to fix the issue for a week now and none of the approaches seem to fix the issue. Does the Firefox dev department have any hints or clues for us?

Short description: Firefox network.lna.blocking blocks same-origin/loopback requests when the page is controlled by a Service Worker

Symptom: Login via OIDC fails in Firefox (the backend call after the IdP redirect is blocked). The error disappears if either network.lna.blocking=false is set or the Service Worker is disabled.

Environment: - Frontend (react) and backend run on the same machine (loopback/localhost)—no cross-network scenario. - Firefox with active network.lna.blocking (experimental Local Network Access feature, Chromium’s equivalent is Private Network Access).

Root Cause (Analysis): 1. apps/react/sw.js registers a global fetch listener via Workbox and calls workbox.core.clientsClaim(). This causes every open page to be immediately controlled by the Service Worker. 2. registerServiceWorker() is called unconditionally on every app start, regardless of authentication state—even on the login/OIDC page. 3. The app uses hash-routing (URL fragments like “#/oidc”); the login page and the rest of the app share the same document URL, so you can’t restrict the SW scope to “everything except login.” 4. Once a page is Service-Worker-controlled, every fetch—including requests not explicitly handled by Workbox routes—first goes through the SW’s fetch event (default behavior when any fetch listener is registered) before proceeding to the network if it isn’t intercepted. 5. Hypothesis: Firefox’s LNA implementation doesn’t correctly inherit the address-space classification (loopback/private/public) for SW-forwarded requests across the controlling client. A direct document fetch (loopback→loopback) is allowed, but an identical target fetch routed through the SW is blocked.

Reproduction (minimal): 1. Use Firefox with network.lna.blocking=true (the default in affected versions). 2. Load a page that registers a Service Worker with a fetch-event listener (e.g. via Workbox precacheAndRoute + clientsClaim()). 3. Ensure both the page and the target resource are served from localhost/loopback. 4. From the SW-controlled page, call fetch() against the loopback target resource → the request is blocked. 5. By comparison, the same fetch from a non-SW-controlled page succeeds. 6. Setting network.lna.blocking=false also allows the fetch to succeed under SW control.

Excluded Causes: - Different address spaces for frontend/backend (both are on the same loopback machine)—ruled out. - Misclassification due to redirect_uri or cross-origin navigation—the OIDC redirect is a top-level navigation (unaffected); only the subsequent backend call (token exchange/session validation in SsoLogin.tsx → ssoLoginSubmit) fails.

Google has not worked on Firefox for me for the last 2-3 days and always gives the same error message: " The connection has timed out. The server at www.google.co.uk is taking too long to respond."

This issue only exists in Firefox, not in Opera or Edge. I have tried clearing the cache, using using Troubleshoot Mode, changing proxy settings to No Proxy, disabling antivirus, restarting the browser, and restarting my PC. None of these have made any difference, not even a slightly different error message. Google does, however, still work on my Firefox for Android.

As far as I can tell so far, Google is the only website affected by this issue, every other website works fine. Gmail and YouTube also still work fine, it's really only Google search.

Any help with this would be greatly appreciated!