www.smalltalkhub.com not reachable from digitalocean host in NewYork2

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

www.smalltalkhub.com not reachable from digitalocean host in NewYork2

Yanni Chiu
I can ping:

     www.smalltalkhub.com (88.190.31.116)

from two other machines (home and another host provider), but I cannot
see 88.190.31.116 from a digitalocean box located in NewYork2. I can see
squeaksource.com, ss3.gemtalksystems.com, ci.infria.fr but not
smalltalkhub.com. Very frustrating, since I want to run my build from
this machine.

Any ideas? Is it on some sort of ban list? The firewall rules allow all
outgoing connections.

Reply | Threaded
Open this post in threaded view
|

Re: www.smalltalkhub.com not reachable from digitalocean host in NewYork2

Camillo Bruni-3
it is up (again?) here from buenos aires...

On 2013-09-24, at 01:01, Yanni Chiu <[hidden email]> wrote:

> I can ping:
>
>    www.smalltalkhub.com (88.190.31.116)
>
> from two other machines (home and another host provider), but I cannot see 88.190.31.116 from a digitalocean box located in NewYork2. I can see squeaksource.com, ss3.gemtalksystems.com, ci.infria.fr but not smalltalkhub.com. Very frustrating, since I want to run my build from this machine.
>
> Any ideas? Is it on some sort of ban list? The firewall rules allow all outgoing connections.
>


signature.asc (457 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: www.smalltalkhub.com not reachable from digitalocean host in NewYork2

Ben Coman
In reply to this post by Yanni Chiu
Yanni Chiu wrote:
I can ping:

    www.smalltalkhub.com (88.190.31.116)

from two other machines (home and another host provider), but I cannot see 88.190.31.116 from a digitalocean box located in NewYork2. I can see squeaksource.com, ss3.gemtalksystems.com, ci.infria.fr but not smalltalkhub.com. Very frustrating, since I want to run my build from this machine.

Any ideas? Is it on some sort of ban list? The firewall rules allow all outgoing connections.


Can you try traceroute from those hosts. This is what I get from my home in Western Australia.

C:\Users\Ben>tracert www.smalltalkhub.com

Tracing route to www.smalltalkhub.com [88.190.31.116] over a maximum of 30 hops:
  1    11 ms     3 ms     4 ms  home.gateway.home.gateway [192.168.1.254]
  2    30 ms    26 ms    32 ms  nexthop.wa.iinet.net.au [203.215.5.244]
  3    52 ms    32 ms    24 ms  ae8.cr2.per2.on.ii.net [150.101.33.126]
  4    33 ms    33 ms    27 ms  ae0.cr1.per1.on.ii.net [150.101.33.12]
  5   337 ms   312 ms   318 ms  te0-3-0.cor1.per1.on.ii.net [150.101.33.99]
  6     *        *        *     Request timed out.
  7   316 ms   316 ms   315 ms  gi0-0-5.bdr1.lon1.on.ii.net [203.16.211.101]
  8   348 ms   349 ms   343 ms  amsix-6k-1.routers.proxad.net [195.69.144.251]
  9   352 ms   360 ms   353 ms  londres-6k-1-po100.intf.routers.proxad.net [212.27.56.41]
 10   365 ms   362 ms   364 ms  bzn-crs16-1-be1102.intf.routers.proxad.net [212.27.51.185]
 11   344 ms   341 ms   339 ms  dedibox-2-t.intf.routers.proxad.net [212.27.58.50]
 12   340 ms   339 ms   339 ms  a9k1-1012.dc3.poneytelecom.eu [88.191.1.131]
 13   350 ms   350 ms   356 ms  45-s103-1-1062.dc2.poneytelecom.eu [88.191.1.114]
 14   341 ms   336 ms   343 ms  sd-32491.dedibox.fr [88.190.31.116]
Trace complete.

Perhaps also try traceroute from some online services to your digitalocean box.
http://traceroute.monitis.com/

btw, the mobile app from there looks interesting (but I've only just discovered it, I haven't used it)
http://www.monitis.com/downloads/mobile-apps

cheers -ben
Reply | Threaded
Open this post in threaded view
|

Re: www.smalltalkhub.com not reachable from digitalocean host in NewYork2

Yanni Chiu
On 24/09/13 12:45 AM, [hidden email] wrote:
 >
 > Can you try traceroute from those hosts.

traceroute to www.smalltalkhub.com (88.190.31.116), 30 hops max, 60 byte
packets
  1  ...  3.148 ms  3.198 ms  3.287 ms
  2  nyk-b6-link.telia.net (62.115.35.101)  30.006 ms  30.012 ms  30.005 ms
  3  nyk-b5-link.telia.net (213.155.131.116)  0.362 ms
nyk-b5-link.telia.net (213.155.131.254)  0.413 ms  0.422 ms
  4  cogent-ic-151338-nyk-b5.c.telia.net (213.248.85.106)  0.954 ms
cogent-ic-151337-nyk-b5.c.telia.net (213.248.73.198)  0.711 ms
cogent-ic-151338-nyk-b5.c.telia.net (213.248.85.106)  1.006 ms
  5  be2063.mpd22.jfk02.atlas.cogentco.com (154.54.47.57)  0.955 ms
be2062.mpd21.jfk02.atlas.cogentco.com (154.54.7.13)  1.290 ms
be2063.mpd22.jfk02.atlas.cogentco.com (154.54.47.57)  1.068 ms
  6  te0-0-0-9.mpd22.par01.atlas.cogentco.com (154.54.46.106)  72.081 ms
te0-0-0-9.ccr22.par01.atlas.cogentco.com (154.54.46.102)  72.745 ms
te0-7-0-11.mpd21.par01.atlas.cogentco.com (154.54.46.110)  72.160 ms
  7  be2039.mag21.par01.atlas.cogentco.com (154.54.75.2)  74.243 ms
be2041.mag21.par01.atlas.cogentco.com (154.54.78.42)  73.472 ms
be2039.mag21.par01.atlas.cogentco.com (154.54.75.2)  76.817 ms
  8  snsci.demarc.cogentco.com (149.6.160.50)  73.537 ms 149.6.160.102
(149.6.160.102)  73.453 ms 149.6.115.26 (149.6.115.26)  73.872 ms
  9  bzn-crs16-1-be1106.intf.routers.proxad.net (212.27.59.101)  81.011
ms  78.111 ms  87.806 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Reply | Threaded
Open this post in threaded view
|

Re: www.smalltalkhub.com not reachable from digitalocean host in NewYork2

Yanni Chiu
On 24/09/13 1:45 AM, Yanni Chiu wrote:
>
> traceroute to www.smalltalkhub.com (88.190.31.116), 30 hops max, 60 byte
> packets
>   1  ...
>   9  bzn-crs16-1-be1106.intf.routers.proxad.net (212.27.59.101)  81.011
> ms  78.111 ms  87.806 ms

It's working now, but the problem seems to have been in "proxad.net".

In the traceroutes that were successful, the route bounced around for 4
or 5 hops within proxad.net, before coming out at:
   4k-s103-1037.dc2.poneytelecom.eu (88.191.1.170)
which then led to smalltalkhub.com

It's never a good time to be unreachable, but I'd just moved to a new
host machine, and deleted the old one, then found the repository
unreachable from the new machine.