Vagrant up失败并发出警告:远程连接断开。重试

Vagrant up失败并发出警告:远程连接断开。重试,vagrant,virtualbox,centos7,vagrant-windows,Vagrant,Virtualbox,Centos7,Vagrant Windows,升级到vagrant版本2.1.1和最新的centos/7(virtualbox,1803.01)并且$vagrant up现在在加载新密钥后无法生成。正在使用的Vagrant文件在以前版本的Vagrant(2.0.3)上运行良好 有趣的是,我能够使用vagrant手动连接到实例,使用新密钥,既可以使用direct ssh,也可以使用: $vagrant ssh nat 已尝试的内容: vagrant config.vm.boot_timeout内的延长超时=1200 在重新安装之前,已卸载va

升级到vagrant版本2.1.1和最新的centos/7(virtualbox,1803.01)并且$vagrant up现在在加载新密钥后无法生成。正在使用的Vagrant文件在以前版本的Vagrant(2.0.3)上运行良好

有趣的是,我能够使用vagrant手动连接到实例,使用新密钥,既可以使用direct ssh,也可以使用:

$vagrant ssh nat

已尝试的内容:
vagrant config.vm.boot_timeout内的延长超时=1200
在重新安装之前,已卸载vagrant和virtualbox+手动删除插件并删除C:\Users\owner\.vagrand.d和C:\Users\owner\.virtualbox目录
尝试了以前有效的旧版本nat.vm.box_version=“1704.01”

为什么不回滚?
最初我升级了,因为我有另一个问题,我将提出一个单独的线程。一旦我创建了它,就会链接到这里

版本
主机操作系统:Windows 7 Professional
来宾操作系统:centos/7 1803.01

流浪版本:2.1.1

流浪者插件列表:
流浪旅店经理(1.8.8)
流浪宿主(2.8.1)
流浪者proxyconf(1.5.2)
流浪重新装载(0.0.1)
流浪股(1.1.9)
流浪客(0.15.1)

还显示了我的稍微消毒过的流浪汉档案。列出的脚本中没有一个实际运行,因为在执行之前,框失败

# -*- mode: ruby -*-
# vi: set ft=ruby :

# abbreviated brand name
BRAND_NAME = "brand"
TOP_LEVEL_DOMAIN = ".some.dev"
BOX_NAME = "centos/7"

Vagrant.configure(2) do |config|

  config.vm.synced_folder ".", "/vagrant", type: "virtualbox"
  config.vm.boot_timeout = 1200

  if Vagrant.has_plugin?("vagrant-proxyconf")
    config.proxy.http     = "http://192.168.100.3:3128/"
    config.proxy.https    = "https://192.168.100.3:3128/"
    config.proxy.no_proxy = "localhost,127.0.0.1,.some.lan"
  end

  config.vm.provider :virtualbox do |vb|
    vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
    vb.memory = 2048
    vb.cpus = 2
    vb.customize ["modifyvm", :id, "--cpuexecutioncap", "50"]
  end

  config.vm.define "nat" do |nat|
    nat.vm.box = BOX_NAME
    nat.vm.network "private_network", ip: "10.0.0.2", virtualbox__intnet: true
    nat.vm.hostname = "nat.staging." + BRAND_NAME + TOP_LEVEL_DOMAIN
    nat.vm.provision :hosts, :sync_hosts => true
    nat.vm.provision "shell", path: "./scripts/aws_replication.sh"
    nat.vm.provision "shell", path: "./scripts/nat_ssh.sh"
    nat.vm.provision "shell", path: "./scripts/nat_staging.sh"
    nat.vm.provision "shell", path: "./scripts/nat_git_clone.sh"
    nat.vm.provision "shell", path: "./scripts/nat_set_ansible.sh"
  end

  config.vm.define "fei" do |fei|
    fei.vm.box = BOX_NAME
    fei.vm.network "private_network", ip: "10.0.0.4", virtualbox__intnet: true
    fei.vm.network "forwarded_port", guest: 80, host: 80, auto_correct: true
    fei.vm.network "forwarded_port", guest: 443, host: 443, auto_correct: true
    fei.vm.network "forwarded_port", guest: 9000, host: 9000, auto_correct: true
    fei.vm.provision :hosts, :sync_hosts => true
    fei.vm.hostname = BRAND_NAME + ".staging" + TOP_LEVEL_DOMAIN
    fei.vm.provision "shell", path: "./scripts/aws_replication.sh"
    fei.vm.provision "shell", path: "./scripts/non-nat_key_staging.sh"
  end
end

nat:检测到不安全的密钥。流浪汉将自动替换
nat:这是一个新生成的密钥对,以提高安全性

每次运行“Vagrant up”命令时,它都会尝试查找不安全的密钥并替换它。要使用路径“config.ssh.private_key_path”中提到的默认密钥,请在Vagrant文件中包含以下条目


请在您的Vagrant文件中使用config.ssh.insert_key=false,然后再试一次。

我使用OSX,通过重新启动计算机解决了此问题。

这可以作为注释安全地显示。您能告诉我们Vagrant文件的位置吗?提前谢谢!在Windows上,Vagrant文件的完整路径是:C:\Users\your username\.Vagrant.d\box\laravel Vagrant Slash homestead\9.1.0\virtualbox\Vagrant文件
# -*- mode: ruby -*-
# vi: set ft=ruby :

# abbreviated brand name
BRAND_NAME = "brand"
TOP_LEVEL_DOMAIN = ".some.dev"
BOX_NAME = "centos/7"

Vagrant.configure(2) do |config|

  config.vm.synced_folder ".", "/vagrant", type: "virtualbox"
  config.vm.boot_timeout = 1200

  if Vagrant.has_plugin?("vagrant-proxyconf")
    config.proxy.http     = "http://192.168.100.3:3128/"
    config.proxy.https    = "https://192.168.100.3:3128/"
    config.proxy.no_proxy = "localhost,127.0.0.1,.some.lan"
  end

  config.vm.provider :virtualbox do |vb|
    vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
    vb.memory = 2048
    vb.cpus = 2
    vb.customize ["modifyvm", :id, "--cpuexecutioncap", "50"]
  end

  config.vm.define "nat" do |nat|
    nat.vm.box = BOX_NAME
    nat.vm.network "private_network", ip: "10.0.0.2", virtualbox__intnet: true
    nat.vm.hostname = "nat.staging." + BRAND_NAME + TOP_LEVEL_DOMAIN
    nat.vm.provision :hosts, :sync_hosts => true
    nat.vm.provision "shell", path: "./scripts/aws_replication.sh"
    nat.vm.provision "shell", path: "./scripts/nat_ssh.sh"
    nat.vm.provision "shell", path: "./scripts/nat_staging.sh"
    nat.vm.provision "shell", path: "./scripts/nat_git_clone.sh"
    nat.vm.provision "shell", path: "./scripts/nat_set_ansible.sh"
  end

  config.vm.define "fei" do |fei|
    fei.vm.box = BOX_NAME
    fei.vm.network "private_network", ip: "10.0.0.4", virtualbox__intnet: true
    fei.vm.network "forwarded_port", guest: 80, host: 80, auto_correct: true
    fei.vm.network "forwarded_port", guest: 443, host: 443, auto_correct: true
    fei.vm.network "forwarded_port", guest: 9000, host: 9000, auto_correct: true
    fei.vm.provision :hosts, :sync_hosts => true
    fei.vm.hostname = BRAND_NAME + ".staging" + TOP_LEVEL_DOMAIN
    fei.vm.provision "shell", path: "./scripts/aws_replication.sh"
    fei.vm.provision "shell", path: "./scripts/non-nat_key_staging.sh"
  end
end