Wagrant reports a port collision on which nothing works

I get a port collision in all ports of my Vagrantfile, which seems to be working fine for a while, and then suddenly something changes and it refuses to work. Please do not reply saying "change your port"

Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 3100 is already in use
on the host machine.

To fix this, modify your current project Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:

  config.vm.network :forwarded_port, guest: 1337, host: 1234

I did everything I could to find the problem, but at the same time it puzzled me.

lsof -n -i4TCP:3100

Prints nothing

I am running vagrant 1.9.2 with vagrant-vmware-fusion (4.0.18)

+4
source share
1 answer

Well, I think I hacked it. This seems to be related to this issue.

https://github.com/mitchellh/vagrant/issues/7948

vagrant-vmware-plugin nat.conf . - , , .

/Library//VMware Fusion/vmnet8/nat.conf [incomingtcp], , .

, , .

8.5.3 vagrant-vmware-fusion 4.0.18.

+4

Source: https://habr.com/ru/post/1673009/


All Articles