Proxifier prevents Vagrant from binding port

[ColdZoo]

Environment
Vagrant 2.2.9
VirtualBox 6.1.10 r138449 (Qt5.6.3)
Maven home: 3.6.3_1
Java version: 13.0.2(openjdk)
OS name: "mac os x", version: "10.15.5", arch: "x86_64", family: "mac"
Proxifier: v2.26

When executing mvn install with Proxifier running, the mvn complaints that the port '27017' is
bound to another process. However, netstat -ntlp | grep 27017 indicates that nobody is listening on it.

To make things even stranger, after changing the port 27017 to 27018, which is also available, in VagrantFile, mvn insists that 27018 is now the conflicting port. mvn install then fails at the 'vm' module.

After some research, I have come to realize that it is the Proxifier who prevent Vagrant from binding port. So, if you are using Proxifier and have encountered the same problem as me, the procedure to build VM is as follows:

1. quit Proxifier
2. cd vm && vagrant destroy this will remove the VM built by previous attempts.
3. wait until the port has bound
4. start Proxifier (for we need download packages after VM's start)