Getting connection reset errors in Chrome

Join the discussion
Ask a follow-up here, or get your own question answered by working scientists, mathematicians and engineers — people, not an autocomplete.
Real named experts · corrections over time · the nuance an AI answer skips
8 replies · 23K views
Jonathan Scott
Gold Member
Messages
2,358
Reaction score
1,261
Getting "connection reset" errors

Today I've had several errors when following links around the forums, but refreshing the page works immediately. The error occurs immediately (not like a timeout) and the "errors details" say that the connection was reset by the server.

Here's what Google Chrome gives as error details:

Error 101 (net::ERR_CONNECTION_RESET): Unknown error.

This could be a bug in Chrome, as I've not seen it when using Firefox, but since I use Chrome much more than Firefox that could also just be chance. Anyone else see the same problem, and if so with what browser?
 
Last edited:
Physics news on Phys.org


Greg Bernhardt said:
How does the error present itself?

In Google Chrome, instead of the web page, I get the following:


This webpage is not available.

The webpage at https://www.physicsforums.com/ might be temporarily down or it may
have moved permanently to a new web address.

More information on this error


If I click on the "More information" link I get the following:


Error 101 (net::ERR_CONNECTION_RESET): Unknown error.


If I click on the refresh button, I usually immediately get the right page, although I think it has sometimes taken a further attempt before it works.
 


Greg Bernhardt said:
I did a quick google search for "Error 101 (net::ERR_CONNECTION_RESET) chrome" and got lots of results. Doesn't look like a PF problem.

That might be partly because it's called other things in other browsers, which tend to describe things in text where Chrome just gives the internal stuff.

However, I now see that when I guessed the format of the message (based on a previous similar message which I had copied), I missed an important point which does tend to point to a Chrome bug this time. It actually says "null" instead of a web server address:


This web page is not available.

The web page at null might be temporarily down or it may have moved permanently to a new web address.

More information on this error


I'm now getting this problem very frequently, getting worse by the minute!
 


I still can't find any problem when using Firefox, so I think that there might well be a Google Chrome problem (it certainly wouldn't be the first). I humbly apologise for even hinting that it might have been the PF server!
 


Jonathan Scott said:
I still can't find any problem when using Firefox, so I think that there might well be a Google Chrome problem (it certainly wouldn't be the first). I humbly apologise for even hinting that it might have been the PF server!

No problem, perhaps try and download/install chrome again, you could get a newer build.
 


Greg Bernhardt said:
No problem, perhaps try and download/install chrome again, you could get a newer build.

I'm automatically picking up the "dev" stream; my build already changed twice in the last 24 hours! I've now raised a Chrome issue for it, but it is intermittent and might be tricky to track down.