Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vagrant up error 416 #11740

Closed
drchibs opened this issue Jul 4, 2020 · 3 comments
Closed

Vagrant up error 416 #11740

drchibs opened this issue Jul 4, 2020 · 3 comments

Comments

@drchibs
Copy link

drchibs commented Jul 4, 2020

this happens every time I run vagrant up on homestead folder, and the vagrant version is Vagrant 2.2.9
is there a fix, please?

$ vagrant up
Bringing machine 'homestead' up with 'virtualbox' provider...
==> homestead: Box 'laravel/homestead' could not be found. Attempting to find and install...
    homestead: Box Provider: virtualbox
    homestead: Box Version: ~> 9.5.0
==> homestead: Loading metadata for box 'laravel/homestead'
    homestead: URL: https://vagrantcloud.com/laravel/homestead
==> homestead: Adding box 'laravel/homestead' (v9.5.1) for provider: virtualbox
    homestead: Downloading: https://vagrantcloud.com/laravel/boxes/homestead/versions/9.5.1/providers/virtualbox.box
==> homestead: Box download is resuming from prior download progress
Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
    homestead:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

The requested URL returned error: 416
@soapy1
Copy link
Contributor

soapy1 commented Jul 6, 2020

Hey there, thanks for the report. In order to better understand what's going on, could you also provided the (smallest) Vagrantfile to reproducing this error and a debug gist.

@chrisroberts
Copy link
Member

Hi there,

It appears that you may have tried to download this once before unsuccessfully, and Vagrant is attempting to resume the download but the partial file is corrupted or incorrect. You should be able to resolve this by removing any files within the tmp directory in your VAGRANT_HOME. This is usually in your home directory (~/.vagrant.d/tmp).

Once they are removed, the download should successfully restart from the beginning.

Cheers!

@ghost
Copy link

ghost commented Aug 6, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@hashicorp hashicorp locked and limited conversation to collaborators Aug 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants