Basically I got this error seconds after I trigger
vagrant box add laravel/homestead in my terminal.
What's more interesting, after second failed attempt, the error message is a little bit different (as you see).
Error number 60 is somehow related to SSL. Since I'm running this command via terminal, I really have no idea how to investigate this issue. Can somebody give me any hints? May it be related to poor wireless internet connection?
slick-mac:~ slick$ vagrant version
Installed Version: 1.7.4
Latest Version: 1.7.4
You're running an up-to-date version of Vagrant!
If you get an SSL issue, you can try to add the box using the insecure option
vagrant box add --insecure laravel/homestead
--insecure When present, SSL certificates won't be verified if the URL is an HTTPS URL
I'm deliberately posting this as an answer because probably I've found solution. So far it's still downloading.
What I did:
1. I removed temp stuff
rm -rf ~/.vagrant.d/tmp/
2. I started the download again
vagrant box add laravel/homestead
So far it's still OK despite of my slow internet connection. If that won't work I will try Frederic's solution.
EDIT:
After 80% it failed. (no --insecure) param.
These SSL related issues are not from client side. It is originated from the source. We can do nothing from our side. I have tried with Windows OS, Mac OS X and manual download with many browsers and even with downloaders, no luck. Somehow I managed to download with mobile browser on 4G. I was wondering why not upload this to place everyone can download.
You can find a mirror here on my Google Drive. It is a copy of laravel/homestead 0.5.0. Have fun.
I encountered the same issue. Adding --insecure argument, specifying url, https://atlas.hashicorp.com/laravel/boxes/homestead, and removing the tmp file beforehand did not work for me.
Brutely repeating download attempts to download did however. Thus, in my case, nothing to do with SSL.
what Worked for me was emptying the temp first then running the following command:
vagrant box add --insecure laravel/homestead
it looks like after failing once ,it couldn't resume correctly until the temp was emptied .
hope this helps.
Related
I have just downloaded the latest version of Vagrant 2.2.15 and VMware. I tried to run
vagrant box add laravel/homestead
But I get
The box 'laravel/homestead' could not be found or could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
vagrant login. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://vagrantcloud.com/laravel/homestead"]
Error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
After checking https://app.vagrantup.com/laravel/boxes/homestead I run
vagrant init laravel/homestead
Then try to run
vagrant up
But I never got it to work and keep getting the same error message. I found this solution https://github.com/hashicorp/vagrant/issues/6764 and installed MS Visual C++ 2010 x86 Redistributables but can't run vagrant up or don't even know how to install homestead after the last update. I used to install it the old same way without issues multiple times but today I couldn't
I tried
vagrant box add laravel/homestead https://atlas.hashicorp.com/laravel/boxes/homestead
But I get
There was an error while downloading the metadata for this box.
The error message is shown below:
schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
I checked the temp here .vagrant.d\tmp but it's empty.
Any help please on installing and running laravel homestead on Windows 10?
Disabling antivirus software (Kaspersky in my case) solved the problem for me.
For me It was Kaspersky as well, but you don't have to disable it everytime you can add an exception to Kaspersky network trusted addresses
Open Kaspersky
Click on the bottom left cog.
Open Network Settings
Click on Trusted addresses
add: vagrantcloud.com
save
Test
vagrant up
vagrant box add laravel/homestead
I assume if you having this issue and it's using another Antivirus the problem /solution is the same, or maybe some proxy intercepting https traffic.
We also only recently encountered this error when using the 2.2.15 version of Vagrant. Downgrading back to Vagrant 2.2.14 was our answer. This could be a Vagrant bug.
Temporarily disable web shield if you're using avast.
Tried adding the domains and app to a trusted list but still without success. This seemed to be the minimum to get the job done
My antivirus was avast, disabling worked for me as well
I have recently started using Laravel Framework 5.6.7 and have everything running smoothly apart from the Zray toolbar it comes with. The toolbar displays the error: "Failed to communicate with Zend Server. See why..."
the link takes me to the troubleshooting page which is of no help:
http://files.zend.com/help/Z-Ray-Azure/Content/troubleshooting.htm
In my local environment I am using the homestead vagrant box:
Vagrant 2.0.2
I tried following this old post but Zray is already installed so I thought it must be a configuration issue:
https://laravel-news.com/installing-zend-z-ray-on-homestead
any ideas on how I can get this toolbar to work would be much appreciated.
I had this issue too and it took a few days to get it resolved. I have no idea if this will work for you but this is how I did it:
Removed all vagrant boxes in my Homestead folder. vagrant box remove --all https://www.vagrantup.com/docs/cli/box.html
Add vagrant box. vagrant box add/laravel/homestead
perform a git pull in the Homestead folder. git pull origin master
went to composer.json and deleted "laravel/homestead": "^7" (also deleted the trailing comma to ensure the JSON was valid).
ran composer update.
Then after a vagrant up --provision (I wasn't sure if provision was needed but I put it just in case), I went to my site and no more Z-RAY issues!
I hope this helps someone else because this was NO fun to figure out.
You have to add
> zray: "true"
in your Homestead.yaml file
I get this errormessage:
An error occurred in the underlying SSH library that Vagrant uses. The
error message is shown below. In many cases, errors from this library
are caused by ssh-agent issues. Try disabling your SSH agent or
removing some keys and try again.
It is my first time with vagrant.
I took a tour through this tutorial.
https://wpbeaches.com/setting-up-a-wordpress-vvv-vagrant-workflow/
I've windows 10, vagrant 1.8.5, Oracle VM newest version.
I read a lot about this issue but nothing helps me.
Maybe somebody knows a solution.
Please try this command
vagrant halt
from inside your homestead directory
I had the same issue and this resolved my issue
Trying to install Vagrant on Windows 7 X64 with installer from Vagrant - vagrant_1.7.0.msi
Installation goes fine, however unable to use vagrant. On any command, for example vagrant -v the below is shown:
Failed to find Vagrant!
What I did:
Googled. Only 1 link with such an error on github regarding to installer. Not sure if this is relevant.
Checked that vagrant in PATH. Yes it is. Otherwise it would not start at all.
Reinstalled, and repaired - few times.
All the above with no luck. Any idea where to dig?
Thank you.
just to add my own version of this problem too:
i installed version 1.7.0
error message after a "vagrant up": "Failed to find Vagrant!"
checked paths, other environment variables in win7, should work..
so i uninstalled it and installed an older version (1.6.5)
and yes, the older version solved the problem.
i got it from their official website: https://www.vagrantup.com/download-archive/v1.6.5.html
i guess the problem was in this file:
https://github.com/mitchellh/vagrant-installers/blob/master/substrate/launcher/main.go
Same Issue on Windows 7 64.
Downgraded back to Vagrant 1.6.5
Have you gone through the installation instructions on vagrant side listed here :
https://docs.vagrantup.com/v2/installation/index.html
This is what I see listed at their site:
The installer will automatically add vagrant to your system path so that it is available in terminals. If it is not found, please try logging out and logging back in to your system (this is particularly necessary sometimes for Windows).
Please try running it from Git Bash too and let me know if it works for you.
And if you still run into issues, try using an older version of vagrant https://www.vagrantup.com/download-archive/v1.6.5.html
Vagrant 1.7.1 should fix this. https://github.com/mitchellh/vagrant/issues/4924#issuecomment-66808666
I am using Vagrant version 1.1.5 and virtual box 4.2.22. when i do vagrant up, It fails with the following error
Error: The VM failed to remain in the "running" state while attempting to boot. This is normally caused by a misconfiguration or host system incompatibilities. Please open the VirtualBox GUI and attempt to boot the virtual machine manually to get a more informative error message.
I check the virtual box logs, It says /Applications directory is writable by everyone. So I fixed it by removing the write permission for the work for /Applications directory.
But the problem is the permission gets reset almost daily. I have to redo the above the fix daily to use vagrant. Any body know why this is happening or any direction I could take to fix this ?
Regards
Rajesh
I dont think the issue is to do with the permissions - well probably not... that will probably just be a warning.
Try running vagrant in Gui mode to see if you can see any errors in the VM itself.
http://docs.vagrantup.com/v2/virtualbox/configuration.html
First check if you are able to do
VAGRANT_LOG=debug vagrant ssh
if not the following solution is most probable.
One of the common error is configuration of ssh key .which one the notice using.
VAGRANT_LOG=debug vagrant up
There if you see vagrant looping for ssh key.
you can easily fix that using following commands .
vkey() { sudo chown "$*":staff ~/.vagrant.d/insecure_private_key;
vkey <new_owner_username>
here vkey() is the zsh function.
credits: https://superuser.com/questions/612376/vagrant-vm-fails-to-boot
-let me know if problem still exists
Cheers