Help needed - Git Pull and File Editor stopped connecting to GitHub at the same time

Hi all,

I’ve been trying for the past day trying to figure out what happened and how to fix it:

I realised yesterday both my Home Assistant instances stopped connecting to GitHub for updates (through the Git Pull add-on) around the same time, 2 weeks ago. I saw it when I saw in the logs that Git Pull couldn’t connect and then on GitHub, the key they were using said was used last time 2 weeks ago.

This happened on both instances I have (they connect to different repos on the same account), one is a RPi and the other is a Mac mini running HA on a VM. The RPi instance was seeded from a backup from the one running on the Mac mini. Git Pull was working on both in the beginning of March. I also usually keep my machines up-to-date, so consider they were being updated as soon as updates were available.

I started to try and fix it and generated new keys but now the Git Pull add-on logs show

Check SSH connection
[Warn] No valid SSH connection for [email protected]
[Info] Start adding SSH key
[Info] Setup deployment_key on id_rsa
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
/run.sh: line 35: /.ssh/id_rsa: No such file or directory
chmod: /.ssh/config: No such file or directory
chmod: /.ssh/id_rsa: No such file or directory
[Info] Local git repository exists
[Info] Git origin is correctly set to [email protected]:(...).git
[Info] Start git fetch...
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

[Error] Git fetch failed
Please make sure you have the correct access rights
and the repository exists.

This log is also strange because the add-on creates the /.ssh/ repo itself and creates the config file. Why does it fail to find the file afterwards?

If I connect through SSH to Home Assistant I can connect to GitHub and do git pull. This is using the new key I generated when trying to solve the Git Pull issue.

Can anyone help? I didn’t find anyone with a similar issue in my searches on Google.

I’m wondering if something changed recently in how add-ons communicate with the rest of the file system that could explain this.

You are not alone, I ran into exactly the same, did you find a solution in the mean time?

When did it start for you?

Same as you, started recent, approx 2 weeks ago.

The update to 2024.4.0 did not fix it. Is this a bug or did our configuration somehow got messed up?

The update to 2024.4.1 did not fix it. Is this a bug or did our configuration somehow got messed up?

A new add-on version just dropped, 7.14.1, and the logs now don’t complain anymore about the key! Seems fixed for me.