Users unable to connect to site


#1

Hi,
Though I’ve never had trouble connecting to my site, I’ve had multiple people tell me they cannot. This is how its been for at least 6 months, maybe longer. One person said that if they used a proxy that they could connect, but not if they navigated straight to it. It seems to occur regardless of internet browser. Any ideas?

Here’s the error one of them got…

[quote]Failed to Connect
Firefox can’t establish a connection to the server at http://www.weezed.com.

Though the site seems valid, the browser was unable to establish a connection.

  • Could the site be temporarily unavailable? Try again later.
  • Are you unable to browse other sites? Check the computer’s network connection.
  • Is your computer or network protected by a firewall or proxy? Incorrect settings can interfere with Web browsing.[/quote]

#2

Works great for me in Los Angeles. The issue looks to be a timeout due to connectivity between them and the server. If they can do a Traceroute, that may shed some light on the issue. Where are these people? US, or outside?

-Scott


#3

The most recent complaint was a guy from California. I don’t know the others. How would someone do a traceroute?


#4

There is a pretty good guide to using traceroute, on different operating systems, in the DreamHost wiki:

http://wiki.dreamhost.com/Traceroute

Hopefully, you will find sufficient information there to pass to your users so that you can get a collection of traceroute reports from those who are having problems. :slight_smile:

–rlparker
–DreamHost Tech Support


#5

Not looking good… Here’s two…

First, someone from Columbus, OH
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\admin stf>tracert weezed.com

Tracing route to weezed.com [208.113.255.0]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Documents and Settings\admin stf>

Now someone from Reinbeck, IA
C:\Users\Waylon>tracert weezed.com

Tracing route to weezed.com [208.113.255.0]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\Waylon>

and here’s mine for comparison from St. Louis, MO
traceroute to weezed.com (208.113.255.0), 64 hops max, 40 byte packets
1 * 192.168.11.1 (192.168.11.1) 1.776 ms 1.520 ms
2 adsl-75-24-81-214.dsl.stlsmo.sbcglobal.net (75.24.81.214) 1.834 ms 1.407 ms 1.496 ms
3 bras5-l0.stlsmo.sbcglobal.net (151.164.182.114) 9.598 ms 9.563 ms 9.693 ms
4 dist1-vlan60.stlsmo.sbcglobal.net (151.164.14.162) 11.229 ms 11.265 ms 9.099 ms
5 151.164.93.178 (151.164.93.178) 7.913 ms 7.688 ms 7.507 ms
6 151.164.171.237 (151.164.171.237) 27.464 ms 30.027 ms 27.103 ms
7 as2914-ntt.eqchil.sbcglobal.net (151.164.251.114) 27.547 ms 140.266 ms 59.466 ms
8 xe-0-1-0.r21.chcgil09.us.bb.gin.ntt.net (129.250.3.13) 32.136 ms 28.273 ms 28.839 ms
9 p64-2-2-0.r21.dllstx09.us.bb.gin.ntt.net (129.250.2.22) 39.162 ms 48.559 ms 39.367 ms
10 ae-0.r20.dllstx09.us.bb.gin.ntt.net (129.250.2.58) 40.844 ms 39.314 ms 39.285 ms
11 as-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.3.130) 45.102 ms 46.173 ms 47.666 ms
12 ae-0.r21.hstntx01.us.bb.gin.ntt.net (129.250.3.25) 46.061 ms 46.948 ms 43.825 ms
13 as-1.r21.lsanca03.us.bb.gin.ntt.net (129.250.3.121) 81.212 ms 79.077 ms *
14 * * *
15 xe-1-3.r00.lsanca17.us.ce.gin.ntt.net (206.183.201.162) 89.335 ms 87.200 ms 87.111 ms
16 border20.po2-20g-bbnet2.lax.pnap.net (216.52.255.101) 89.729 ms 134.582 ms 88.058 ms
17 * newdream-8.border20.lax.pnap.net (216.52.220.146) 132.675 ms 89.687 ms
18 ip-66-33-201-67.dreamhost.com (66.33.201.67) 88.152 ms * 87.630 ms
19 apache2-igloo.popinski.dreamhost.com (208.113.255.0) 87.798 ms 100.579 ms 114.914 ms

Advice?


#6

That’s the strangest thing I’ve even seen! How does it have an IP address of 208.113.255.0? Who uses a 255 Class C, or a 0 for a server?

Those traceroutes look like they’re dying right at the user end, so I wonder if the non-standard IP address has something to do with it. I’d send a message to Support asking about the weird IP address if someone here doesn’t chime in to explain it.

-Scott


#7

Their routers (or ISPs) might be baulking at it due to a rule somewhere.

Would be good to get a comparison of their gear and providers.

Maximum Cash Discount on any plan with MAXCASH


#8

Well, I submitted a ticket, and the support guy said that the ip WAS actually valid, but some routers were probably rejecting it. He moved me to another apache service and now all is good. Kind of strange I’d end up with that IP in the first place, but at least its fixed now.