"vagabond up" stops on SSH auth method: private key
I am trying to install laravel on my environment machine. I followed all the steps in the official documentation . And when I execute my "vagrant" my console displays the following error.
...
Stop in SSH mode. I used to set up ssh-keygen with "ssh-keygen -t rsa -b 4096 -C" me@email.com "
I added the node part to the .rb file:
Even the .yaml file. I think I edited correctly
In the hosts file I added "192.168.10.10 administracio.dev" at the bottom of the file.
And then when I resolve this error, the following error appears:
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.
Any suggestions?
source to share
The solution works for me too: when configured in Bios "Intel Virtualization Technology = Enabled", the "SSH auth method: private key" step is not frozen yet and the virtual machine starts normally. When you return to the "Intel Virtualization Technology = Disabled" Bios, the "SSH auth method: private key" step is frozen again.
Motherboard: Asus Z170 Pro Gaming (lga1151), Bios Menu: Advanced \ Cpu Configuration, Virtual Box: 5.1.22, Vagrant: 1.9.5, Windows 10
source to share
I had the same problem today and found that my VirtualBox settings (Network | Advanced | Connected) are set correctly (this is a checkbox.) I started comparing this VM, which has been stable for several months, with some of my other virtual machines and found that the only difference was in the network adapters, since adapter 2 is different from the rest.
Adapter 1 was installed to the following:
Attached To: NAT
Adapter Type: Intel PRO/1000 MT Desktop ....
while adapter 2 is set to the following ...
Attached To: Host-only Adapter
Adapter Type: PCnet-FAST III ...
I haven't changed any of these network settings in VirtualBox, ever. Once I have set the adapter type of adapter 2 to the same settings as adapter 1 as above, I then wander around, stop and wander up and return to normal.
source to share