Can't reach site because of too long responding time
Permalink
Hi,
Since this morning I can't reach my Concrete5 site (http://dylancremers.nl/) because it takes too long to respond. I already got in contact with my hosting, but they have no problems of reaching the site (because of their fast interenet connection over there) and say the problem is caused by Concrete5. Could somebody please help me? I really need this site because of my work and I can't even reach the Concrete5 dashboard or anything.
Since this morning I can't reach my Concrete5 site (http://dylancremers.nl/) because it takes too long to respond. I already got in contact with my hosting, but they have no problems of reaching the site (because of their fast interenet connection over there) and say the problem is caused by Concrete5. Could somebody please help me? I really need this site because of my work and I can't even reach the Concrete5 dashboard or anything.
I have done what you asked and this is what I got back. (See attachment)
I'm no expert, far from it but if you can't reach the site (not even get a ping back from it or get Tracert to the webserver) in my eyes that must be a issue with the hosting. I personally can't see this being an issue with C5 because you can't even reach the webserver to begin with.
Thanks. I think I will contact my hosting again tomorrow. I was already wondering if they were wrong and that is was a hosting error. It didn't make any sense otherwise.
Hi gavtompson,
I got in contact with my hosting provider again. And they checked my site again and they have no problem with visiting the site. They also checked the servers and they found no issues. Any guesses of what the problem could be? I really need your help man.
I got in contact with my hosting provider again. And they checked my site again and they have no problem with visiting the site. They also checked the servers and they found no issues. Any guesses of what the problem could be? I really need your help man.
If your server was working correctly you'd expect a static resource like the robots.txt file to return almost instantly:
http://dylancremers.nl/robots.txt...
But that's not loading either.
I think your host have diagnosed things incorrectly, I'd say it's some sort of networking issue on their end.
I often usehttp://tools.pingdom.com/ to check that it's not just me if I have trouble accessing a site (sometimes firewalls can automatically block you, etc)
Perhaps ask the host to explain why a static file on your site isn't coming up in pingdom tools.
http://dylancremers.nl/robots.txt...
But that's not loading either.
I think your host have diagnosed things incorrectly, I'd say it's some sort of networking issue on their end.
I often usehttp://tools.pingdom.com/ to check that it's not just me if I have trouble accessing a site (sometimes firewalls can automatically block you, etc)
Perhaps ask the host to explain why a static file on your site isn't coming up in pingdom tools.
Take Mesuva's advice :).
Also, can you even access your CPanel? that has nothing to do with C5.
Who is your host out of interest?
Also, can you even access your CPanel? that has nothing to do with C5.
Who is your host out of interest?
Hi Dylan,
Your website loaded just fine here from Ashland, Oregon (of course not the fastest route) at 3:30pm PST:
FYI, John
Your website loaded just fine here from Ashland, Oregon (of course not the fastest route) at 3:30pm PST:
Tracing route to dylancremers.nl [46.30.213.127] over a maximum of 30 hops: 1 3 ms 2 ms 2 ms xxxxxxxxxxxx [192.168.0.1] 2 30 ms 29 ms 27 ms eugn-dsl-gw25.eugn.qwest.net [67.42.192.25] 3 27 ms 27 ms 26 ms eugn-agw1.inet.qwest.net [67.42.193.193] 4 33 ms 33 ms 32 ms sea-brdr-02.inet.qwest.net [67.14.41.194] 5 47 ms 49 ms 45 ms sea-b1-link.telia.net [80.239.194.29] 6 48 ms 47 ms 47 ms sjo-b21-link.telia.net [62.115.118.171] 7 115 ms 115 ms 113 ms ash-bb4-link.telia.net [62.115.138.52] 8 112 ms 113 ms 113 ms ash-b1-link.telia.net [213.155.130.73] 9 115 ms 115 ms 116 ms one-ic-324593-ash-b1.c.telia.net [62.115.154.197] 10 308 ms 306 ms 307 ms ae1-0.cr1-wdc2.mpls.one.com [104.37.32.44] 11 324 ms 305 ms 216 ms xe-0-0-3-0.cr1-lon1.mpls.one.com [104.37.32.51] 12 315 ms 223 ms 291 ms xe-5-0-5-0.cr1-ams1.mpls.one.com [46.30.208.60] 13 306 ms 309 ms 307 ms xe-4-3-0-200.cr1-cph3.net.one.com [46.30.210.16] 14 322 ms 308 ms 305 ms xe-0-0-29-200.dr3-cph3.net.one.com [46.30.210.17]
Viewing 15 lines of 18 lines. View entire code block.
FYI, John
It's loading for me now too (and through pingdom), it wasn't 12 hours ago.
I suspect they've fixed something, perhaps a routing issue.
I suspect they've fixed something, perhaps a routing issue.
Hi guys,
The problem has been fixed now. I'm still quite not sure what caused it, because my hosting provider says that they couldn't find a sollution, but it got fixed anyway so I'm happy. Thanks for the support everybody!
The problem has been fixed now. I'm still quite not sure what caused it, because my hosting provider says that they couldn't find a sollution, but it got fixed anyway so I'm happy. Thanks for the support everybody!
The twitter plugin was causing my site to timeout for some reason, but now it is not. Perhaps 3rd party code such as twitter or facebook was timing out.
Do a
tracert dylancremers.nl