I use Vagrant 1.9.1 and boxes are config.vm.box = "centos/7". There seems to be private keys employed when calling „vagrant ssh“ to connect to a box. However, I’m not sure where are those keys located. Thanks a lot
Kind Regards
Diana
You can run vagrant ssh-config command, for example
fhenri#machine:~/project/vagrant/centos$ vagrant ssh-config app1
Host app1
HostName 127.0.0.1
User vagrant
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /Users/fhenri/.vagrant.d/insecure_private_key
IdentitiesOnly yes
LogLevel FATAL
It will give you the information of the ssh key used
Related
I am trying to copy a demo.zip from local host to a newly initiated vagrant VM.
I tried command like this from my MAC terminal:
scp -P 2200 demo.zip vagrant#127.0.0.1:/home/vagrant
However, I get:
vagrant#127.0.0.1: Permission denied (publickey).
lost connection
And below is the log from vagrant ssh-config:
Host default
HostName 127.0.0.1
User vagrant
Port 2200
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /Volumes/dailystorage/program_analysis_VM/.vagrant/machines/default/virtualbox/private_key
IdentitiesOnly yes
LogLevel FATAL
The version of vagrant box is ubuntu-xenial (Ubuntu 16.04.3).
Could anyone tell what's going on here and possible ways out?
Thanks!
UPDATE: Solved by installing vagrant scp.
The name localhost normally resolves to the IPv4 loopback address 127.0.0.1
So you can try copy file from your local machine to local machine.
Try this:
scp -i /Volumes/dailystorage/program_analysis_VM/.vagrant/machines/default/virtualbox/private_key demo.zip vagrant#private_ip_address_your_remote_machine:/home/vagrant
I regenerated the key and it worked:
Generate Key Pair on master-1 node $ssh-keygen
Leave all settings to default.
View the generated public key ID at:
$cat .ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQD......8+08b vagrant#master-1
Move public key of master to all other VMs
$cat >> ~/.ssh/authorized_keys <<EOF
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQD......8+08b vagrant#master-1
EOF
I installed the vagrant VM, but when i run:
vagrant ssh
it display an error of configuration:
command-line: line 0: Bad configuration option: IdentitiesOnly
I checked :
vagrant ssh-config
it display me:
C:\Vagrant\Ubuntu1>vagrant ssh-config
Host default
HostName 127.0.0.1
User vagrant
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile C:/Vagrant/Ubuntu1/.vagrant/machines/default/virtualbox/private_key
IdentitiesOnly yes
LogLevel FATAL
Can you tell me why, knowing that the first time i'm using vagrant.
IdentitiesOnly option is in OpenSSH since 2004 (OpenSSH 3.9). If you are using older version, you should certainly update.
Other possibility is to remove the colliding option, since it is not crucial to the functionality.
I'm trying to configure my first Vagrant box.
However it allows me to ssh onto it (with vagrant ssh) only the first time after vagrant up
But when I log out of the VM I can't log back onto it.
Doing Vagrant provision yields:
▶ vagrant provision
==> default: Running provisioner: shell...
SSH authentication failed! This is typically caused by the public/private
keypair for the SSH user not being properly set on the guest VM. Please
verify that the guest VM is setup with the proper public key, and that
the private key path for Vagrant is setup properly as well.
And trying to ssh into it yields:
▶ vagrant ssh
vagrant#127.0.0.1's password:
vagrant#127.0.0.1's password:
vagrant#127.0.0.1's password:
Permission denied (publickey,password).
Even if I give it the default password (vagrant) it rejects it and asks for it again 3 times.
When I start it in GUI mode, after writing any credentials whole console clears out and asks to log in again.
Tried destroying and rebuilding the VM, clearing project/.vagrant and ~/.vagrant.d.
Always the same result.
Adding config.ssh.insert_key = false to Vagrantfile changed nothing.
My box is ubuntu/trusty64 and my ssh-config looks like that:
▶ vagrant ssh-config
Host default
HostName 127.0.0.1
User vagrant
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /home/iraasta/.vagrant.d/insecure_private_key
IdentitiesOnly yes
LogLevel FATAL
Trying to ssh manually with ssh vagrant#127.0.0.1 -p 2222 and password vagrant also returns Permission Denied
I am running vagarant using chef. When I am running vagrant up. Its creating an instance after that its prompting for password. Actually it should login with ssh key
I have granted
chmod 0700 ~/.ssh/.ssh
chmod 0600 ~/.ssh/.ssh/authorized_keys
root#system-desktop:/home/system/Documents/dsrv169# vagrant --version
Vagrant 1.6.5
config.vm.provider :digital_ocean do |provider, override|
override.ssh.private_key_path = '~/.ssh/id_rsa'
override.vm.box = 'digital_ocean'
root#system-desktop:/home/system/Documents/dsrv168# vagrant ssh-config
Host default
HostName 45.55.239.147
User root
Port 22
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /root/.ssh/id_rsa
IdentitiesOnly yes
LogLevel FATAL
May I know what I required to do
it's just owner and group permission issue. After issuing chown it worked normally.
How can I make IP address for vagrant ssh the same as for the VM? What would I need to change/add to my manifest (Vagrant config files) ?
To explain my situation a little more: In my /etc/hosts file, I've setup local domains to map to the IP address of the VM as 192.168.56.105 - this is what is configured in the Vagrant setup, this works.
However vagrant ssh tries to connect to 127.0.0.1
Why would this be?
My vagrant ssh details are (when outputted to a file):
Host default
HostName 127.0.0.1
User vagrant
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /Users/rdavis/.vagrant.d/insecure_private_key
IdentitiesOnly yes
LogLevel FATAL
My specific problem had a root cause in port collision (with other VMs I'm using). Full credit to my colleague for spotting this.
Vagrant detects port collision but in your Vagrantfile config you have to do something about it i.e.
auto_correct: true
https://docs.vagrantup.com/v2/networking/forwarded_ports.html
This means that I can run more than one VM at a time without this issue.