Hi Jeff, I cleaned out the nat.json file and restarted my machine. I'm still seeing the port collision issue. Here's the debug gist: https://gist.github.com/weshoke/3208260f3933b3ea4afb9374298499b7. Any ideas? thanks, wes
On Friday, April 24, 2020 at 8:55:14 AM UTC-7, Jeff Bonhag wrote: > > Hi there, > > Is port 2222 in use by some other process? > > Are there any entries listed in the settings file? This is located at > /opt/vagrant-vmware-desktop/settings/nat.json. If so, remove them (or just > delete the file and let it be recreated) and restart the > vagrant-vmware-utility with launchctl. > > If you are still encountering collisions, can you please open a new GitHub > issue with a debug gist of a 'vagrant up --debug'. The extra logging that's > been added will hopefully help determine what's causing this state. > > Thanks! > > On Thu, Apr 23, 2020 at 3:41 AM Wes Smith <w...@plethora.com <javascript:>> > wrote: > >> vagrant up --provision >> Bringing machine 'default' up with 'vmware_fusion' provider... >> ==> default: Checking if box 'generic/debian10' version '2.0.6' is up to >> date... >> ==> default: Verifying vmnet devices are healthy... >> ==> default: Preparing network adapters... >> ==> default: Starting the VMware VM... >> ==> default: Waiting for the VM to receive an address... >> Some of the defined forwarded ports would collide with existing >> forwarded ports on VMware network devices. This can be due to >> existing Vagrant-managed VMware machines, or due to manually >> configured port forwarding with VMware. Please fix the following >> port collisions and try again: >> >> >> 2222 >> >> >> This keeps happening. I'm editing /Library/Preferences/VMware\ >> Fusion/vmnet8/nat.conf to clean any ports before running vagrant up, but >> nothing's working. >> >> >> Vagrant 2.2.7 >> vmrun version 1.17.0 build-13668589 >> >> Any ideas? I'm at wits end here. >> >> I've tried to delete the VM, clean the settings, restart the host >> machine. Nothing's working here. >> >> thanks! >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to vagra...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/3abe3112-be73-4884-ab77-c70d2c61c0fe%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/3abe3112-be73-4884-ab77-c70d2c61c0fe%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c93fb0e8-e292-4891-bc6f-d2cc35c8cdec%40googlegroups.com.
