-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git pull add-on : malformed deployment_key throwing libcrypto error. #3700
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I don't think this is stale |
I confirm, the solution from @baudneo is the functional workaround. I was experiencing the same issue and the new line dashes and double quotes fixed my headache. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
When using an SSH key with the git pull add-on, the add-on will format the key in YAML as:
Using the
- >-
YAML formatting which does not supply a \n (newline) at the end. This results in a libcrypto error when ssh tries to load the private key and fails the git command. When I try and manually add a newline using the>-
nomenclature, the text is reformatted when clicking the save button which removes the newline.I solved this issue by reformatting the key by editing the config in YAML mode:
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Git pull
What is the version of the add-on?
7.14.1
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Spotify
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
When using the
- >-
format, the private key needs a newline terminator at the end or you can switch the formatting.The text was updated successfully, but these errors were encountered: