When I click on Firefox and the to my email it says there is a problem with my internet. My internet is up and running fine. I have done everything it says Firefox can't connect to the server at mail.yahoo.com.

(Sorry if the wrong area.)

I'm curious and play with Node-Red a lot.

Just now I am playing with the `http-request` to explore web pages.

I press the `F12` key and the tools pop up and I go through some basic things.

I see/get just about nothing. See pic (Don't know to make it inline.) But the name says it all.

So I've pressed the `F12` key, clicked on the NETWORK and REFRESHED the page.

Now with Chrome.

Whole different set of stuff.

Someone - please. What's going on? I'm not understanding the huge difference with how things are shown.

Setup: macOS Tahoe (26.4) and Firefox 149.0

=

Behavior: Out of the blue this morning, every website I try to visit in Firefox returns "Looks like there’s a problem with this site". Every other browser works fine.

Things I've tried, that haven't fixed it: - Ruled Out DNS: Sites like 1.1.1.1 and my home router's IP return the same issue in Firefox, but also resolve in any other browser. - Firefox Safe Mode: no fix - Deleted All Settings, Reinstalled Fresh: - Removed the Firefox App, deleted:

       - ~/Library/Application\ Support/Firefox
       - ~/Library/Caches/Mozilla
       - ~/Library/Caches/Firefox

...and then downloaded and installed 149.0 fresh. - Refreshed Firefox (via [link] - about:preferences (toggled between FALSE and TRUE, testing each time) via this YouTube video

- network.dns.disableIPv6

- network.dns.disablePrefetch
- network.dns.disablePrefetchFromHTTPS
- network.dns.disable

....and in desperation, I checked my Mac for Malware (clean)

I'm at a complete loss: every other browser works, but Firefox is a 100% fail for all websites. Any thoughts?

I know little to nothing about computers. My Mozilla account says it is disconnected whenever I come online. I do not manually disconnect ever. Keeps telling me that it cannot detect proxy even though my proxies are set to off.

i have problem with setting up my proxy. i choose manual proxy configuration, fill the HTTP Proxy & port. When i click ok then input username & password but it keep asking for the username & password. (I have asked the proxy provider they say the proxy is good, no problem)

Hi. I have a Dell Inspiron, it’s a few years old, and my computer is running windows. Today I was on a website, doing my assignments as usual when randomly the internet stopped working on the browser (I was on the web for about an hour before this). There was no change to my behavior, I had been on the same site for the whole hour, and had been interacting with the site during that time. My computer still says it’s connected to the internet, and I was even able to play an online game on my computer that I had downloaded, so it looks like my computer is connected to the internet. I’ve tried to clear my cache and open private windows but that didn’t help.

Current Behavior When Firefox is set to offline mode (File → Work Offline), the Developer Tools Network tab does not display request body of requests that web applications attempt to make. This creates a significant gap in debugging capabilities, as developers cannot inspect request payloads details that would normally be visible.

Requested Enhancement Enable the Network tab to capture and display attempted network requests payload even when offline mode is enabled

Firefox 147.0.4 on macOS 26.3 does not work via SOCKS proxy.

Firefox 147.0.4 on Windows 11 x64 works fine via the same intranet SOCKS proxy, with exactly the same settings.

The advantage of Firefox is its flexibility. It supports its own SOCKS proxy settings, independent of systems-wide ones. Unfortunately, it seems this Firefox feature is broken on macOS (but Windows version works perfectly).

Safari 26.3 (21623.2.7.11.6) and DuckDuckGo 1.177.0 (625) web-browsers that use system-wide macOS SOCKS proxy settings also works fine with this intranet proxy server. So it seems SOCKS proxy server itself is OK, and the problem is confined to Firefox on macOS.

Has anyone seen Firefox 147 on macOS work via SOCKS proxy? Is there a principal difference between how Firefox handles SOCKS proxy on macOS vs. Windows? What might be the best way to address the problem on macOS?

Thanks!