Valued Contributor
•
1.7K Messages
Can't access personal web site
A few years ago, when Cox eliminated personal website hosting, I moved my small site to a free hosting service atspace. I have been able to access it until about a week ago when I started getting timeouts. I can ping the site so I am getting dns resolution. If I run through an external proxy server it works fine but as soon as I try to access it directly via Cox HSI I get the timeouts. Also, I can access it via Verizon 4G but when I connect my cell phone to Cox via wifi I get the same timeouts. So this happens on both my PC wired Ethernet into Cox and my smartphone. The only common denominator is Cox HSI. Could Cox be blocking http into atspace domains? Is there a reason for blocking like a malware problem with this hosting service?
Health_Edge
Valued Contributor III
•
4.2K Messages
11 years ago
What exactly is the error? And would you feel comfortable sharing the domain to see if I can replicate the issue?
0
0
AllenP
Valued Contributor
•
1.7K Messages
11 years ago
No problem sharing, I would appreciate it if you try to duplicate the problem.
It's a family genealogy site my son created at: http://apaulct.atspace.cc/paul_family/
When I try to access it using the latest version of Firefox (v 34.0.5) on a Win 8.1 PC connected via wired Ethernet I get:
The connection has timed out
The server at apaulct.atspace.cc is taking too long to respond.
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.
If I go to a public proxy server and enter the same url the site loads without issue.
Thanks
0
0
ChrisL
Former Moderator
•
7.1K Messages
11 years ago
I just tried that link from both home and our residential test account here in the office and am not experiencing any problems accessing the site. I'm thinking there may be a problem on the remote end perhaps having a geographical impact but I'd suggest for the sake of being thorough restarting your modem and router or possibly bypassing the router to see if there is any difference.
0
0
AllenP
Valued Contributor
•
1.7K Messages
11 years ago
Chris, I ...
- Powered down the modem, router, and PC.
- Disconnected the Ethernet from the router to modem and connected the PC directly to the modem.
- Powered up the modem & waited for it to fully boot.
- Powered on the PC.
Tested from the PC with same result. The website timed out.
I am now back to my original config ... modem ->router->PC and have same result.
I am pretty sure the PC isn't the issue since the same thing happens with my smartphone. I can access the site via Verizon's 4G network but when I connect via wifi to Cox I get the same timeout. We just eliminated the router as the same thing happens when bypassing it.
Any more ideas? Thanks.
0
0
ChrisL
Former Moderator
•
7.1K Messages
11 years ago
If you're able to ping the site OK I don't think this is going to be a network or Internet issue. I'm sticking with my original theory that this is probably an application issue on the other end in the absence of any further data.
0
0
Health_Edge
Valued Contributor III
•
4.2K Messages
11 years ago
What are you pinging to test the domain? And can you post a tracert to the domain from Cox and Verizon? I can also view the website without any problem and I am in RI.
0
0
AllenP
Valued Contributor
•
1.7K Messages
11 years ago
I am pinging apaulct.atspace.cc here is the tracert from Cox. I have to install a traceroute app on my cell phone than post the screen captures. Funny thing, I was out this afternoon and able to access the site from a Cox hotspot in the center of town. Strange
Tracing route to apaulct.atspace.cc [83.125.22.186]
over a maximum of 30 hops:
1 * * * Request timed out.
2 8 ms 7 ms 7 ms ip98-190-163-122.ri.ri.cox.net [98.190.163.122]
3 9 ms 9 ms 9 ms ip98-190-33-72.ri.ri.cox.net [98.190.33.72]
4 13 ms 12 ms 12 ms ip98-190-33-34.ri.ri.cox.net [98.190.33.34]
5 17 ms 18 ms 16 ms 68.1.5.157
6 18 ms 18 ms 16 ms xe-11-2-1.edge1.NewYork1.Level3.net [4.78.132.29
]
7 17 ms 18 ms 17 ms ae-1-60.ear2.NewYork1.Level3.net [4.69.155.22]
8 18 ms 21 ms 18 ms telia-level3-10.NewYork1.Level3.net [4.68.110.82
]
9 33 ms 16 ms 17 ms nyk-bb2-link.telia.net [213.155.130.244]
10 87 ms 88 ms 87 ms ldn-bb2-link.telia.net [213.155.133.6]
11 86 ms 85 ms 87 ms ldn-b7-link.telia.net [80.91.248.93]
12 87 ms 87 ms 86 ms eunetworks-ic-138752-ldn-b5.c.telia.net [213.248
.103.22]
13 92 ms 147 ms 92 ms ae1-irt1.ams01.nl.as13237.net [82.197.136.22]
14 101 ms 102 ms 100 ms ae1-irt1.dus03.de.as13237.net [82.197.128.21]
15 109 ms 108 ms 108 ms xe11-0-0.irt1.ham21.de.as13237.net [217.71.96.21
3]
16 108 ms 108 ms 106 ms 217.71.100.142
17 108 ms 112 ms 108 ms f6-www.runhosting.com [83.125.22.186]
Trace complete.
0
0
Health_Edge
Valued Contributor III
•
4.2K Messages
11 years ago
Looks like routing is good. Hitting a similar Level3 server, see my tracert below. No need for iphone screenshots if issue has been isolated to HSI. Try a telnet to the site
Tracing route to apaulct.atspace.cc [83.125.22.186]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 9 ms 9 ms 9 ms 10.2.48.1
3 10 ms 10 ms 8 ms ip98-190-160-114.ri.ri.cox.net [98.190.160.114]
4 21 ms 11 ms 11 ms ip98-190-33-123.ri.ri.cox.net [98.190.33.123]
5 15 ms 16 ms 18 ms 68.1.5.157
6 16 ms 16 ms 15 ms xe-8-1-0.edge1.NewYork1.Level3.net [4.78.132.5]
7 17 ms 18 ms 16 ms ae-4-90.ear2.NewYork1.Level3.net [4.69.155.200]
8 16 ms 17 ms 17 ms telia-level3-10.NewYork1.Level3.net [4.68.110.82]
9 34 ms 28 ms 35 ms nyk-bb2-link.telia.net [80.91.254.15]
10 85 ms 85 ms 85 ms ldn-bb2-link.telia.net [213.248.65.93]
11 85 ms 85 ms 94 ms ldn-b7-link.telia.net [62.115.141.151]
12 86 ms 85 ms 100 ms eunetworks-ic-138752-ldn-b5.c.telia.net [213.248.103.22]
13 91 ms 93 ms 93 ms ae1-irt1.ams01.nl.as13237.net [82.197.136.22]
14 108 ms 103 ms 103 ms ae1-irt1.dus03.de.as13237.net [82.197.128.21]
15 107 ms 117 ms 127 ms xe11-0-0.irt1.ham21.de.as13237.net [217.71.96.21.3]
16 111 ms 111 ms 119 ms 217.71.100.142
17 105 ms 105 ms 105 ms f6-www.runhosting.com [83.125.22.186]
Trace complete.
0
0