But before doing so, you should always scan your PC for Malware. So, in this method, we will try to scan and fix the Registry to see if the error persists. In my case, the Apache instance is shared between a number of applications/developers and I guess an upgrade or reconfiguration of the sever which I was not aware of has introduced these issues. As I mentioned earlier, the ERRCONNECTIONRESET Chrome error could be a result of some unwanted changes in your PC’s registry. Turning-off compression in the confluence web application solved the problem for me, as described here. I came across these instructions on testing for (and disabling) mod_deflate. This caused that the content was compressed twice which cannot be handled by the client.Īpache2 was using mod_deflate to compress content sent from the server to to the client. issuing the request directly on the machine where tomcat/confluence was running using a SOCKS proxy over ssh).įinally, I found out that the problem was caused by double compression performed by confluence and apache2. I also discovered that I can view all pages when I bypass the proxy (eg. The subtle problem was that some of the pages (like the login screen) could be viewed, while I lost the connection when viewing other pages. When I tried to view the confluence wiki pages, I received following error messages:

I had similar problems when running a confluence instance (within a tomcat server) behind apache2 using either mod_jk or mod_proxy.

The connection was reset. chrome