Unable to clone from http://eukaryota.dathub.org

[lmsurpre]

I've been tracking dat for a while and decided to try the tutorial today. I got stuck on the following step:

> dat clone http://eukaryota.dathub.org eukaryota
Cloning http://eukaryota.dathub.org into eukaryota...
Progress:  [+0, -0].
socket hang up

I'm guessing it has something to do with our corporate firewall because the same command worked fine from http://try-dat.com/
How to help debug?

PS. I'm on OS X Yosemite

[lmsurpre]

Cloning the sample from the tutorial into my local environment failed in a similar manner.
When I left the office, the dat clone from eukaryota completed successfully.
So, I think my suspicion was correct: there's no problem with the get-dat tutorial and this issue can be closed. If there is a simple way to collect debug/trace information from the failed dat clone, I would be happy to open an issue with this information at https://github.com/maxogden/dat

[max-mapper]

Hiya,

I am able to clone http://eukaryota.dathub.org from the cafe wifi that i'm
on, so it must be a corporate filewall issue. We are in the process of
moving all of the dathub example dats to https:// which should increase the
connection success rate quite a bit actually. We were testing cloning
recently over a t-mobile hotspot while roaming and were having connection
issues on http that went away when we switched to https (aggressive and/or
poorly implemented proxies).

edit: just saw your new comment, glad to hear it eventually worked, and
thanks for the debug offer

On Mon, Aug 31, 2015 at 12:14 PM, lmsurpre notifications@github.com wrote:

I've been tracking dat for a while and decided to try the tutorial today.
I got stuck on the following step:

dat clone http://eukaryota.dathub.org eukaryota
Cloning http://eukaryota.dathub.org into eukaryota...
Progress: [+0, -0].
socket hang up

I'm guessing it has something to do with our corporate firewall because
the same command worked fine from http://try-dat.com/
How to help debug?

PS. I'm on OS X Yosemite

—
Reply to this email directly or view it on GitHub
#36.