-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Docs enahncement needed - invalid format of private key #4
Comments
Hello @yod527 The SSH key in the action is correct in your example. The SSH key in the secrets should start with |
@sbaerlocher adding extra space before However, I found out my issue. I'm connecting to my instances via ssh-proxy, which is specified in the inventory file: inventory.yml:
and that leads to the next errors:
If I try to remove the bastion host and connect to instances directly, by public IP address everything works fine. Also, I found a similar issue https://github.heygears.community/t/invalid-format-permission-denied-publickey/17342 and the answer is to use public IP address or install GitHub action in my network, which does not sound like a solution for me. P.S. From my local machine, connecting to instances via proxy does not cause any issues, and works just fine. |
I also had this problem. I needed to set StrictHostKeyChecking=no in ansible_ssh_common_args. Then apparently it does not need to find public key. |
Hello, I am exactly in the same use case you described @yod527. I tried to disable the strict host key checking as you mentioned @Goffen, but without success for now unfortunately. The connection to the bastion host seems to succeed as I get "Connection established." after seeing "Connecting to [ip-bastion] port 22". The last error available in the logs is : My initial SSH configuration was like this one : I then deleted the IdentityFile lines (which are temporary files with variable naming when playing the action) and instead added the key to the ssh agent when running locally. This still works locally but I still did not manage to make it work with Github Actions.
Do you have any idea or suggestion about a potential origin of the issue? |
@samuelp-mw Facing exactly the same issue, and not able to find a workaround to make it work in Gitlab. Have you found any solutions maybe? |
for me this is broken as well. no idea what is going on. my workaround is simply to and then instead of using the private_key property I pass
works for me 😵💫 |
Hello and thanks for your work!
Trying to launch my playbook, but getting private key error.
Getting next error:
Just not getting, what am I doing wrong.. How do I need to pass the private key correctly?
Thanks
The text was updated successfully, but these errors were encountered: