Open nextgenthemes opened 2 years ago
I have this same problem, on macOS Monterey VirtualBox 6.1.30 Vagrant 2.2.17
And again this problem: macOS BigSur 11.6.4 VirtualBox 6.1.34 Vagrant 2.2.19
Hi I was able to get mine up and running, turned out the problem was with Cloudflare Warp https://www.reddit.com/r/CloudFlare/comments/oxvrz1/warp_breaks_localhost_on_a_mac/
Hi. Thank you for your advice. I hope it will be helpful for someone. I had different problem - with firewall. I needed to allow incoming connections. It looks like some settings have been reset to defaults after system update (System Preferences -> Security & Priviacy -> Firewall). I rebooted the laptop in this morning. Some people hate windows for their update policy and what I see... :)
This really is getting annoying. This and similar issues go back to 2015 or even b4, I have seen this happening on all OSes in different variations. This seems to be a total mess and it not getting better. I already spent many hours of tine trying to fix this and the last thing I remembered I did was adding
mount_options: ["vers=4,tcp"]
to my Vagrantfile and I think this was what fixed it, I have added and tried many other things. The VAST amount of issues around this and solutions are crazy, ranging from adding rules to firewalls ... all kinds of things. I had the same issue b4 with a different solution I think.Can this he solved ONCE AND FOR ALL? Maybe? How about building in some tests in the actual exaction of Vagrant? Like going down the list of fixes and solutions and checking if they are applied to the system, like firewall rules of whatever. And if system needs and supports version 4 use it with TCP by default? From what I remember, in THEORY version 3 should still work on the latest cutting-edge stuff Tumbleweed ships with, but for me that is what fixed it I think - until now.
How about putting out some actual helpful error messages like the "if vagrant was recently updated, do this". That I have to run after every update, it's annoying, but at least it points me to the solution that actually works.
I noticed this
mount -o vers=3,udp,vers=4,tcp 192.168.50.1:/u/w/n.com /vagrant-nfs-n.com
it seems the options get put at the end, but there are also the WRONG options on the beginning of the command. My guess is that mount uses the options that come first. So my custom options are not used anymore since last version. That is my guess is what happens.Vagrant version
Vagrant 2.2.18
Host operating system
Open SUSE Tumbleweed
Guest operating system
Ubuntu 20.10
Vagrantfile
Debug output
Expected behavior
Just work, or at least put out error messages about what to do.
Actual behavior
Timeout AGAIN.
Steps to reproduce
References
Countless issues about this for many many years, more or less arround the same issue(s), even saw one on Windows 10 today about something related.