I-Firefox Community Forum

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?

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?

I turned off my HP computer with Windows 11 on August 1. Everything was working fine at that time. When I turned it on again on August 18, everything worked except email. I can get email on my iphone, but not on my computer. I spent over an hour trouble-shooting with someone representing my email server, tds.net, with no resolution. I tried to access my email thru Firefox, my usual browser, as well as thru Edge. The message I get when trying to access my tds email is: "The connection has timed out. The server at mail.tds.net is taking too long to respond." I then went to an IT specialist who tried everything he could, including disabling Bitdefender, and nothing worked. I then tried to open an email account with gmail.com and received this message: "The page isn’t redirecting properly. Firefox can’t connect to the server at accounts.google.com." I don't know what else to try. Everything I read said the it is likely a problem with my anti-virus software, but the problem still exists when that is turned off. Is there anything else I can try???

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!

i looked up lots questions and solution. nothings seems to work. i did all Troubleshoot and diagnose Firefox problems. cleared cache, restarted firefox, refreshed. everything I could do. nothing works.

could you tell me what else I can try?

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!

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.

As of about last Thursday, I have been unable to access my Isomedia.com SpamTitan01 account. I usually have a trove of spam messages, which I look at and delete, except for the one or two that are real emails. For the last 5 days My Titan vault is empty, though it is trying to retrieve data. My address is [redacted] @pioneernet.net Could it be that a Firefox update is preventing me from access?

Nancy Moore

Up until today (3/26) , accessing CompuServe (AOL) mail was not an issue. Now , getting to the site is OK , but when it attempts to access the mail , I get:

Firefox Can’t Open This Page

To protect your security, compuserve.com will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.

What changed overnight? After getting the message , if I click on Mail , it works just fine. There is also a similar message when closing the page , but not every time.

Any clues?

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

Dell updates to my Dell computer are blocked

'Problem loading page':

The page isn’t redirecting properly

Firefox can’t connect to the server at www.dell.com What can you do about it?

The site could be temporarily unavailable or too busy. Try again in a few moments.

I was having an odd issue the other day, that I now solved by comparing the settings on a working Firefox profile with mine.

For some reason, on one of my multiple Firefox profiles a list of web apps wasn't working. Among them were Discord, Miro Board, and Google Pay. I was suspecting that they all had the same issue, but didn't know what it was at that time.

The security settings were the obvious suspect (Ad-blockers, DNS, HTTPS enforcement etc.) because clearly something was being blocked, however nothing helped. The solution was in the Network settings. (See screenshot) I was using Manual proxy settings from the time I messed with I2P networks (or something similar).

I am not sure why having a proxy to localhost (127.0.0.1) on HTTP would somehow cause very specific major apps to stop working, while others keep working fine, but it happened to me anyway.

For anyone in a similar situation, with those particular apps not working, check your proxy settings.

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?