techsupport
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:
I once had a similar issue (but not fully the same), alas I forgot how I fixed it.
Some suggestions:
- Any mention of *.0.2 in your host file? FF might read it differently from other programs
- if nothing there perhaps you can add a link to *.0.2 in the host file?
- clear the dns cache etc via ipconfig in a command prompt
- Firefox proxy settings, set something else, close ff, open it again then revert to no proxy
- Disable the FF safebrowsing thing (forgot the name and can't currently check)
- Disable FF secure dns features, don't let firefox choose one nor set a custom one, just put it on isp provided only <- also, use this one in windows tcp/ip settings, not a google one etc.
- is the subnet mask set correctly? If behind a switch and 2nd network/NAT
- make a new empty FF profile and try the adress from there
Percussive maintenance? ;-)
Hope you get it resolved.
You are a god. For mysterious reasons, having this IP in my hosts file breaks loading the page. Removing it from hosts restores access. I have no idea why Firefox would care about this because I'm not trying to access the page by name, but by IP address. My best guess is there's some sort of bug relating to handling of hosts file entries.
I found this answer, but I still don't understand what's going on and why this network.trr.exclude-etc-hosts might be useful.
Haha thanks :-)
I vaguely remembered an issue with a host file that firefox blocked instead of rerouted. Never did get to submit a bug report for it I think, hmm.
Glad I could help you resolve it.
The fact you're not seeing any exit packets, along with the ability to connect using anything other than Firefox means it must be an issue with Firefox itself.
Not to insult your intelligence, but do you have any extensions installed on Firefox such as an ad-blocker? Ones that are allowed to operate in private mode as well? I've had random issues with blacklists in my ad-blocker having bad entries in the past.
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.
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
Proxy settings in about:config?
The proxy is disabled. No proxy.
Firefox has an HTTPS-Only mode. Did you double check that? Make sure you can get anywhere on http tcp/80 in the browser.
Yes that is turned off. Also checked I can visit an unencrypted website, port 80. It also works over LAN using a python script.
Does wireshark on the Firefox box show outgoing packets to 192.168.0.2?
Nope! I just ran this test. No outgoing packets seen on the same machine with firefox trying to visit 192.168.0.2.
Start by also running Wireshark on the client device where Firefox is installed.
Might be some weird fringe case that's not handled correctly somewhere like an ipv4 checksum of ffff or something.
This isn't something too plausible, but this seems weird enough that farfetched things might be afoot.
Then again, NS_CONNECTION_REFUSED would mean receiving a reset or something, as opposed to being silently dropped.
Firefox does work for other LAN IPs, right?
Firefox is able to visit other LAN IPs fine, such as 192.168.0.1 and 192.168.0.203.
Running Wireshark on the same laptop, it doesn't see any outgoing packets for *.2.