1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #9839 resolved

Unable to download/pull from repository

Oded Handel
created an issue

Trying to download a repository of ~3.5k files, 1GB packed. The download stops mid-way every single time, always at different stages of download completion. Trying to use a download manager ends up with a "request to server timed out" error. What's more, Bitbucket doesn't allow download resuming, so I have to start the download anew every time it happens (happened at 96.6% downloaded today, ARGHHH!)

Pulling from the repository using SourceTree yields the same result (the difference being it takes MUCH longer, between 15 minutes and an hour), with the following error:

fatal: early EOF

fatal: The remote end hung up unexpectedly fatal: index-pack failed

error: RPC failed; result=18, HTTP code = 200

I'm literally pulling my hair out at this. Please, does anybody know why it's so difficult to download from my repository???

Comments (5)

  1. Abhin Chhabra staff

    Hi Oded Handel

    I was able to clone the repo on my machine without issues. Could you try using SSH?

    abhin:tmp abhinchhabra$ git clone git@bitbucket.org:Zulthus/attack-on-titan.git
    Cloning into 'attack-on-titan'...
    remote: Counting objects: 5047, done.
    remote: Compressing objects: 100% (3254/3254), done.
    remote: Total 5047 (delta 2473), reused 4252 (delta 1784)
    Receiving objects: 100% (5047/5047), 1011.11 MiB | 1.75 MiB/s, done.
    Resolving deltas: 100% (2473/2473), done.
    Checking connectivity... done.
    Checking out files: 100% (2114/2114), done.
  2. Oded Handel reporter

    Hi Abhin,

    I was able to download the repo manually last night, after countless trials. I can say I've used both HTTPS and SSH in SourceTree and both had the same issue. Downloading manually and watching the download progress, I could see the download speed rise and drop constantly, as if the connection was very unstable. Could it be something with my connection or ISP? I've never had such issues with any website.

  3. Log in to comment