I'm getting the following error when i run vagrant up
vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/trusty64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'ubuntu/trusty64'
default: URL: https://vagrantcloud.com/ubuntu/trusty64
==> default: Adding box 'ubuntu/trusty64' (v14.04) for provider: virtualbox
default: Downloading: https://vagrantcloud.com/ubuntu/trusty64/version/1/provider/virtualbox.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
SSL read: error:00000000:lib(0):func(0):reason(0), errno 50
From a brief Google, this seems to be a problem when your host machine, i.e. the real machine, you are setting up Vagrant on has an issue with the SSL connection to download the box that will be used.
What kind of laptop or desktop are you using, and what is the operating system? Are you up to date with any updates for the operating system (security updates, etc)?
Hi, my computer is ASUS X42D. I keep getting "SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054" when trying to add vagrant box. In Laravel they said to hardware virtualization (VT-x), but I can't find it in my BIOS. Any help please?
+1
+1
+1
+1
I had the same issue and I host .vbox at AWS S3. The errors are:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
SSL read: error:00000000:lib(0):func(0):reason(0), errno 60
After I swtich from S3 https to http, it works.
@gdbtek, I have the same problem with adding vagrant add box laravel/homestead (http://bit.ly/1WQNcIN). Could you tell me how exactly did you solved this problem? How to switch from https to http?
Same issue here, with Homestead as well
@komarnicki @Anahkiasen
vagrant box add laravel/homestead http://atlas.hashicorp.com/laravel/boxes/homestead
@zouchao, this fixed my problem: http://slick.pl/kb/software/vagrant-fix-for-error-60-ssl-read/
use
vagrant box add laravel/homestead -c
may works
use
vagrant box add laravel/homestead -c
may works
This made it work for me!
We found this worked for us -
vagrant box add --insecure -c laravel/homestead http://atlas.hashicorp.com/laravel/boxes/homestead
I get this on a MacBook Pro Retina 2013. It happened last time when I updated homestead and again now. This needs a proper fix than a workaround... Any solutions?
I also received this error on OSX simply because my shell had lost its internet connection halfway through the download.
After installing VirtualBox and Vagrant, I ran the command vagrant init hashicorp/precise64, then vagrant up. Halfway through the latter command, I walked away from my machine (which went inactive and required me to submit my credentials to log back in) and when I came back I had the error message above SSL read: error:00000000:lib(0):func(0):reason(0), errno 54. I issued another vagrant up command and continued working with the laptop rather than walk away, and the command finished without error status.
On OS/X, I repeated the "vagrant up" command after the error, and the process resumed and completed.
Uploaded a mirror to Google Drive. Download and add it manually. https://drive.google.com/file/d/0BxiUDyf4p8pdZHpPUGhwVkJ2VWc/view?usp=sharing
Experiencing this too with Vagrant 1.9.1. @jeremyfelt Could you reopen?
Caffeine + vagrant destroy -f; vagrant box remove -f <image>; rm -rf .vagrant; vagrant init <image> && vagrant up worked for me.
@Shkeats I'm not sure that this is a bug in VVV. From reading through the discussion here it seems like there can sometimes be an issue on the host machine or with the network connection. If it seems like something we can fix in VVV, please open a new issue with a clear list of steps to reproduce. Thanks!
+1 for me on Windows 10 just now. The download never completes.
I keep trying again and again, and I've even tried https://github.com/Varying-Vagrant-Vagrants/VVV/issues/401#issuecomment-166156672.
I'm trying to install a specific older version of Homestead (downgrading because of https://github.com/laravel/homestead/issues/510 since the latest version of VirtualBox seems to have a bug).
The problem was solved by running the windows updates
@angel1995j
Unfortunatley it wasn't ... Today i downloaded all the windows updates and still got this problem, Tried every solution here and it didn't work for me also after i updated virtualbox and vagrant
@moodgalal
The other you can do is check the php.ini file located in the root of your site and see the lines of ssl and see if there are any commented.
I'm using Windows 10 and replacing curl with the following one solved it for me:
Win64 x86_64 | 7zip | 7.54.1 | binary | SSL | SSH
Original source
Although the download speed still all over the place (first few seconds normal speed, than drops), this was the only binary which was able to keep-alive the connection (I don't know is it important that it includes the certificates or not). Even the MSYS2 mingw curl's are not finished the download.
OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104 on ubuntu 17.04
For those of you who has this problem
see the solution here
http://slick.pl/kb/software/vagrant-fix-for-error-60-ssl-read/
that's weird it's been years and the problem remains!
Then It worked for me 👍
Im using just vagrant reload command and try again. It works for me!
Well, I have the same error.
My OS is Wondows 10
Windows is update
But my error is the connection time to download.

What happen?
@DJviolin Where do you pasted curl file? In php folder?
@yosmangel I don't remember well what I did, maybe I replaced at C:\HashiCorp\Vagrant\embedded\mingw64\bin or I replaced it system-wise. I using MSYS2 with Mingw64 on windows, There are two curl paths: C:\msys64\mingw64\bin and C:\msys64\usr\bin.
@yosmangel that's not the same issue, that isn't even a VVV box, you should open a new issue over at Laravel Homestead, this is the VVV project
@tomjn My issue was the same, SSL read error, But, In my case, I solved my problem with the modem and call of my home telephone. Sorry
Just a quick up... (Maybe not the most secure way 🤷🏻♂️) I fixed the problem by running the command as Sudo.
@zigmasdirigeant do you mean sudo vagrant up? You should never run the vagrant commands with sudo, it will cause issues as all subsequent vagrant commands will require sudo too, and it wasn't built to be ran that way
Just a quick update: with the latest Vagrant version tested, third-party curl is not required. Just use the one that shipped with Vagrant (at least I don't need to use the monkey patching now).
vagrant box add laravel/homestead -c
This fixed it
@komarnicki @Anahkiasen
vagrant box add laravel/homestead http://atlas.hashicorp.com/laravel/boxes/homestead
This worked !! Thanks 👍
A reminder, this is not a support avenue for Laravel Homestead, this is the VVV project
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
use
may works