# Connection to remote git repository is not possible

**URL:** <https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590>\
**Category:** General\
**Tags:** git\
**Created:** [5 November 2025 10:29 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590 "2025-11-05T10:29:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![wewa](https://avatars.discourse-cdn.com/v4/letter/w/91b2a8/32.png) [@wewa](https://discourse.nodered.org/u/wewa)\
**Post date:** [5 November 2025 10:29 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/1 "2025-11-05T10:29:51Z")

</div>

When trying to push my changes to my remote repo, node-red is not initiating the push. Just the following progress display is appearing for some milliseconds.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/a/aafb4beb737423ad49705d33d0f71bef5b65704a.png)

What I miss is that node-red is asking for the private key for my id\_rsa. Days ago, when I set up the remote connection, this was working fine. But now it stoped working. Also a restart of the node-red service is not helping.

Node-red is running on a Raspberry Pi and was installed acording follwing instruction: [Running on Raspberry Pi : Node-RED](https://nodered.org/docs/getting-started/raspberrypi)

What is going wrong here?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [5 November 2025 13:51 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/2 "2025-11-05T13:51:57Z")

</div>

If it did initially work and now does not due to the private key not being unlocked then it must have been unlocked when you first tried. Either you need an unlocked key or you need a key manager that lets you unlock it.

I don't use git with node-red so I don't have an exact answer. However, with recent npm attacks, I do now use signed git commits which require an unlocked key and I use a secrets manager for that. I'm currently using Kleopatra for that.

---

<div class="post-metadata">

**Author:** ![wewa](https://avatars.discourse-cdn.com/v4/letter/w/91b2a8/32.png) [@wewa](https://discourse.nodered.org/u/wewa)\
**Post date:** [13 November 2025 19:48 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/3 "2025-11-13T19:48:36Z")

</div>

But how to unlock the key? I thought node-red project will do this automatically or at least will ask for it.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [13 November 2025 20:36 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/4 "2025-11-13T20:36:55Z")

</div>

I unlock the key before it the cert is needed, it stays active in-memory, ready for use. That's what Kleopatra does for you.

---

<div class="post-metadata">

**Author:** ![wewa](https://avatars.discourse-cdn.com/v4/letter/w/91b2a8/32.png) [@wewa](https://discourse.nodered.org/u/wewa)\
**Post date:** [21 November 2025 06:21 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/5 "2025-11-21T06:21:30Z")

</div>

But I see no need in unlocking the key with some external tool. This seems just like a workaround for a bug in Node-RED to me.

Node-RED asked the first time when connecting to the remote for password to unlock id\_rsa. So it should just ask again the next time.

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [21 November 2025 08:54 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/6 "2025-11-21T08:54:38Z")

</div>

Are you running NR as a service?

If so you may need to check this issue

> <https://github.com/node-red/node-red/issues/5138>
>
> \### Current Behavior
> 
> On both versions 4.0.2 and 4.0.9 and the newest version of… RaspberryPi OS dated 2025-05-13. This is a clean install of both. I get an error when I try to clone a project from GitHub. There is not a directory "/run/user/0".
> 
> !\[Image\](https://github.com/user-attachments/assets/3815520a-0c43-4bfc-9662-1e5260ace616)
> 
> An unexpected error occurred:
> listen EACCES: permission denied /run/user/0/node-red-git-askpass-b17c333040d9423f-sock
> code: EACCES
> 
> 
> !\[Image\](https://github.com/user-attachments/assets/0493ca03-c735-49c4-ac6a-bf6fc7cb4a86)
> 
> !\[Image\](https://github.com/user-attachments/assets/3ff17e69-141e-4c25-802e-cd920e9427ff)
> 
> !\[Image\](https://github.com/user-attachments/assets/e6bde8a9-d107-41a8-a88d-365bc519ebd3)
> 
> \### Expected Behavior
> 
> \_No response\_
> 
> \### Steps To Reproduce
> 
> Start Imager
> Select Raspberry Pi 4 
> Select Raspberry Pi OS (64 Bit) dated 2025-05-13
> Install to storge device
> 
> Move SD card to Raspberry Pi 4 
> Set up network address 
> 
> After Install
> sudo apt update
> sudo apt full-upgrade
> sudo reboot
> 
> bash \<(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --allow-low-ports --node20 --confirm-pi --update-nodes --nodered-version="4.0.9"
> 
> sudo systemctl enable nodered.service
> 
> \### Example flow
> 
> None
> 
> 
> \### Environment
> 
> \- Node-RED version:4.0.2 or 4.0.9
> \- Node.js version: 20.19.2
> \- npm version:10.8.2
> \- Platform/OS: Raspberry Pi 4 / Raspberry Pi OS (64 Bit) dated 2025-05-13
> \- Browser: Windows 11 / Google Chrome Version 136.0.7103.114 (Official Build) (64-bit)

---

<div class="post-metadata">

**Author:** ![wewa](https://avatars.discourse-cdn.com/v4/letter/w/91b2a8/32.png) [@wewa](https://discourse.nodered.org/u/wewa)\
**Post date:** [21 November 2025 09:26 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/7 "2025-11-21T09:26:12Z")

</div>

Yes, I am. Thanks, I'll give it a try.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [21 November 2025 10:53 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/8 "2025-11-21T10:53:08Z")

</div>

> [@wewa](#):
>
> But I see no need in unlocking the key with some external tool. This seems just like a workaround for a bug in Node-RED to me.

Absolutely not!

The point of an external key manager is to manage the keys in a dedicated, security-focused tool away from other systems and services that might get compromised. Or, as in Node-RED's case, where anyone who can amend a flow would be able to get your pass code.

The 2nd point is to be able to automate service restarts without human intervention. The key manager takes care of it so if Node-RED has to restart for some reason, you don't have to have a person with access to the server to manually put in the passcode before it will restart.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [5 December 2025 10:53 UTC](https://discourse.nodered.org/t/connection-to-remote-git-repository-is-not-possible/99590/9 "2025-12-05T10:53:12Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.