Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured (“config.vm.boot_timeout” value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you’re using a custom box, make sure that networking is properly
working and you’re able to connect to the machine. It is a common
problem that networking isn’t setup properly in these boxes.
Verify that authentication configurations are also setup properly,
If the box appears to be booting properly, you may want to increase
the timeout (“config.vm.boot_timeout”) value.
If I open VitualBox after time out I can see the virtual machine ansible_default open.
Try changing the IP address of the VM. That’s in your Vagrantfile, line 39. It doesn’t have to be 192.168.50.x. It can be anything in the ipv4 private address space. If that doesn’t fix it, it could be a software firewall on your computer.
Sounds like you’ve tried a lot. I’m sure it is frustrating. I’m not aware of what this might be. Googling ‘vagrant virtualbox update "Connection timeout"’ turned up quite a variety of causes and resolutions. Perhaps you’ve looked through those results, e.g., this and this for starters.
Yesterday a friend of mine, telecommunication engineer, came home to help me with the router. We checked net cards of virtual machines for six o seven hours and how dhcp was assign IP. Finally he decided that new router was defective. I am returning it to Amazon.