Firefox Community Forum

blocking pages https://www.ui-deref.com/r/?to=https://data.notification-htp.dish.com/ee/v1/click%3Fparams%3Dv1.10COjSKNA5PrObazTisehHaAu92BIO9JYdMGyGMpqr4WinxM1dh598psfuBG2Wz_fojlM5iQAf-FP0Yp880Ggw3gKu5pzo7jx1Ppx5OO1gwVBBlGYnT9S59VME_SDZ4tOwNJLJfL_gkeymBeqv6rS2DGd2cIo99fV_u6h4lDyrz0Q9mGuznkCNdyWj4qmM1P_6d6h4x64pvyOqe0xdgKZ7GjBSN_7DQX93YU52up00cKGoGAqn1waXAs2i2BHrkDY7EBo0thuq9vVSSsoX9hCDLXXj-eloVqMfSEN1Z-WS44m7UglPbfk3MNhdAWomTGoa6Rfs0DfnCIh_yZ3Sl6JJXpozo4O_o%26pid%3Dv1.sBhGBFuph3l-jqvOcGhIFPgusFRIbkBGNwIoYDMnY3oBzt0CKL1I9dinuyDWSCWANt0cTTruwBgOcAUh29cgLEizf5Jf%26tuid%3D6a565e3493a2c601fb9af049%26configId%3D8bdd7ab2-db13-479e-981f-ae95ef3a097e&tt1=gkXntVe5gsurV2prJkSNY57hq7GBiBnCWyIYHRXeOSj2ymRqdjtlag9giqYJriRe1azJHHJKR9Q9spkamVkkAE22WHUzhjffZPft1uqF8zS

I am running Firefox version 153.0.1 on a 64bit install of Windows 11.

A few days ago I had to factory reset my computer, including a clean Windows install. Since then, when attempting to access https://vodafone.cz/muj/prihlaseni, I get an Imperva Error 15 "Access Denied" error screen - screenshot attached here. Clicking the Imperva logo on the bottom of the error message leads to https://www.imperva.com/why-am-i-seeing-this-page/?src=23.

I was able to access the site in the past, most recently on July 8, 2026 - this would have been Firefox version 152.0.5.

This error persists in troubleshooting mode but not in private/anonymous (with or without extensions enabled), nor does it appear in Microsoft Edge or Firefox on Adroid.

Clearing cookies and cache did not help - in fact the error first showed up on a clean install of Firefox, when there weren't any cookies or cache stored yet. I've tried different DNS over HTTPS settings and listing the site as an exception in settings, but none of this made a difference. Enabling Firefox's built in VPN also made no difference, regardless of the selected location.

I found a recent post (https://support.mozilla.org/en-US/questions/1588627) describing a similar issue on a different website and tried the suggestion listed there to try a fresh profile - this seemed to work, but within a couple of minutes of browsing the error message returned. I've even reinstalled Firefox entirely, but this too did not help for long.

Interestingly enough, the error message lists a proxy IP address (not blacked out on the screenshot) despite the fact that I am not using a proxy.

The website provider's tech support claims this is an issue on the user side, not theirs - they have not been able to replicate the issue.

Is there anything I'm missing that would explain why this is happening?

Thanks!

Chaque fois que je lance une recherche sur Qwant avec Firefox j'ai le message: "Qwant.com est temporairement indisponible" alors que ça fonctionne avec Safari une idée ? [redacted email]

Ich habe einen DEepl Pro Account. Mein Standardbrowser ist Firefox. Ich melde mich im Firefox-Browser für die Desktop-App an. Es erscheint der Hinweis: "Du hast dich erfolgreich angemeldet und wirst gleich zur App weitergeleitet." Die Weiterleitung scheint von Firefox blockiert zu werden (wozu eigentlich???). In den Einstellungen ist meine Präferenz für Deepl.com korrekt aktiviert. Ich möchte Firefox als Standardbrowser nicht aufgeben, doch das scheint die einzige bekannte Lösung zu sein, die sofort hilft. Ich nutze an einem PC mit Windows 11.

Meine Frage: Wo kommt dieser Bug her und wie muss ich Firefox genau einstellen, damit solche Blockaden nicht passieren?

(Ich beobachte solche dummen, unerwünschten Blockaden in Firefox leider häufig, nehme dann manchmal den Link und öffne ihn einfach in Chrome, was immer problemlos möglich ist. Ich möchte nicht die Funktionalität des Browsers mit endlos vielen "Sicherheitseinstellungen" erwürgen.)

I asked AI: "I'm being prevented from using options which cause pop ups but I don't think I've deliberately changed any settings. I want to use "analyze the board" on the Gameknot website but I'm being prevented from using it. How can I get it back?" I followed the instructions: "Mozilla Firefox: Click the three lines (top right) > Settings > Privacy & Security > Permissions. Go to the "Pop-up windows" section and click Exceptions, then add https://gameknot.com" but I haven't re-acquired use of the pop up I ant to continue working. I want it back and its extremely irritating as the work around is very long and boring.

I have been using mail.com for over 20 years with no problems. This past week I started getting the attached error screen whenever I click on a link embedded in my email (for example, a link in an email from the Washington Post to the text of a full article on the Post's website). I've tried adding this site to my exceptions list, but this screen still keeps popping up. When I click on the "ignore the risk" link I get another error screen -- "Error 400 -- bad request." How can I fix this?

websites are being blocked when I click on links from my email account and I don't know why but I also want it stopped the websites are Stage32.com and https://course.fp-platform.online/learn/hRpTYcFi2UyZKzLm2gaOHg/theory

I use a site nextdoor.com and get email notifications. On opening the email, I see the option to view the comment, on clicking on view, this is what happens: . "The site ahead may contain harmful programs

Firefox blocked this page because it might try to trick you into installing programs that harm your browsing experience (for example, by changing your homepage or showing extra ads on sites you visit).

Advisory provided by Google Safe Browsing." And I can go not further. Why is this happening? How do I dump it and proceed with using nextdoor as normal. gargle is a blight on all users, and I want nothing to do with them. Is it time for me to change browsers?

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.

I turn that off and still no Twitter and your system turns it back on again all by itself, your settings are doing what they want to do, not what I SAY to do. Now, I cannot get into Twitter.

I cant use firefox to connect to mail.com. I can connect by other browsers just not with firefox. Server Not Found

Firefox can’t connect to the server at 6938e629511d9131a58e28150289aa0a.safeframe.googlesyndication.com.