Okay, I’ve look around and I know I’m missing what I need to do.
I have a site and it’s been deployed and works great. My issue is when I vagrant ssh I can’t run composer update because it wont connect to bitbucket. I can run vagrant provision without error, but it is not trying to read a remote repo…
So for this is what’s happened.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for bitbucket.org has changed,
and the key for the corresponding IP address 18.205.93.2
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
Offending RSA key in /home/vagrant/.ssh/known_hosts:4
remove with:
ssh-keygen -f “/home/vagrant/.ssh/known_hosts” -R bitbucket.org
I then tested my ssh from vagrant with ssh -T git@github.com
I then got an error: Permission denied (publickey).
So I tried removing known_hosts: ssh-keygen -f “/home/vagrant/.ssh/known_hosts” -R bitbucket.org
Now when I run composer update I get: Connection to bitbucket.org closed by remote host.
fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists
I can run “composer update” off my local machine fine, so I have the proper keys, it’s just not forwarding.
In my ssh config file what do I need to put for vagrant?
Reading the remote repo works properly for deploy production…