Last time this happened it turned out that the VPN I was on was blocking all 10.* addresses - in case you didnt realize, Vagrant assigns 10.* address by default. So simply changing the network IP address in Vagrantfile solved the problem.
Solution to internal network blocking 10.* addresses:
config.vm.network :public_network, ip: "220.127.116.11"
Well, something happened and everything stopped working again (I am a consultant for a company, so perhaps something got locked down just for contingent staff, because all of the FTEs can work just fine with default config).
Solution is to allow VPN passthrough in Vagrantfile:
... config.vm.network :private_network, ip: "18.104.22.168" ... config.vm.provider :virtualbox do |p| p.gui = true p.customize ["modifyvm", :id, "--memory", "1500", "--clipboard", "bidirectional", "--natdnshostresolver1", "on"] end
* shamelessly stolen from a random (but very useful) site I found after banging my head against a keyboard failed to produce the desired outcome. (source: http://akrabat.com/computing/sharing-host-vpn-with-vagrant (I even kept the pretty code background)).
Random yet very accurate and completely unrelated funny