I-Firefox Community Forum

This is the message I get when I try to access Kroger.com. It has always worked before and nothing has changed on my computer. No issues accessing other sites.

You don't have permission to access "http://www.kroger.com/pr/pickup-delivery-savings-4?" on this server.

Reference #18.13200117.1772323532.fee04a0c

https://errors.edgesuite.net/18.13200117.1772323532.fee04a0c

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)

i HAVE CLEARED THE CACHE, DATA, HISTORY, everything i CAN THINK OF. aLL WEB SITES WORK FINE except gO dADDY.

Access Denied You don't have permission to access "http://www.godaddy.com/" on this server.

Reference #18.6bf7d517.1771978173.2cedcff8

https://errors.edgesuite.net/18.6bf7d517.1771978173.2cedcff8

Privacy Policy from TD Bank (https://easyweb.td.com) appears at the bottom of every page change, no matter if "Accept All" has be selected. Moving from one account to another causes this pop up to appear. This does not happen with Chrome. With Chrome, one "accept all" has been chosen, the pop up no longer appears

If I turn off Enhanced Tracking Protection the problem seems to stop.

Hello. I did not receive an answer to my last help request. A Block Ad does not allow me to access this site: https://www.tempo.pt/lisboa.htm?utm_source=newsletter&utm_medium=email#-0eebc5457c97ef8bca0b518ed4194951 I need some help, please. This is a site informing me about the weather. Thank you.

Heyo! So, I've had this ongoing issue with Firefox for quite some time around trying to access the Newgrounds website, but failing to do so. I have tried several things such as disabling the enhanced tracking setting, disabling DNS over HTTPS, forcing cookies and third-party popups to be allowed but that does not work what so ever and disabling enhanced tracking is greyed out so it's not even clickable to toggle off.

One thing that did work was to use the built-in VPN, but I really don't want to constantly have to use a VPN to browse one singular site every time I want to access it. So now for the question. Has anyone else experienced this? And if you have, how did you solve it if at all?

Hello- about 6 or 7 months ago I started noticing issues where I will type in a web address or a search term and it will not do anything after pressing enter. Just sit there blank. This does not happen all the time but is happening enough that it is frustrating. for example I could type in bank of america or amazon.com or something like that and it will not do anything. No spinning wheel no anything. I can delete what I typed in and try typing something else and the same thing. I can open a new window and try searching again and it will do the same thing. Then a few minutes later I can try it again and it will work fine. BUT what DOES work always is if I open a new private window and search that way it will always work.

Any thoughts? i've deleted cache/browser history, cookies, un-installed and re-installed. I have the firefox is up to date message. I am using FIrefox 151.0.3 64 bit Using windows 11 Home version 25H2

I use Google as my default search engine in firefox.

Thanks

Ryan

I waited for a long time to do an upgrade to avoid problems. Today finally I decided to upgrade to the latest version of Firefox for my iMac, 147.0.1. Before the upgrade I successfully used with zero issues gemini.google.com/app . Now the website comes up, but regardless what I enter as a question I only get an error message stating "something went wrong". The same website works with no issues (TG) with Safari.

Does anyone else experience the same? Is this a known bug with this version of Firefox? Is there a work around for it? Is the solution just using Safari?

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!

When I try click to search on a word in Firefox on my iMac, which I've done productively for years, I'm now, without having changed anything about my settings. faced with

Hmm. We’re having trouble finding that site.

We can’t connect to the server at gb.search.yahoo.com.

How can I get rid of this?

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 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!