9
Vagrant Version: 1.6.3
VirtualBox: 4.3.14
Ubuntu 14.04 LTS 64 Bit

I have been on this for a pretty good while now and cannot figure this out. I have my public and private keys setup and they work. I know they are not the problem at they worked fine before I updated Ubuntu from 32 Bit to 64 Bit. I have uninstalled and reinstalled all software mentioned and still no fix. This is on a Laravel Homestead instance but it is happening on all my boxes, including the precise32 from vagrants home page.

When I run vagrant ssh-config The error I am getting is

    The provider for this Vagrant-managed machine is reporting that it
    is not yet ready for SSH. Depending on your provider this can carry
    different meanings. Make sure your machine is created and running and
    try again. Additionally, check the output of `vagrant status` to verify
    that the machine is in the state that you expect. If you continue to
    get this error message, please view the documentation for the provider
    you're using.

This did not happend when I was on 32 Bit, but I had other issues when is what caused me to move up to 64 Bit.

When I run vagrant up, it stops on this line:

==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2201
default: SSH username: vagrant
default: SSH auth method: private key

Any thoughts on this would be welcomed. I hate that this is happening as I just recently released a podcast episode on how awesome development on Vagrant WAS as of right now, its sucking my time to try to get this in order. Thanks to all in advance!

peterh
  • 4,953
  • 13
  • 30
  • 44
devcflynn
  • 91
  • 1
  • 1
  • 2
  • Any info in the VirtualBox GUI? Check that the machine isn't hung on something like GRUB in the little preview image. – xofer Aug 07 '14 at 17:06
  • So when I turn **config.vm.gui = true** on - everything boots fine but it ask for a user name and password at the login prompt. This is what the key is suppose to bypass as far as I understand. I know there is the ability to set it to insecure login, but I do not want to do that. – devcflynn Aug 07 '14 at 17:21

2 Answers2

0

2022 I have the same issue with building vagrant box run vagrant ssh-config got this message. but I solve it on Windows10 by following:

In Vagrantfile add

config.ssh.private_key_path = ["~/.ssh/your_key", "~/.vagrant.d/insecure_private_key"]
config.vm.provision "file", source: "~/.ssh/your_key.pub", destination: "~/.ssh/authorized_keys"

vagrant up && vagrant ssh works for me.

praHoc
  • 101
  • 1
0

You need to add a valid public key to the vagrant user inside the VM. See: https://stackoverflow.com/a/14719184/938598

Community
  • 1
xofer
  • 3,072
  • 12
  • 19