After being offline, sometimes Firefox can't connect until restarted
Sometimes, if the computer is offline and Firefox is open, when the computer goes back online Firefox can't connect to any website, with the page "Hmm. We’re having trouble finding that site.". The only fix is to close Firefox and open it again. Going offline doesn't always do this, and while I'm not sure of what exactly causes this to happen, a way to easily reproduce it is:
- Turn off the Wi-Fi;
- Reboot the computer;
- Open Firefox;
- Turn on the Wi-Fi;
After the computer is connected, refreshing the page sends you to "Hmm. We’re having trouble finding that site.". You have to restart Firefox.
A way that doesn't 100% reproduce it, but works enough times, is to reboot the computer without turning off the Wi-Fi, and open Firefox as soon as possible (before the computer manages to connect to the router, which is the part that isn't always consistent). Rarely, it happens after suspending the computer, or after a disconnection due to an unstable connection. I can reproduce it in Firefox's safe mode. I have a hunch that maybe this is related to networking drivers.
I'm using a Lenovo IdeaPad 5 14ARE05 (Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)), Linux NixOS 22.11 (I don't know about Windows).
Ask me for any log you might need.
This is kinda a duplicate of https://support.mozilla.org/en-US/questions/1078253, except that their solution does nothing to me.
All Replies (3)
Martino said
A way that doesn't 100% reproduce it, but works enough times, is to reboot the computer without turning off the Wi-Fi, and open Firefox as soon as possible (before the computer manages to connect to the router, which is the part that isn't always consistent).
I get this sometimes when trying to use the browser before the network is up and running and I'm plugged in. You mentioned a few times that you're opening the browser before WiFi is connected.
Muudetud jonzn4SUSE poolt
It appears i have similar problem: Debian 5.10.28 Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) FF dev. 101.0b4 (64-bit_
Suspecting this can be narrowed down to a wierd DNS issue. FF could not connect to internet, chrome could. Changed dns nameserver to only 8.8.8.8 and 127.0.0.1 and FF worked again Connected system to another local network (so system was connected to 2 networks same time) FF was still fine. Disconnected from 2nd (local) network and suddenly FF began agian having "We can’t connect to the server at.." problem
Maybe someone can try to replicate 1 then 2 networks and only 2 nameservers to narrow down what FF is trying to connect to vs chrome and other browsers not having the issue
confirmed Debian 5.10.28 FF 97.0b9 64-bit and 101.0b4 (64-bit)
It is a wierd dns issue with ff. Chrome works perfect.
To replicate: 1. delete dns nameservers 2. restart FF 3. attempt to visit a website w/ff (this should generate "can't connect to website at..." error 4. add name servers 5. restart FF (FF should still generate "can't connect....") 6. nslookup google.com 7. try FF website again and it should work
- ff is having trouble negotiating dns nameservers and needs nslookup to mark the path for FF. - ff is requesting dnsname server info differently than does chrome or other browsers (changing how ff requests dns nameserver info to something in line with other browser standards may eliminate this problem)
DNS PREFETHCING / Disable ivp6 does nothing to resolve this problem all the solutions here do not work either: https://www.youtube.com/watch?v=nGb0BQKdAtU
https://support.mozilla.org/en-US/questions/1275246
I have used FF for years , a core user. This error almost had me switch permanently to chromium. If FF connectivity is not a primary focus of dev team most of the other developments and adjunct offering (mozillavpn) will not get traction. FF is the sun mozilla products gain adoption because of.