When I'm running vagrant provisioning I get this error. Can anyone help me?
I'm using antoniofrignani/laravel-homestead-settler-32 box in vagrant and it was working nice until yesterday.
Related
I have installed vagrant and virtual-box added homestead box on it now i am executing a command from terminal "vagrant up" which throws error here is snapshot:
I have installed virtual-box is 5.0 and vagrant is 1.8.1. I am totally stuck here. I don't know what should i do now? I am new to unubtu 16.04. Any kind of help will be appreciated.
I'm currently trying to create a virtual environment for wordpress development. I've installed Git Bash, ConEmu, Virtual Box, Vagrant, Vagrant Host updater, Vagrant triggers, and Varying Vagrant Vagrants. the first time I used vagrant up, I got this message:
default: Successfully added box 'ubuntu/trusty64' (v20150609.0.10) for 'virtualbox'! There are errors in the configuration of this machine. Please fix the following errors and try again:
vm: * The 'fix-no-tty' provisioner could not be found.
I don't really have any idea what this means and have had little success finding information on the internet. Does anyone know what the fix-no-tty provisioner is and how i could fix it?
I encountered the same issue today with a new clone of VVV while running Vagrant 1.6.3. The fix-no-tty provisioner was introduced on April 29. Named provisioner support was added to Vagrant in version 1.7.0. I upgraded to Vagrant 1.7.2 and was able to bring the VM up.
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.
Problem
I am attempting to get Laravel Homestead working on my Mac Book Air. I have followed the instruction from http://laravel.com/docs/4.2/homestead but when I vagrant up I get stopped on: default: Warning: Connection timeout. Retrying... After I vagrant up fails because of connection timeout i can not vagrant provision or vagrant reload. I can however vagrant ssh into the machine and I can ping google from the machine. I can also spin up other vagrant boxes on my machine with no problem...
Information:
OS: OSX 10.10 (Yosemite)
Vagrant: 1.6.5
Virtual Box: 4.3.16
I have searched around on the internet and found a few “solutions” that has not worked for me:
Turn on “Hardware Virtualisation”. This is automatically turned on in ant instal based mac computer.
Start VM with v.gui = true. This start the VM with with the server terminal in view. Nothing is throwing any errors. and this did not solve the problem
More Debugging Steps:
Tried just booting up the vagrant box laravel/homestead by running vagrant init laravel/homestead then vagrant up. This still gives the same problem.
I have tried vagrant box laravel/homestead versions 0.1.7, 0.1.8 and 0.1.9(newest) All giving the same problem.
Did you let the vagrant output continue after "default: Warning: Connection timeout. Retrying..." Vagrant may actually be retrying the connection. Sounds like you're exiting out when you see that error instead of waiting for vagrant to finish with an actual exit error
A year old post and maybe you have solved it, but I was struggling with it recently and just managed to solve it.
I had the same problem everything was configured correctly but there was no way to ping 192.168.10.10.
In my case it seemed that net-tools package wasn't installed in my distro (Archlinux) by default so installing it allowed me to connect.
See the relevant section at Archlinux Wiki.
Hope that helps someone.
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.