重新安装无线驱动程序后,“ vagrant”框现在挂在“ SSH身份验证方法:私钥”上

时间:2019-07-15 15:20:46

标签: ssh vagrant vmware

无法连接到图书馆的wifi。假定他们只是告诉我门户页面在哪里,就请他们的技术人员来做。相反,他卸载了Windows 10的wifi驱动程序并重新启动了我的计算机。现在,我所有无业游民的箱子都挂在SSH auth method: private key上,尽管之前工作正常,但最终还是超时了。

我已经确认BIOS中启用了虚拟化。确认Cable Connected在VMware配置中已勾选。已关闭防火墙。已删除insecure_private_key。已经摧毁并重建了无业游民的盒子。

是不是某些端口配置设置被清除了?

==> [censored]: Checking if box 'zodiacmedia/ubuntu-16.04-x64' version '1.0.7' is up to date...
==> [censored]: Verifying vmnet devices are healthy...
==> [censored]: Preparing network adapters...
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING:   ethernet0.pcislotnumber = "32"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING:   Vagrant.configure(2) do |config|
WARNING:     config.vm.provider :vmare_workstation do |vmware|
WARNING:       vmware.vmx["ethernet0.pcislotnumber"] = "32"
WARNING:     end
WARNING:   end
WARNING:
WARNING: For more information: https://www.vagrantup.com/docs/vmware/boxes.html#vmx-whitelisting
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING:   ethernet1.pcislotnumber = "33"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING:   Vagrant.configure(2) do |config|
WARNING:     config.vm.provider :vmare_workstation do |vmware|
WARNING:       vmware.vmx["ethernet1.pcislotnumber"] = "33"
WARNING:     end
WARNING:   end
WARNING:
WARNING: For more information: https://www.vagrantup.com/docs/vmware/boxes.html#vmx-whitelisting
==> [censored]: Starting the VMware VM...
==> [censored]: Waiting for the VM to receive an address...
==> [censored]: Forwarding ports...
    [censored]: -- 22 => 2222
==> [censored]: Waiting for machine to boot. This may take a few minutes...
    [censored]: SSH address: [censored].60.130:22
    [censored]: SSH username: vagrant
    [censored]: SSH auth method: private key
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.

出于隐私原因,将域名和IP更改为[审查]。它看起来与工作时相同,但始终不会超过最后一行。

0 个答案:

没有答案