The connection was reset. The connection to the server...
I get two page load/connection errors many times a day that I have never seen before I started the 4X.0 series. One is "The connection was rest" (picture attached) and the other error is "Secure Connection". Also the report check box does not stay checked and pressing the "report" button doesn't seem to work, so I rather doubt any of the error info is getting to where it need to go. This happens all the time now and is severely annoying to the point of switching browsers. I run several, but FF is (was) my main browser. It'll be easy to move. I don't want to.
The connection was reset
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer's network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
Reporting the address and certificate information for will help us identify and block malicious sites. Thanks for helping create a safer web!
Automatically report errors in the future Learn more…
All Replies (2)
http://www.ehow.com/how_11385212_troubleshoot-reset-connection-firefox.html
https://support.mozilla.org/en-US/kb/server-not-found-connection-problem
https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can
https://support.mozilla.org/en-US/kb/secure-connection-failed-error-message
https://support.mozilla.org/en-US/kb/connection-untrusted-error-message
http://kb.mozillazine.org/Error_loading_websites
This Connection is Untrusted is sometimes caused because the computer system clock is wrong. Check the time / date / time zone settings.
Thank you for your severely quick reply and the information. But I already read through all this prior to posting. This is a recent issue that did not happen prior to the 40.0 series and doesn't not happen with any other browser. And when I do get the error screens, pressing the "try Again" button always works. So as far as I can see it's a software hiccup.