title: Deleted .vagrant directory prevents me from SSH
body: <p>I am using Vagrant to run 4 VMs. My Vagrantfile looks like this :</p>
  
  <pre><code>Vagrant.configure(2) do |config|
    config.vm.box = "bento/centos-7.2"
    config.vm.synced_folder "data", "/vagrant"
  
    # Master1
    config.vm.define :master1 do |m1|
      m1.vm.hostname = "master1.mycluster"
      m1.vm.network :private_network, ip: "192.168.0.12"
      m1.vm.provider :virtualbox do |vb|
        vb.memory = "8192"
      end
      m1.vm.network "forwarded_port", guest: 50070, host: 50070
    end
  
    # Other machines are defined in the same way
  end
  </code></pre>
  
  <p>Everything was working perfectly, until I accidentally removed the <code>.vagrant</code> folder from my project directory.</p>
  
  <p>First, I tried putting back my VMs ids into <code>.vagrant/machines/${name}/virtualbox/id</code>. Running <code>vagrant status</code> did see my VMs as up and running, but I couldn't connect via SSH anymore.</p>
  
  <p>I looked for a solution, but couldn't find one, so I decided to destroy and re-start my VMs. Sadly, the <code>vagrant up</code> (or <code>vagrant up --provision</code>) command got stuck trying to SSH to <strong>127.0.0.1:2222</strong>. Shouldn't it be trying to connect to <strong>192.168.0.12:2222</strong>, instead ? Here is the command output :</p>
  
  <pre><code>Bringing machine 'master1' up with 'virtualbox' provider...
  ==&gt; master1: Importing base box 'bento/centos-7.2'...
  ==&gt; master1: Matching MAC address for NAT networking...
  ==&gt; master1: Checking if box 'bento/centos-7.2' is up to date...
  ==&gt; master1: Setting the name of the VM: vagrant_master1_1493974030138_66977
  ==&gt; master1: Clearing any previously set network interfaces...
  ==&gt; master1: Preparing network interfaces based on configuration...
      master1: Adapter 1: nat
      master1: Adapter 2: hostonly
  ==&gt; master1: Forwarding ports...
      master1: 50070 (guest) =&gt; 50070 (host) (adapter 1)
      master1: 61888 (guest) =&gt; 61888 (host) (adapter 1)
      master1: 18080 (guest) =&gt; 18080 (host) (adapter 1)
      master1: 9995 (guest) =&gt; 9959 (host) (adapter 1)
      master1: 8787 (guest) =&gt; 8787 (host) (adapter 1)
      master1: 8088 (guest) =&gt; 8088 (host) (adapter 1)
      master1: 22 (guest) =&gt; 2222 (host) (adapter 1)
  ==&gt; master1: Running 'pre-boot' VM customizations...
  ==&gt; master1: Booting VM...
  ==&gt; master1: Waiting for machine to boot. This may take a few minutes...
      master1: SSH address: 127.0.0.1:2222
      master1: SSH username: vagrant
      master1: SSH auth method: private key
      master1: Warning: Remote connection disconnect. Retrying...
      master1: Warning: Authentication failure. Retrying...
  </code></pre>
  
  <p>Though, I can connect to my VM by doing <code>ssh -p 2222 vagrant@127.0.0.1</code>, and the SSH folder does not seem to have permission issues.</p>
  
  <pre><code>[vagrant@localhost ~]$ ls -la /home/vagrant/.ssh/
  total 4
  drwx------. 2 vagrant root     28  1 déc.  15:56 .
  drwx------. 3 vagrant vagrant  90  1 déc.  15:57 ..
  -rw-------. 1 vagrant root    409  1 déc.  15:56 authorized_keys
  </code></pre>
  
  <p>What can I do to be able to run VMs again, using Vagrant ?</p>