I’ve really tried lots of things found on stack-overflow and other sources but nothing seems to work. I’m getting very frustrated with this. Any ideas?
Yes, i’ve reviewed these threads and i can’t see a clear solution on them.
Both threads seems to be relationed with router issues. Don’t think is my case as i can use other virtual machines (through vagrant) in these IP’s.
If i change the box to “precise64” the “Connection timeout” is solved by itself but the process is broken some steps after. I suppose the trellis “tasks” (vagrant, ansible, composer) are customized to work only with “trusty64”
Is there any “version” of Trellis working with “precise64”?
Yes, i’ve also tried that but the only thing that happens is that i can see the whole boot process through the virtual box windows and at the end i’m asked the login/password to log into the system
With the default vagrant/vagrant i can log into the machine but no synced folder or any other trellis process/service has been installed/loaded in the machine.
Seems to be the same problem. A specific vagrant box with a specific network does not work. You can start a Vagrant Box, but no others. Have do you checked what IP is assigned to your VM? If there is no IP assigned, the problem will be the same. I think there is no problem related to Ubuntu version, most likely is related to DHCP. I’m not sure, of course.
The bad new is that we can not found a solution for this problem yet. And, since it is a very difficult to replicate, due to its specific conditions, other people cant research over it. For me was a nightmare.
I haven’t tested this solution deeply but after doing this change…
...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
...
it works as is suposed to
No more default: Warning: Connection timeout. Retrying... !!
