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!
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

geoffrey
28,736 PointsVagrant keeps timing out - as well for me.... [SOLVED]
I'm desperately looking for a solution to start the laravel course, and even more to install Laravel with Vagrant.
As the title says, I have all the time that warning : Connection Timeout retrying when running the command vagrant up.
I've been browsing the web to search for a solution for hours now. But I've found nothing hence my post here, I hope someone or Hampton Paulk. Does the private key needs to be the same as my own system ?
I've checked and these ones are differents, I tested to copy/past my own key, but doesn't work neither.
Here is another screen of my Homestead.yaml:
http://geoffreyorban.be/homestead.png
Sorry for the long post, but I try give all the information.

Hampton Paulk
5,093 PointsGlad you found it! Can you please move your comment with your solution to an answer, so I might mark it as best answer for the other students out there that might be beating their heads on the desk?
2 Answers

geoffrey
28,736 PointsI've finally after some hours spent to solve it, found the solution. VT technology was indeed disabled inside my bios. I read my mother board manual, and It seems this option was inside the overclocking tab of the BIOS, oddly !
All of this for "nothing", but at least my prob is solved ! Sorry guys.

Hampton Paulk
5,093 PointsThanks for adding this as an answer! It will surely help other students!

Tom Mertz
15,254 PointsThanks for posting this! You saved me hours of headache. It only took me 20 minutes to finally wise up and search the forums, haha.

Alan Johnson
7,625 PointsGlad you figured this out, Geoffrey!
geoffrey
28,736 Pointsgeoffrey
28,736 PointsI've finally after some hours spent to solve it, found the solution. VT technology was indeed disabled inside my bios. I read my mother board manual, and It seems this option was inside the overclocking tab of the BIOS, oddly !
All of this for "nothing", but at least my prob is solved ! Sorry guys.