Now that you have overcome all the troubles, will you share the instructions?
:) On Tue, Apr 8, 2014 at 2:52 PM, Brien Givens <[email protected]> wrote: > Demitri... thanks again for your help... my box is up and running now. > > On Monday, April 7, 2014 5:47:14 PM UTC-7, Demitri Swan wrote: >> >> Renaming the user account is never really a good idea. You might have >> changed the Full Name and not the shortname (which is the name that Darwin >> and CLI software actually cares about). You can verify this with the dscl >> command. Anyway, just starting over with the new user account will likely >> fix your problem. >> >> Good luck. >> >> >> On Mon, Apr 7, 2014 at 4:35 PM, Brien Givens <[email protected]> wrote: >> >>> I think I've zeroed in on the problem. When I created the base box, I >>> named my User Account 'admin'. Later on, I read about the need for a >>> 'vagrant' User Account, so I just renamed my 'admin' account to 'vagrant'. >>> >>> I'm in the process of recreating my base box. Hopefully, everything will >>> go smoothly this time. >>> >>> Thanks a mil for your help! This was ridiculous to sort out. >>> >>> >>> On Monday, April 7, 2014 4:02:30 PM UTC-7, [email protected] wrote: >>>> >>>> Additionally, from the looks of your output, it looks like your SSHing >>>> into the admin account, NOT the vagrant user. The keys provided by Vagrant >>>> are intended for a user named vagrant, not admin. Make sure you have a >>>> vagrant user on the guest machine and give it admin privileges. >>>> >>>> Otherwise, you can generate your own SSH keys... >>>> >>>> >>>> >>>> On Monday, April 7, 2014 3:53:35 PM UTC-7, [email protected] wrote: >>>>> >>>>> If you had to type in your password, then your keys did not work. If >>>>> your SSH keys don't work, vagrant ssh will not work. Some things to >>>>> check/try: >>>>> >>>>> - > ~/.ssh/known_hosts # (Execute this on your host system. >>>>> Standard SSH troubleshooting) >>>>> - Try loosening up your permissions on your ssh directories and >>>>> files completely in the guest machine. For example, chmod -R 0777 >>>>> ~/.ssh. >>>>> After doing this, try SSHing into the guest as described previously. >>>>> If you >>>>> don't get asked for your password, then your keys are working and the >>>>> permissions you had previously were too strict. After you get it >>>>> working >>>>> though, you may want to tighten them up a bit >>>>> - Make sure that the vagrant user in the guest system owns the >>>>> ~/.ssh directory for the vagrant user. >>>>> - Double check and make sure that the ~/.ssh/authorized_keys file >>>>> on the guest contains the string exactly as is in the public key >>>>> provided >>>>> by the folks at Vagrant. If there is a typo here, the key won't work >>>>> >>>>> >>>>> On Monday, April 7, 2014 3:33:55 PM UTC-7, Brien Givens wrote: >>>>>> >>>>>> That worked instantly. This is the output: >>>>>> >>>>>> Guests-MacBook-Pro:vagrant-base-dev briengivens$ ssh -p 2222 -i >>>>>> ~/.vagrant.d/insecure_private_key vagrant@localhost >>>>>> The authenticity of host '[localhost]:2222 ([127.0.0.1]:2222)' can't >>>>>> be established. >>>>>> RSA key fingerprint is (removed). >>>>>> Are you sure you want to continue connecting (yes/no)? yes >>>>>> Warning: Permanently added '[localhost]:2222' (RSA) to the list of >>>>>> known hosts. >>>>>> Password: >>>>>> Last login: Mon Apr 7 11:34:45 2014 >>>>>> Dev-Box:~ admin$ >>>>>> >>>>>> On Monday, April 7, 2014 3:23:58 PM UTC-7, [email protected] wrote: >>>>>>> >>>>>>> Try the following: >>>>>>> >>>>>>> ssh -p 2222 -i ~/.vagrant.d/insecure_private_key vagrant@localhost >>>>>>> >>>>>>> The -p flag allows you to specify the port. The -i flag allows you >>>>>>> to specify the path to the private key that is provided with your >>>>>>> vagrant >>>>>>> installation. vagrant@localhost is the general method of connecting >>>>>>> to remote ssh nodes, with vagrant being the user and localhost being the >>>>>>> host to which you intend to connect. Since vagrant does SSH through NAT >>>>>>> on >>>>>>> the localhost, we use localhost here. >>>>>>> >>>>>>> If this fails, then my guess is that something is wrong with your >>>>>>> ssh keys. If it does not fail, but instead just takes a long time to >>>>>>> authenticate, then my guess is that UseDNS in sshd_config on the guest >>>>>>> is >>>>>>> set to yes. If you set this to no, then you can sometimes reduce the >>>>>>> time >>>>>>> it takes to SSH into the guest system. >>>>>>> >>>>>>> >>>>>>> On Monday, April 7, 2014 3:02:54 PM UTC-7, Brien Givens wrote: >>>>>>>> >>>>>>>> password... how do I use the private key? >>>>>>>> >>>>>>>> On Monday, April 7, 2014 2:39:33 PM UTC-7, [email protected]: >>>>>>>>> >>>>>>>>> When you SSH in manually, are you using your private key or are >>>>>>>>> you using your password? >>>>>>>>> >>>>>>>>> >>>>>>>>> On Monday, April 7, 2014 2:21:49 PM UTC-7, Brien Givens wrote: >>>>>>>>>> >>>>>>>>>> I'm having similar problems with a similar setup >>>>>>>>>> >>>>>>>>>> http://stackoverflow.com/questions/22922891/vagrant-ssh- >>>>>>>>>> authentication-failure<http://www.google.com/url?q=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F22922891%2Fvagrant-ssh-authentication-failure&sa=D&sntz=1&usg=AFQjCNG49fdFq3pbL9LOfSXiRfYzzhnXqw> >>>>>>>>>> >>>>>>>>>> I followed demit's suggestions but the problem persists. >>>>>>>>>> >>>>>>>>>> @Alexey - I assume 'up' means you got yours running? What finally >>>>>>>>>> got it working for you? >>>>>>>>>> >>>>>>>>>> @demit - any other tips? >>>>>>>>>> >>>>>>>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Vagrant" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>> topic/vagrant-up/HKL0FXR6QmE/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
