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

Development Tools Installing a Ruby Development Environment Installing a Ruby Development Environment Installing the Treehouse VM on Mac

Posted by Justin Gaba
Justin Gaba
3,311 Points

When I type "vagrant up" I get an authentication error.

Update: Apologies for the duplicate post . Originally I didn't realize I had an authentication error and didn't know that I should type 'vagrant halt' and try 'vagrant up' again.

Update2: I have now resolved the issue I had

new-host-3:treehouse justingaba$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> 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: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
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.```

4 Answers

Justin Gaba
Justin Gaba
3,311 Points

Hey Andrew Stanley, I fixed the problem I was having by taking the steps below

  1. Typed 'vagrant ssh-config' in the console
  2. Made sure to halt by typing 'vagrant halt'
  3. Then deleted my treehouse directory and extracted the contents of this file Link from video
  4. Then typed 'vagrant up' followed by vagrant ssh' and it worked
Andrew Stanley
Andrew Stanley
11,392 Points
Andrew Stanley
Andrew Stanley
11,392 Points

Are you in the virtual machine on your own computer?

I had trouble with the vagrant command when installing Ruby on Rails to the VM so I just decided to install it locally. If you are working locally just type in your password that you use to access your machine and you should be go to go. Hope this helps.

A.

Andrew Stanley
Andrew Stanley
11,392 Points
Andrew Stanley
Andrew Stanley
11,392 Points

Alrighty so I was able to download vagrant, install Virtual Box and get it up and running. When I ran the script it never asked me for a password but when I went back and looked it stated that there was a 'private key' in the virtualbox installer.

Try uninstalling the virtualbox application and install it again to see if that fixes the issue. Let me know if this helps.

A.

Andrew Stanley
Andrew Stanley
11,392 Points
Andrew Stanley
Andrew Stanley
11,392 Points

Well done and good luck Justin Gaba!

Justin Gaba
Justin Gaba
3,311 Points

Thanks :) Good Luck as well Andrew Stanley