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
Adam Kelm
29,082 PointsTreehouse VM not connecting
When I try running the Treehouse VM for AR Basics, I keep getting this startup sequence with the error message until it eventually fails:
Ī» vagrant reload
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 3000 => 3000 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: treehouse
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
I haven't changed anything since successfully using this VM a few days ago, so I think the issue may be on the server side. Has anyone else had this problem, or know how to solve it?
1 Answer
Michael Hulet
47,913 PointsThere is no server side. What's happening is the Treehouse VM isn't starting up. Try running vagrant up
Adam Kelm
29,082 PointsAdam Kelm
29,082 Points"Vagrant reload" is the same command as "vagrant up" with the additional step of assuring it's shut down properly. That was the first command, before I tried the reload.