techsupport

2497 readers

6 users here now

The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.

If something works or if you find a solution to your problem let us know it will be greatly apreciated.

Rules: instance rules + stay on topic

Partnered communities:

You Should Know

Software gore

Recommendations

founded 2 years ago

MODERATORS

GatoB

[SOLVED] Firefox Can't Connect to Specific LAN IP (infosec.pub)

submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/techsupport

19 comments fedilink hide all child comments

This is a really weird problem that I can't seem to track down further. Perhaps a creative person could suggest some test ideas. Here are the facts:

Firefox "Unable to connect" to my LAN server (a router) at 192.168.0.2 port 80.
Network error is specifically "NS_CONNECTION_REFUSED".
Wireshark on a Raspberry Pi placed between the laptop and server shows no packets exchanged trying to connect. Any packet containing 192.168.0.2, any port.
Chrome and Safari work just fine on the same machine. I can see the packets in Wireshark. This validates my test setup works.
Curl works, loads the web page. I can see the packets.
I have reinstalled, refreshed, removed all extensions, cleared all history and cookies in Firefox and still cannot load the page.
Firefox in Safe Mode cannot load the page.
Disabled DNS over HTTPS, made sure No Proxy is selected in network settings. Still cannot load the page.
Disabled IPv6 in Firefox with about:config setting. Still fails.
I have no security software installed of any kind on this Mac. No antivirus or firewall except the default OS one.
Turned off Mac built-in Firewall. Still unable to connect.

Why is Firefox apparently refusing to connect to my server? Other LAN IP addresses work fine, even local ones. It specifically hates this one.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 3 weeks ago (1 children)

No insult taken! I reset Firefox and I’m using a new profile. There are no extensions installed.

I’m not sure how I would go about debugging Firefox further to understand why it doesn’t want to attempt connecting to that IP. Currently I agree with you. It seems like there’s some bug with Firefox itself or perhaps an unexpected configuration hidden elsewhere on the system on which it depends but nobody else.

[–] [email protected] 2 points 3 weeks ago

You might try a quick shell script to set NSPR_LOG_MODULES and NSPR_LOG_FILE to "all" debug mode to fish for some clues. https://firefox-source-docs.mozilla.org/nspr/reference/nspr_log_modules.html#nspr-log-modules