I don't develop very often, and things change and evolve occasionally at Bitbucket. So my configuration breaks. I want to push and pull from my local Linux and from my shared host Linus. In the big picture, I don't care how; I just want to do it the right way.
But at the moment I can push and pull from my local Linux but not from the shared host Linux. Both of them say this:
git config -l
user.email=t...m
user.name=Tom Haws
core.editor=nano
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=git@bitbucket.org:hawstom/engcalcs.git
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master
pull.rebase=false
branch.clipboard.remote=origin
The shared host fails like this:
1.
git pull
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
2.
ssh git@bitbucket.org host_key_info
Host key verification failed.
Again, I can push from my local Linux. What article do I need or steps do I need to do to get right with Bitbucket from the shared Linux host?
Tom
Hi Tom and welcome to the community!
We recently added two new host keys in Bitbucket Cloud, we rotated the RSA host key and removed the DSA host key.
Based on the error message, the machine where the pull fails may still be using our old RSA or the DSA host key to verify the authenticity of Bitbucket Cloud.
If you are using OpenSSH or a compatible client, you can check the steps in this blog post, in the section WHAT YOU NEED TO DO:
We also have the following FAQ page with questions and answers about some other SSH clients and commonly encountered issues:
Please feel free to reach out if you have any questions.
Kind regards,
Theodora
Very nice. Strangely, however, I had a completely different experience today than I did 4 days ago when trying this.
1. My shared Linux host logged me in to bash, which it was inexplicably failing to do four days ago.
2. As suggested at https://bitbucket.org/blog/ssh-host-key-changes, it "switched to the new host keys automatically".
There seems to have been a transient problem with my shell login for some reason. All's well that ends well. Have a very nice day.
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.