5👍
✅
While the virtual machine is running, any changes to the Vagrantfile are not properly registered by the machine even if you run vagrant up
.
To ensure that all the changes get reflected correctly, the virtual machine should be halted and then run again.
In my case, I had changed the forwarding ports while the vagrant was running. I was doing vagrant up
assuming the changes will get reflected but they did not.
Doing vagrant halt
followed by vagrant up
solved my issue.
0👍
Make sure your port forwards are not auto corrected. If so, halt all the machines and remove the port forwarding cache by following:
rm -rf ~/.vagrant.d/data/fp-leases
Source:stackexchange.com