vagrant up fails after aborted download

[shaicoleman]

If a download is interrupted during "vagrant up", and the server doesn't support HTTP byte ranges, subsequent invocations of vagrant up will return the curl error "HTTP server doesn't seem to support byte ranges. Cannot resume.", exception: Vagrant::Errors::DownloaderError

Expected behavior:
If the server does not support byte ranges, the incomplete file should be deleted and retried.

Vagrant 1.6.5
Ubuntu 14.04 LTS
curl 7.35.0

[jschiessl]

I'm having the exact same issue with the exact same version of Vagrant under Windows 8.1. Had to go to .vagrant.d\tmp and delete the partial download.

[rayburgemeestre]

+1

[mcranwill]

+1, that solved my issue also

[temujin9]

+1, same issue and resolution.

[VincentVToscano]

+1

[gremdev]

+1

[mitchellh]

This is pretty bad. Thanks for the catch.

[VincentVToscano]

No problem. Thanks for a great product.

[mitchellh]

Fixed

[aidanmorgan]

I seem to be having this issue with the latest, it only seems to happen with HTTPS connections, HTTP works fine.

[davidkazuhiro]

This is still happening for me when using https://dl.bintray.com/mitchellh/vagrant/vagrant_1.7.1_x86_64.deb

david@david-VirtualBox:~/vagrant/centos6$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'relativkreativ/centos-6-minimal' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'relativkreativ/centos-6-minimal'
    default: URL: https://atlas.hashicorp.com/relativkreativ/centos-6-minimal
==> default: Adding box 'relativkreativ/centos-6-minimal' (v1.0.0) for provider: virtualbox
    default: Downloading: https://atlas.hashicorp.com/relativkreativ/boxes/centos-6-minimal/versions/1.0.0/providers/virtualbox.box
==> default: Box download is resuming from prior download progress
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

HTTP server doesn't seem to support byte ranges. Cannot resume.
david@david-VirtualBox:~/vagrant/centos6$ vagrant -v
Vagrant 1.7.1

[cgood92]

All you need to do is simply delete the temporary download file, which is located (in the Windows world) at: C:\Users<username>.vagrant.d\tmp*
After you delete it, you can re-run vagrant up and everything should work fine.

[anandjainjk]

That worked for me. Thanks

[sergiotapia]

Still an issue for me.

• Vagrant 1.7.2
• Mac OSX Yosemite

---

The download timed out, and then when I ran the vagrant up command again to download it says:

HTTP server doesn't seem to support byte ranges. Cannot resume

I think Vagrant should be smart enough to toss the tmp data for that image, if the response server does not support byte ranges. Thanks!

[atommyb]

For any Mac users:
Remove ~/.vagrant.d/tmp/ directory.
Then try 'vagrant up' again.

[brunodles]

This keeps ocurring.
On linux we must remove files using that command
rm ~/.vagrant.d/tmp/*
Then vagrant up again

[levlaz]

This is still an issue for me on Debian Testing (Stretch) with the latest Vagrant package installed 1.7.2+dfsg-4, removing from .vagrant.d/tmp resolves the issue for me.

[BrendanTWhite]

Same problem, same fix, when Updating 'laravel/homestead' with provider 'virtualbox' from version '0.2.6' to '0.2.7' under Yosemite 10.10.3.

[mitulgolakiya]

getting same problem with 'laravel/homestead' virtualbox for version 0.2.7 with Yosemite 10.10.4.

[BrendanTWhite]

@mitulgolakiya did you try rm ~/.vagrant.d/tmp/* and then vagrant up again? That fixed it for me when I had this issue.

[kazemisoroush]

+1 👍

[cesarcruzc]

Thanks!

[timozattol]

Happened to me after "ctrl+c"ing the process during a vagrant box update, since it was taking too long for my connection. Removing all temp files in vagrant.d resolved the problem though 👍
Thanks!

[ghost]

+1 on deleting tmp files on mac

[danieljimenez]

+1 👍

[ascsoftware]

On Ubuntu 12.04 check for tmp files with: ls -al ~/.vagrant.d/tmp/
Then delete the image rm ~/.vagrant.d/tmp/boxf6d5788a461c7fff8e60ab85ed9732f64a77fa0f
And restart download process with vagrant up.
Worked on vagrant 1.7.3 and Virtualbox 5.0

[tedstein]

+1

[RossBarnie]

+1 Vagrant 1.7.4, OS X 10.10, deleting the tmp box "fixed" the issue but given the number of plusses above since the issue was closed it should perhaps be re-opened.

[robmarano]

+1 on deleting tmp files on mac. Find it in /Users/$USER/.vagrant.d/tmp. Thanks!

[ericrini]

This doesn't seem to be fixed.

[kentaguilar]

Still occurs on my end on OSX. Ran the following code.

rm ~/.vagrant.d/tmp/*
Then run the vagrant command again.

[livemixlove]

+1

[bijanvakili]

+1

[anthonygreen]

"Still occurs on my end on OSX."
+1

[Gandem]

Delete .vangran.d/tmp/* worked for me. The error still occurs on Windows 10

[JBusch]

+1 on Windows 10

[chrisgame]

Have you guys tried vagrant box add <box name> --clean. The fix would be better but at least this way you don't have to go digging around for files.

[nprokopic]

+1 for removing a partial download from ~/.vagrant.d/tmp.

Vagrant 1.7.4, OS X 10.10.4

[davidyell]

I just found this issue by googling for the error. I can see I'm not alone. I'm using 1.7.4 on OSX.

[ludo237]

+1 the patch works for OSX 10.11.2 Beta (15C40a) with Vagrant 1.7.4

[pfuhrmann]

Same issue with the 1.7.4 on Linux Mint 17.2

[mitchellh]

Reproduced, taking a look.

[mitchellh]

Fixed

[davidrichied]

Same issue on Mac OSX 10.9. Deleting the files in .vagrant.d/tmp/ fixed the issue.

[pfuhrmann]

@davidrichied @gonciarz do you have latest gem built from git? Fix is scheduled for 1.8 release I believe.

[davidrichied]

@pfuhrmann I do not believe I do. I downloaded Vagrant, version 1.7.4, from https://www.vagrantup.com/downloads.html

[omurphy27]

+1

This just happened to me and I solved it by doing rm ~/.vagrant.d/tmp/*

On Mac OS X El Capitan 10.11.2 (15C50) and Vagrant 1.7.4

[RossBarnie]

@nirajbothra This has been fixed in Vagrant 1.8.1, you should upgrade to resolve the problem.

[ghost]

This just happened for me on Windows using 1.7.4. cgood92's comment worked for me.