title: VirtualBox guest not getting ip address assigned by Vagrantfile
body: <p>Upon vagrant up, the guest box is getting assigned the wrong IP address and causing the following error:</p>
  
  <pre><code>...
  ...
  SSH address: 127.0.0.1:2222
  serverbox: SSH username: vagrant
  serverbox: SSH auth method: private key
  serverbox: Warning: Connection timeout. Retrying...
  serverbox: Warning: Connection timeout. Retrying...
  serverbox: Warning: Connection timeout. Retrying...
  ...
  </code></pre>
  
  <p>I do work at home and at the office so must always reconfigure the ip address assignment in Vagrantfile depending on where I am at because the subnets are different. (192.168.x.x versus 10.80.x.x)</p>
  
  <p>This has worked fine until just yesterday. I have no idea what is causing the issues as I haven't made any adjustments.</p>
  
  <p>Vagrantfile:</p>
  
  <pre><code>Vagrant.configure("2") do |config|                                                                                                                       
    config.vm.provider "virtualbox" do |vb|                                                                                                                
      vb.customize ["modifyvm", :id, "--memory", "512"]                                                                                                    
    end                                                                                                                                                    
    config.vm.network "public_network", ip: '10.80.2.144'
    #config.vm.network "public_netowrk", ip: '192.168.1.144'                                                                                        
  end
  
  ...
  </code></pre>
  
  <p>The Vagrantfile should put my guestbox on the 10.80.x.x address but netstat shows that my box is still going up on the 192.168.x.x address. This means I am unable to work with the guestbox since it is going to an out of bounds subnet.</p>
  
  <p>I've done halt and up again as well as completely rebooting my cpu and checking to make sure virtualization is on in BIOS.</p>
  
  <p>I've looked <a href="https://stackoverflow.com/questions/24583827/vagrant-box-default-warning-connection-timeout-retrying?rq=1">here</a> and tried <a href="https://stackoverflow.com/questions/22575261/vagrant-stuck-connection-timeout-retrying#answer-23095019">this</a> method to no avail.</p>
  
  <p>I also tried vb.gui = true but my machine is running headless. Virtualbox's Preview logging screen might provide some useful information but it is so small I can't make anything out of it. If someone has any advice on how to make that larger that could probably help a lot.</p>
  
  <p>UPDATE:</p>
  
  <p>So my solution is an undesired solution but my workday has been torpedoed and need to move forward so I just destroyed my box and re up'ed.</p>
  
  <p>Apparently, my keys became insecure. Not sure how that happened but the new box replaced my keys.</p>