title: Why is connection refused by Vagrant box in Windows 10?
body: <p>I've been having problems with Vagrant since upgrading to Windows 10. At first I had the <a href="https://github.com/mitchellh/vagrant/issues/6068" rel="nofollow">"host-only adapter" problem</a> that many people seem to be experiencing. This was fixed by updating VirtualBox to the latest version, and my Vagrant box now seems to provision and start ok, and I can SSH into it, but can't connect via HTTP. If I try to access it from a browser, I get "Unable to connect". If I try <code>curl</code>ing it, I get the message:</p>
  
  <pre><code>Failed to connect to test.dev port 80: Connection refused
  </code></pre>
  
  <p>I've checked and Apache seems to be running on the VM (and in fact if I SSH into the VM and then run <code>curl 127.0.0.1</code> the expected homepage is returned). At this point I've drawn a blank: I don't know whether the problem is in Windows or the VM's settings. Any help would be greatly appreciated!</p>
  
  <p>(For what it's worth, I'm using VirtualBox 5.0.15r105158 + Vagrant 1.8.1)</p>
  
  <p><strong>Update</strong>: it turns out that the VM <em>is</em> accessible from <code>test.dev:8888</code> in the browser, so I'm guessing the problem is to do with port-forwarding? I don't know much about this though, so have no idea why this wouldn't be working in Windows 10. (In case it helps, my Vagrantfile contains the line <code>config.vm.network :forwarded_port, guest: 80, host: 8888</code>)</p>