Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Ethan Moffat
3,223 PointsVagrant SSH issues.
As from the title I am having issues with my current Vagrant SSH. Whenever I try to type the command "vagrant ssh" it gives me a error and doesn't connect me to the treehouse VM. I also get the following error when I try booting up the VM via "vagrant up" Warning: Connection timeout. Retrying...
That error above spams constantly. I am using Windows 10, I think it isn't supporting Vagrant or it could be Virtual Machine. I will keep updates on my situation unless one of you have a idea that could resolve it. Please respond to me as soon as possible, thank you!
I cannot show the vagrant SSH error because the booting up error spams and won't proceed.
Ethan Moffat
3,223 PointsI believe I downloaded the wrong version. I need to download the one that comes with SSH client.
Ethan Moffat
3,223 PointsI have been trying for awhile to resolve my issue but still the same thing. I am now coming into thinking switching to Linux or buying a Mac OS however, I would prefer not to.
2 Answers
JoJo KoKo
4,712 PointsCurrent version of Vagrant doesn't work with Windows 10 when you try to set private network. Here is a thread on github : https://github.com/mitchellh/vagrant/issues/6068
Ethan Moffat
3,223 PointsThank you JoJo, I am downloading a newer devlopment build to try and see if it will help with the issue.
Ethan Moffat
3,223 PointsEthan Moffat
3,223 PointsQuick update this just happned. 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, as well.
If the box appears to be booting properly, you may want to increase the timeout ("config.vm.boot_timeout") value.