The connection was reset, error message

chiefs11 said 1 year, 2 months ago:

Having this same issue on our domain as well: http://www.evcreations.com

“The connection was reset” first time you try to load the page.. works fine after that. Very unprofessional looking when potential customers go to our website for the first time! This has been going on since last week… please fix it!

We won’t be upgrading to a dedicated host to solve this, we’ll be going elsewhere!

chiefs11 said 1 year, 2 months ago:

Some traceroutes:

From Comcast cable:
traceroute to http://www.evcreations.com (184.168.188.1), 30 hops max, 40 byte packets
1 fire.4wick.dr (192.168.100.1) 0.341 ms 0.352 ms 0.363 ms
2 24.0.192.1 (24.0.192.1) 13.800 ms 13.906 ms 29.255 ms
3 te-4-2-ur01.swedesboro.nj.panjde.comcast.net (68.85.116.197) 13.971 ms 14.048 ms 14.120 ms
4 te-9-3-ur02.woodbury.nj.panjde.comcast.net (68.85.35.133) 14.244 ms 14.924 ms 15.520 ms
5 te-9-3-ur01.woodbury.nj.panjde.comcast.net (68.85.35.129) 16.215 ms 16.344 ms 16.802 ms
6 te-0-4-0-0-ar01.audubon.nj.panjde.comcast.net (68.86.210.97) 16.936 ms 17.899 ms 18.258 ms
7 xe-6-0-0-0-ar03.audubon.nj.panjde.comcast.net (68.85.62.178) 17.639 ms 10.042 ms 10.124 ms
8 pos-3-9-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.95.157) 14.470 ms 14.607 ms 15.160 ms
9 pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net (68.86.86.26) 15.890 ms 15.312 ms 14.818 ms
10 ash1-pr1-ae5-301.us.twtelecom.net (66.192.252.209) 17.364 ms 17.345 ms 16.960 ms
11 phx1-ar3-xe-2-1-0-0.us.twtelecom.net (66.192.242.38) 73.128 ms 75.960 ms 75.984 ms
12 * * *
13 ip-208-109-113-245.ip.secureserver.net (208.109.113.245) 97.087 ms 96.782 ms 94.145 ms
14 ip-208-109-113-245.ip.secureserver.net (208.109.113.245) 94.061 ms 94.194 ms 96.881 ms
15 ip-184-168-0-102.ip.secureserver.net (184.168.0.102) 96.718 ms 95.607 ms 95.647 ms
16 ip-184-168-0-102.ip.secureserver.net (184.168.0.102) 96.834 ms !X * *

From Verizon FIOS:
traceroute to http://www.evcreations.com (184.168.188.1), 30 hops max, 40 byte packets
1 firewalla.phonetics.com (10.1.2.81) 0.093 ms 0.090 ms 0.090 ms
2 L300.PHLAPA-VFTTP-78.verizon-gni.net (72.78.240.1) 4.577 ms 4.847 ms 4.842 ms
3 G2-0-6-778.PHLAPA-LCR-07.verizon-gni.net (130.81.109.128) 4.834 ms 4.826 ms 4.829 ms
4 * * *
5 so-8-0-0-0.LCC2-RES-BB-RTR1-RE1.verizon-gni.net (130.81.19.118) 19.148 ms 16.331 ms 19.131 ms
6 0.ae1.BR1.IAD8.ALTER.NET (152.63.32.141) 16.295 ms 16.290 ms 16.289 ms
7 dcp-brdr-03.inet.qwest.net (63.146.26.105) 56.472 ms 51.696 ms 50.563 ms
8 phn-core-01.inet.qwest.net (67.14.19.30) 88.665 ms phn-core-02.inet.qwest.net (67.14.19.42) 88.652 ms 91.329 ms
9 phn-edge-06.inet.qwest.net (205.171.12.146) 96.249 ms 97.480 ms phn-edge-06.inet.qwest.net (205.171.12.142) 94.893 ms
10 63-234-235-102.dia.static.qwest.net (63.234.235.102) 92.376 ms 92.351 ms 91.896 ms
11 * * *
12 ip-208-109-113-245.ip.secureserver.net (208.109.113.245) 97.429 ms 97.582 ms 97.554 ms
13 ip-208-109-113-245.ip.secureserver.net (208.109.113.245) 99.027 ms 99.966 ms 97.498 ms
14 ip-184-168-0-102.ip.secureserver.net (184.168.0.102) 97.474 ms 97.026 ms 97.025 ms
15 ip-184-168-0-102.ip.secureserver.net (184.168.0.102) 97.084 ms !X * *

Baillee said 1 year, 2 months ago:

Thank you everyone for taking the time to post here on the Forums, and for providing me plenty of information to have this issue reviewed by my advanced teams.

The issue you are experiencing may be related to filters we have currently applied to protect your site. We noted a large volume of external traffic that occurred on the server and placed these filters to ensure only legitimate requests were being processed. Our servers and environments are fully operational at this time.

Furthermore, we have reviewed the servers in question, and some of the filters have been removed. However, there are also a couple servers in which we are still investigating a large volume of traffic to, and will be adjusting the filters once this traffic is confirmed to be legitimate.

Again, we sincerely appreciate your patience and understanding in this matter.

- Baillee

PTom said 1 year, 2 months ago:

@Baillee: “Furthermore, we have reviewed the servers in question, and some of the filters have been removed.”

Does it mean the filters are removed from certain hosting accounts individually? If I have a site which legitimately has, say, 10000 visitors a day, then I need to open a support ticket in order to have the traffic filters removed from my site?

Or you have a general solution, so there is no need to contact support for each affected site separately?

canen_concepts said 1 year, 2 months ago:

This issue is still happening to my server as well.

http://www.canenconcepts.com

This issue has been present for the last 3 days.

inrng said 1 year, 2 months ago:

Still happening for me too at inrng.com

hientruong said 1 year, 2 months ago:

Same issue at my website http://ttgdnguyenhien.com. It happens 3 days ago. Please, give some advise.

jguardon said 1 year, 2 months ago:

Hi all. Now, on my side it seems this issue has gone (for now) but access times to the pages are quite slow. 14 to 30 seconds at worst is not acceptable. ¿Could you take a look at this? Thanks in advance.

chiefs11 said 1 year, 2 months ago:

Just wanted to follow up…
It appears that our website is working OK now and the issues seem to have been resolved.

Baillee said 1 year, 2 months ago:

At this time, it appears this issue should be resolved for the customers on this thread. If you’re still having an issue, please provide your domain name and a current traceroute.

Thanks!

- Baillee

creativelite said 1 year, 1 month ago:

I have the same problem for my domain http://www.creativelite.com

Baillee said 1 year, 1 month ago:

@creativelite

I would be happy to look into this for you. Please provide a current trace route to your site so that we may review.

Thanks!

Baillee

epicurean said 1 year ago:

Baillee, I’m suddenly having this problem with multiple sites. The one I need resolved asap is carolinaepicurean.com I’m not sure what you mean by a trace route? Thanks, Laura

JasonP said 1 year ago:

@epicurean

I was unable to replicate the issue at this time. You can review the results of a third party tracking tool.

http://host-tracker.com/check_res_ajx/10252798-0/

As for the trace route, this article will walk you through the process:

Performing a Traceroute in Microsoft Windows

Jason

recaihazer said 11 months, 1 week ago:

Same problem with my domain windowstelefon.com

chrome >> Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.
firefox >> No problem
After firefox browsing >> No problem
After a hour on chrome >> Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.

Could you help me?