# First time using trellis and stuck in vagrant up: Getting "Warning: Connection timeout. Retrying..." **URL:** https://discourse.roots.io/t/first-time-using-trellis-and-stuck-in-vagrant-up-getting-warning-connection-timeout-retrying/6202 **Category:** trellis **Created:** 2016-03-14T17:08:22Z **Posts:** 11 ## Post 1 by @juanmaguitar — 2016-03-14T17:08:23Z Hi! I’d really like to start using Trellis for my wordpress developments but i’m stuck on the “vagrant up” ![](https://discourse.roots.io/uploads/default/original/2X/9/961fa249d6bb64107c2a9b5690d0c0a925289c77.png) My environment is - Mac OS X “El Capitan” 10.11.3 - Ansible 2.0.1.0 - Vagrant 1.8.1 - Virtual Box 5.0.16 r105871 and my vagrant plugins are: - vagrant-bindfs (0.4.6) - vagrant-hostmanager (1.8.1) - vagrant-share (1.1.5, system) - vagrant-triggers (0.5.2) - vagrant-vbguest (0.11.0) ![](https://discourse.roots.io/uploads/default/original/2X/b/b63583fbee2d316a0d141df7da7a02d385a5c542.png) 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? Thanks in advance!! - JuanMa --- ## Post 2 by @ben — 2016-03-14T17:13:17Z Have you looked through these threads? > [@Timed out while waiting for the machine to boot](https://discourse.roots.io/t/timed-out-while-waiting-for-the-machine-to-boot/5943): > > After a VirtualBox update, I can’t up vagrant box. ==\> 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: Warning: Connection timeout. Retrying... default: Warning: Connection timeout. Retrying... default: Warning: Connection timeout. Retrying... How can be fixed? Thank you! [https://discourse.roots.io/t/warning-connection-timeout-only-on-certain-networks/6161](https://discourse.roots.io/t/warning-connection-timeout-only-on-certain-networks/6161) --- ## Post 3 by @juanmaguitar — 2016-03-15T08:20:46Z Hi benword! 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”? Cheers!! - JuanMa --- ## Post 4 by @juanmaguitar — 2016-03-15T10:07:36Z Here you have the details about what i’m saying [https://gist.github.com/juanmaguitar/2e08d9953a232b91634a](https://gist.github.com/juanmaguitar/2e08d9953a232b91634a) --- ## Post 5 by @Twansparant — 2016-03-15T10:51:32Z Did you try setting the **vb.gui** in your virtualbox settings in your Vagrantfile and see if something comes up in there? ``` # Virtualbox settings config.vm.provider 'virtualbox' do |vb| # for debugging set vb.gui to true vb.gui = true vb.name = config.vm.hostname vb.customize ['modifyvm', :id, '--cpus', cpus] vb.customize ['modifyvm', :id, '--memory', memory] # Fix for slow external network connections vb.customize ['modifyvm', :id, '--natdnshostresolver1', 'on'] vb.customize ['modifyvm', :id, '--natdnsproxy1', 'on'] end ``` --- ## Post 6 by @juanmaguitar — 2016-03-15T13:00:26Z Hi Twansparant! 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. Any other clue i can use the “vb.gui = true” for? Thanks! - JuanMa --- ## Post 7 by @aitor — 2016-03-15T15:11:25Z > [@juanmaguitar](#): > > 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. 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. sorry I can not help more! --- ## Post 8 by @aitor — 2016-03-15T15:14:04Z I forget to mention. If this problem is the same, Vagrant Box should start with wifi deactivated. Maybe you can try it. --- ## Post 9 by @juanmaguitar — 2016-03-15T16:42:58Z Hi aitor!! Here there are the logs from the `vagrant up` and the `boot.log` inside the VM [https://gist.github.com/juanmaguitar/d1a4f15bf0050598527c](https://gist.github.com/juanmaguitar/d1a4f15bf0050598527c) [https://gist.github.com/juanmaguitar/c7f37d0bd08dd870cd39](https://gist.github.com/juanmaguitar/c7f37d0bd08dd870cd39) Don’t understand what’s going on here. The IP assigned to the VM seems to be 10.0.2.15 but the VM is only responding to 127.0.0.1 Hope these logs can help you (or someone else more DevOps than me) understand what the problem really Thanks in advance - JuanMa --- ## Post 10 by @aitor — 2016-03-15T16:54:52Z I mean, check the router to see what IP is assigned. It must be 192.168.50.5 by default. Also, did you try to shut down the wifi before vagrant up? (assuming you are wifi connected to router) --- ## Post 11 by @juanmaguitar — 2016-05-03T11:04:14Z It seems that changing DNS server settings and [using some of the popular ones](http://www.computerworlduk.com/security/best-6-free-dns-services-2016-boost-internet-performance-security-3632790/) solves this issue ![](https://discourse.roots.io/uploads/default/original/2X/c/c5ff2882e79b6c0b77440ff495c6e4212584548a.png) 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...` !! :slight_smile: