what about permissions? from the console as your user try
chown -R vagrant: ~/.ssh chmod -R 0600 ~/.ssh chmod 0700 ~/.ssh first command set owner second set all file and dir as RW third (no -R) set dir to RWX then you can try vagrant ssh On Sun, Oct 1, 2017 at 1:56 AM, 'Paul Baxter' via Vagrant < [email protected]> wrote: > Having problems with connecting to my VM and possibly initial insecure key > ssh exchange for my first box. > > Can ping the VM from host but not SSH. > > VM (centos/7) is created and I can log in via hyperv console but not via > ssh. > > Anyone point me to recent documentation that is pertinent to setting up > the ssh, or the hyper v network > > (e.g. I've seen some web blogs suggest you must run vagrant as an > administrator in powershell) > I've tried both as <user> and run as admin but no real difference. Both > seem to create and start the VM and neither let me ssh in! > > > I followed https://followkman.com/2016/07/27/vagrant-up-on- > windows-10-with-hyper-v/amp/ with some fixes > > my <user> .ssh dir has > vagrant insecure public key (from github.. hashicorp/keys/vagrant.pub) > copied as <user>\.ssh\authorized_keys > Also locally generated a public/private key using ssh-keygen > Files are <user>\.ssh\rsa_id and rsa_id.pub > Overwrote <user>\.vagrant.d\insecure_private_key with the contents of my > rsa_id (private key) > > Using openssh v7.5p1 (latest) or putty > > Getting a connection refused with ssh or putty but don't know why and how > to debug this. > > > Other info: > > hyperV external switch shared with the host win 10 pro machine > ipconfig on host reports the vExternal switch IP as 192.168.1.X > Connecting into the VM via hyper V with password. ip a also shows eth0 > with IP 192.168.1.X (same IP as virtual switch) - expected? > > Tried changing the VM machine to use a legacy network adapter instead. No > difference. > > Initial trials were unsuccessful. However in the middle of trying lots of > things, I did have this working earlier, but having destroyed the VM and > recreated I have failed to repeat the success. > > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > 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]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/c6c1348f-d1ee-4f7f-a29b-7f2b08b7bbba%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/c6c1348f-d1ee-4f7f-a29b-7f2b08b7bbba%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey09X41T-6J6ae-guBO1F6nctuBQE6fcRDS2pxhPazGPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
