fatal: Could not read from remote repository. #4037
Replies: 5 comments
-
|
For some reason, I had to update my local And set up a new deployment key. |
Beta Was this translation helpful? Give feedback.
-
|
as of yesterday (April 7th 2025) our deployments broke without any changes. We encountered the exact same issue as described above and the ForwardingAgent did not fix it. Anybody having insights on what can have happened/experienced the same? |
Beta Was this translation helpful? Give feedback.
-
|
For anybody else coming along: in our case the error was caused by one repository in our organization having a deploy-key of the name "runner" defined |
Beta Was this translation helpful? Give feedback.
-
|
@m1rm just updated my answer, in my case I had to do both - enable forwarding agent, and create a new deployment key. |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue, but in a different situation: Turns out, that Deployer only takes the first SSH key for the connection and ignores all other keys. The solution is to delete the old ones. After that, Deployer sees only the correct key. Then the SSH Agent has to be cleared. Following commands can be helpful
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Suddenly my deployment process stopped working, it was working without issues a week ago, the error I am getting is this:
When I connect to the server, and I run the command by hand, it works just fine:
I checked the github permissions and it works as well:
It's set up, as recommended, with a deploy key.
Any idea why deployer wouldn't be able to fetch the repository, but me, connected as same user, can do it without issues? I'm running out of ideas. As you see, it worked fine for 464 releases before 😅
Beta Was this translation helpful? Give feedback.
All reactions