Chef Vagrant Couldn't resolve host 'www.getchef.com' - ruby

When I'm running:
:$ vagrant provision
or
:$ vagrant up
I'm getting this error:
nisevi#localhost processor (master):$ vagrant provision
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Couldn't resolve host 'www.getchef.com'
if anyone knows to what is related this error, I'm gonna be very grateful.
###################################EDIT
A colleague gave me this thread:
https://serverfault.com/questions/453185/vagrant-virtualbox-dns-10-0-2-3-not-working
as reference where I was able to find some interesting information about mi issue. But now I'm dealing with other problem: bit.ly/1BxehY0

Likely your VM doesn't have any network access due to an incorrect config and an incorrectly installed VirtualBox. Try commenting out the Chef provisioner and then log in to the VM using vagrant ssh. See if you can reach the internet from inside and if not, fix that before progressing. If you include the content of the Vagrantfile we might be able to help more.

For me following worked:
Did vagrant ssh (It threw error to do vagrant up).
Again did vagrant up.
That's all.

Related

Can not vagrant up virtual box - The provider 'virtualbox' that was requested to back the machine 'default' - /dev/vboxdrv does not exist

Now I am facing an error about vagrant and virtualbox. I can't up my vagrant. while I up my vagrant it is show error below.
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:
VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.
After I run "VBoxManage --version" it shows
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.
You will not be able to start VMs until this problem is fixed.
6.1.10_Ubuntur138449
Does anyone used to know this error, could you help me to fix this problem. I already search a lot but, cannot apply the solution. Sometimes they talk about disable secure boot. Thank you in advance !!
Ubuntu 20.04
Vagrant 2.2.9
Version 6.1.10_Ubuntu r138449

vagrant up - server not starting because a ssh library issue

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

Vagrant - The host path of the shared folder is missing: ../keys

When I try to run vagrant up or vagrant provision I get this error:
There are errors in the configuration of this machine. Please fix
the following errors and try again:
vm:
* The host path of the shared folder is missing: ../../../../keys
I already tried vagrant destroy but I get the same error.
Does anybody have suggestions on what to check?
I'm on ubuntu 15.10
I've had this once before and there's plenty of possible solutions on the web.
What worked for me is to simply create the folder that's apparently missing. Do the following (easiest on command line):
cd /path/to/wherever/it/is/supposed/to/be/
mkdir keys
You should then be able to vagrant up fine.

vagrant fails to start up in osx mountain lion

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

Could not resolve host error when trying to install the Homestead Vagrant Box

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.

Resources