Oops! Google Chrome could not find/connect

[escapeUK]

I only use Chrome and never get any of those issues, or any other issues come to that.

[adubya]

I use Chrome as my main browser and only get the above if there's a network connection issue.

The built in dev tools are ace IMO + easy to write extensions.

[xoggoth]

I was getting very similar with IE9 a few months ago. Pages not found but ok on refresh. I did change settings so it doesn't store any stuff in cache which seems to have fixed it.

[d000hg]

Such a shame when Chrome started so well. Has it got crap just in time to take the crown of most-used browser? Do we all migrate back towards IE10 now?

[fullyautomatix]

Chrome has so many issues i rarely use the bloody thing.

One annoying bug was that when you sometimes hit F5 it would not load the stylesheet for some reason and the entire page would load up horribly due to the lack of stylesheet. If you then look into the Chrome console it would show a generic error message for the stylesheet file, along the lines of "error while loading style.css" . This issue never happened with IE or Firefox.

[d000hg]

People online seem to suggest it is a Chrome-specific issue - DNS issues I've had in the past but they would affect everything.

I really like Chrome and I don't like FF/IE9 so it would be a shame. Also... where do you find all the really geeky settings in Chrome these days? Even the advanced settings seems pretty minimal in the newer versions and "under the hood" appears to be gone?

[cojak]

Maybe something to do with DNS?

Or more likely something to do with Chrome. I used it for a while in its early days, but as time has gone by I've relegated it to use only for testing and debugging. Google seems to have just added features without any adequate testing, and its ended up an unreliable resource hog. It was when they introduced serious regressions that broke existing features, then downgraded the bug reports to a low priority for months (or even closed obvious bugs as WONTFIX), that I decided to go back to Safari, which may not be updated very often but does actually work. Usually.

WNFS.

I became unhappy with Chrome and went back to FF since they fixed their crappiness a couple of upgrades ago.

[NickFitz]

Maybe something to do with DNS?

Or more likely something to do with Chrome. I used it for a while in its early days, but as time has gone by I've relegated it to use only for testing and debugging. Google seems to have just added features without any adequate testing, and its ended up an unreliable resource hog. It was when they introduced serious regressions that broke existing features, then downgraded the bug reports to a low priority for months (or even closed obvious bugs as WONTFIX), that I decided to go back to Safari, which may not be updated very often but does actually work. Usually.

[SimonMac]

I get this several times a day and refreshing nearly always works fine... except when it's a form submission and things get annoying.

I find people complaining about it online but not obvious solution other than "maybe something to do with DNS".

Does anyone here have any suggestions?

I get this too, I have now just learnt to live with it

[d000hg]

I get this several times a day and refreshing nearly always works fine... except when it's a form submission and things get annoying.

I find people complaining about it online but not obvious solution other than "maybe something to do with DNS".

Does anyone here have any suggestions?