Firefox Cannot Consistently Access a Web Site
My desktop Firefox (version 155.0.1) has recently became unable to consistently access the Web site at this Web site this Web site. Chrome successfully accesses the site 100% of the time. Firefox's connection failures are intermittent, unpredictable, and usually go away on their own after varying time intervals (sometimes can't connect for up to 24 hours). I see status messages saying Firefox is trying to connect to the site, but it eventually gives up and times out.
I cleared the Firefox cache, but that had no effect. I don't recall making any significant changes to the Firefox settings lately. Any suggestions on what to look at/try would be greatly appreciated.
(Yes, I know the site doesn't use https: Its protocol is outside my control).
All Replies (6)
My desktop Firefox (version 155.0.1) has recently became unable to consistently access the Web site at this Web site this Web site. Chrome successfully accesses the site 100% of the time. Firefox's connection failures are intermittent, unpredictable, and usually go away on their own after varying time intervals (sometimes can't connect for up to 24 hours). I see status messages saying Firefox is trying to connect to the site, but it eventually gives up and times out. I cleared the Firefox cache, but that had no effect. I don't recall making any significant changes to the Firefox settings lately. Any suggestions on what to look at/try would be greatly appreciated. (Yes, I know the site doesn't use https: Its protocol is outside my control).
Note: This forum isn't showing the site link correctly. The site URL is http://www.hymntime.com/tch.
Nah, the site is fine, and http is also fine (less things can break down).
It seems hosted at some Google cloud so hard to tell how DNS and content delivery is handled. When you have trouble connecting, check about:networking where it's actually trying to connect, and how the DNS resolution looks like. Not sure if your Google–hosted infrastructure is supposed to do some security checks or bot protections on loads?
After I got Firefox can’t connect to the server at www.hymntime.com, I entered about:networking as suggested. Firefox then displays a very large table of host names, ports, etc.
To (possibly) complicate matters, I have to access the Internet through Wifi at my apartment complex, which uses Cox. Probably not relevant, though, since Chrome connects to the site with no problems. By process of elimination, the problem seems to be in my Firefox. I’ve been using Firefox to access that site for literally decades, and this is the first time it’s had a problem like this. As I said, I can verify (through Chrome) that the site is up and running normally. Are you connecting to it with Firefox?
What should I be looking for in the about:networking output? Would it help to send that table to the site manager?
Ah, sorry I misread the post thinking that's your site — i.e. you'd have known how to make use of the networking data there (to compare to the expected results, if you were the site operator).
Besides some hanging connection to no longer existing "Bibles & Literature in French (BLF USA)" resources, I indeed do see it plenty fine in Firefox:
Thanks for the quick turnaround. The fact that you can see the site in FF and I (sometimes) can't—assuming we’re both using the latest FF version— means something must wrong with my FF installation (or perhaps I've stumbled across some edge case FF bug).
The problem does not seem be my infrastructure or Internet connection, since Chrome connects flawlessly , 100% of the time. And I also don't understand what caused the problem suddenly surface without warning.
Maybe the Web server sometimes thinks our IP address is a bad actor? I just tried turning on/off my VPN to see if that made any difference, and it didn't. Very mysterious. Does FF maintain any logs that I could forward to Mozilla for the developers to examine?
Since the site seems to provided from within Google network, they most likely won't be blocking their own browser — but may apply different rules for other clients.
I'd still guess it's the connection/routing being a factor here, look for Firefox DNS over HTTPS options and change the provider or flip that feature on/off, which might give you different resolving and potential regional connection difference — maybe some of the settings will work better for this host.
(Before the kind of a failure point is known, it's rather hard to advise any logging steps — as it's not apparent which component would see any relevant operations.)
Modified