http/ssl to dropbox.com dying

[Greg Ihnen]

From other geographic locations I can connect to the dropbox service and get to 
their https web page, but from my home connection I can't, unless I vpn around 
the issue.

downforeveryoneorjustme says it's just me, but they're located someplace else 
geographically, and I don't know if they check the https site. 
http://www.dropbox.com immediately redirects to https://www.dropbox.com

It seems like a transport issue.

Is there any tools for checking where an https connection is failing, like a 
traceroute for https?

I'm not sure if the traceroute results are indicative but here it is

Macintosh-2:~ gregihnen$ traceroute dropbox.com
traceroute: Warning: dropbox.com has multiple addresses; using 199.47.216.179
traceroute to dropbox.com (199.47.216.179), 64 hops max, 52 byte packets
 1  router (192.168.7.1)  1786.458 ms  1.670 ms  2.072 ms
 2  modem (100.42.12.241)  1644.717 ms  2031.032 ms  2113.805 ms
 3  75.7.64.12 (75.7.64.12)  2594.284 ms  1650.347 ms  822.159 ms
 4  75.7.64.2 (75.7.64.2)  1528.550 ms  2168.641 ms  1922.285 ms
 5  12.91.131.205 (12.91.131.205)  2323.903 ms  3137.965 ms  2138.427 ms
 6  cr83.cgcil.ip.att.net (12.122.133.202)  1629.569 ms  1946.842 ms  1621.351 
ms
 7  cr1.cgcil.ip.att.net (12.123.7.110)  2256.595 ms  1515.060 ms  2418.845 ms
 8  gar8.cgcil.ip.att.net (12.122.133.161)  2349.706 ms  2339.392 ms  583.224 ms
 9  192.205.37.150 (192.205.37.150)  1396.288 ms  1732.779 ms  2664.270 ms
10  4.69.158.138 (4.69.158.138)  2690.646 ms
4.69.158.130 (4.69.158.130)  2313.195 ms
4.69.158.138 (4.69.158.138)  1261.560 ms
11  ae-3-3.ebr2.denver1.level3.net (4.69.132.61)  1476.892 ms  1819.138 ms  
2188.664 ms
12  ae-1-100.ebr1.denver1.level3.net (4.69.151.181)  1490.142 ms  2916.895 ms  
2569.848 ms
13  ae-3-3.ebr2.sanjose1.level3.net (4.69.132.57)  4328.125 ms  3226.550 ms  
2648.859 ms
14  ae-72-72.csw2.sanjose1.level3.net (4.69.153.22)  2171.863 ms
ae-82-82.csw3.sanjose1.level3.net (4.69.153.26)  2675.059 ms
ae-92-92.csw4.sanjose1.level3.net (4.69.153.30)  4404.724 ms
15  ae-1-60.edge2.sanjose3.level3.net (4.69.152.17)  3331.595 ms
ae-2-70.edge2.sanjose3.level3.net (4.69.152.81)  3112.938 ms  2492.688 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *

Greg

Re: http/ssl to dropbox.com dying

[Israel G. Lugo]

Hi,

On 06/29/2012 11:20 PM, Greg Ihnen wrote:
 It seems like a transport issue.

 Is there any tools for checking where an https connection is failing, like a 
 traceroute for https?

GNU/Linux traceroute sends UDP by default. Something along the way could
be filtering UDP, so default traceroute may not be indicative.

To better replicate the problem, you can tell traceroute to send TCP
SYNs to the specific port you're trying to reach (443). Run this as root
(it needs raw sockets):

# traceroute -M tcp -p 443 dropbox.com

Regards,
Israel G. Lugo