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
Related
I installed correctly vagrant but when I try to open vvv.test browser don't allow to show me the page
no erros when I initialized vagrant
I work on windows 10, a new installation with no particular environment. I use vagrant on my laptop and no problem incurred. On this new installation if I use the last version of vagrant I can't initialized vagrant because an error of vagrant to download the package. I installed the same version of vagrant on my laptop vagrant_2.2.10_x86_64 and I can do all except for the error of browser.
I can access without problem with ssh.
I don't know why I have this problem
I am currently in the process of downloading homestead and laravel. I already downloaded vagrant and VirtualBox 5.x. When I input vagrant box add laravel/homestead I get this error:
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 Atlas, 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://atlas.hashicorp.com/laravel/homestead"]
Error:
I tried googling what the issue may be and didn't find anything that helped. I am using a mac if that helps.
Any help would be greatly appreciated!
As Frédéric Henri answered on Vagrant box could not be found or could not be accessed in the remote catalog - incompatible curl version you need to run following command:
sudo rm /opt/vagrant/embedded/bin/curl
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.
Virtual Box 4.3.14
Vagrant 1.6.3
and when I vagrant up I get this error
default: warning: connection refused. Retying...
it goes on and on until it gives up and says
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
I am on windows 7, I even tried running cmd on administrator mode same thing
I even tried vagrant reload as I read on on other web resources, still same thing, it outputs the same thing
I did not tweak my virtualbox after install, basically just install virtualbox and install vagrant then run vagrant up
and oh by the way my vagrantfile and provisioning script is from here
https://gist.github.com/JeffreyWay/9244801
https://gist.github.com/JeffreyWay/9244714
Been googling and unfurtunately I can't find clear answer
Tnx in advance
It seems its a virtual box / vagrant version incompatibility issue
I uninstalled Virtual Box 4.3.14 and installed Virtual Box 4.3.12 and it worked. Basically I downgraded virtual box.
I hope this gets fixed soon.
Hope this helps anyone.
Open your vagrantfile using notepad and edit it so that it looks like this:
Please tally your vagrantfile with this one word by word. Then open BIOS and turn on virtualisation. Watch this video to learn how to do it. It is a very short video.
PS: You may need to uninstall vagrant before doing this. And in your Users folder in C:, there will be a folder named .vagrant.d, please delete that as well before following these steps.
Uninstalling vagrant will require that you run your machine as administrator. You can right click on Command Prompt (search cmd in windows search box) and click run as administrator. Type the following command: net user administrator /active:yes
You will get a message called command completed successfully. Now you can log off and see that there are two accounts, one of them is admin. You can log in from that and uninstall vagrant.
I'm having problems installing the Homestead Vagrant box following the guide on the Laravel docs.
I have the current latest version of Vagrant (2.2.6) and whenever I'm trying to add the laravel/homestead box to my Vagrant installation using vagrant box add laravel/homestead I get this error:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Could not resolve host: vagrantcloud-files-production.s3.amazonaws.com
Anyone have a clue on how to fix this and/or where the problem lies? Would be much appreciated.
Okay it works now as Kenny already said, for some reason now (a day later) files begin to download. Looks like it was a problem with S3 or something.