title: vagrant up: config.ssh.timeout
body: <p>I do not understand why I cannot "vagrant up" anymore after I run some provisioning scripts (I use ansible).</p>
  
  <pre><code>[default] Waiting for machine to boot. This may take a few minutes...
  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.ssh.timeout" value) time period. This can
  mean a number of things.
  
  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.ssh.timeout") value.
  </code></pre>
  
  <p>What can be broken? What is vagrant trying to do when running vagrant up?
  Connecting with the default user, i.e. "vagrant" ?</p>
  
  <p>Obviously it is related to SSH.
  Yes I pushed some SSH keys but I do not think I changed the vagrant user at all so "vagrant up" should still work right? I also changed a little bit the /etc/sudoers file but I tried without modifying it and it does not seem to work anyway...</p>
  
  <p>Well, I am running out of ideas..
  Thanks.</p>