I found alot of topics like this but still can't figure out where my exact Problem is.
I already had git set up and running fine but for a while now pushing to my repo is not possible anymore. The Credentials window pops up, I enter my credentials and it comes up agian.
When looking up the response in the network-Tab I can see a 400 with this Message:
For me it is working with a token. The github password doesn't work. But, if you create a token on github, it does...
On github, when authenticated, go to settings -> Developper settings (last in the menu on the left). Create a token. Use it
Unfortunatelly I am using bitbucket - and Bitbucket does not support Tokens.
Okay, after digging deeper into the whole thing I connected to the console and fired git from there. Got the same error. So I setup rsa-key verification for the repo and now I was able to push/pull from the console. (Also changed the url of the repo from https to ssh.)
Pushing and pulling from the console works fine now. But I still receive an error message in node-red.
It says:
"Der Repository Host-SchlĂĽssel konnte nicht verifiziert werden. Bitte aktualisieren Sie Ihre known_hosts -Datei und versuchen Sie es erneut."
-> Host key verification can not be done. As I do not receive this error message on the console I think it has something to do with the executing user. Any hints how to solve that?
I guess it depends how you have deployed NodeRed. If you have created a specific user or if you run in docker the ssh keys won't be the same as the ones in the console.
Yeah, that helped somehow.
I already ssh-ed directly via console to bitbucket.org but that only inserted the key to the known_hosts file of the user "pi".
su-ing to the User iobroker is not possible on my system. I already tried adding the key on that way too. What finally worked was: Searching all "known_hosts" files on the System. The user iobroker has one in its home-directory. Root can edit it and adding the key from the link above solved the Problem.
sudo echo "..." does NOT add the key. (No permissions) (Dafuqq?)
sudu su
-> cd /home/iobroker/.ssh
-> nano known_hosts
-> insert key here
Save and you are good to go.
However, it feels like something went wrong in the process here. Shouldn't node-red be able to save the key on its own? Maybe ask if the user shall allow the key?