You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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.
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.
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?
The text was updated successfully, but these errors were encountered: