最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

Git Pull failing for 1 project in VS Code - Stack Overflow

programmeradmin0浏览0评论

I'm developing 2 separate projects using VS Code connected to GitHub. I'm running Ubuntu 24.04.1 LTS on a Dell Latitude. The projects are in /home/website/mtbc and /home/website/blogApp. All works fine for the blogApp, but the other has developed a problem whenever I try to Sync Changes following a Commit. When I press Sync Changes I get the following messages:

 git pull --tags origin main
sign_and_send_pubkey: signing failed for RSA "/home/a___t/.ssh/id_rsa" from agent: agent refused operation
sign_and_send_pubkey: signing failed for ED25519 "/home/allentrev/.ssh/id_ed25519" from agent: agent refused operation
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I'd appreciate some help on how to problem solve the issue. I don't understand how it can work on one project but not the other. I'm going at it randomly at the moment and don't really know what I'm doing.

I've followed the steps in the GitHub docs SSH Troubleshooting Guide:

a) I'm not using Sudo anywhere. The Keys were generated and added to GitHub using my username.

b) I'm connected to [email protected]. After running ssh -vT [email protected] I get the console output contained here

c) I have always used [email protected]. If I use ssh -T [email protected] I get:

sign_and_send_pubkey: signing failed for RSA "/home/allent/.ssh/id_rsa" from agent: agent refused operation

sign_and_send_pubkey: signing failed for ED25519 "/home/allent/.ssh/id_ed25519" from agent: agent refused operation

[email protected]: Permission denied (publickey).

d) I have loaded keys: output to ssh-add -l -E sha256 is:

sign_and_send_pubkey: signing failed for RSA "/home/allent/.ssh/id_rsa" from agent: agent refused operation

sign_and_send_pubkey: signing failed for ED25519 "/home/allent/.ssh/id_ed25519" from agent: agent refused operation

These keys are being used: see contents off b)

e) Public keys are attached to account: Using ssh-add -l I get

4096 SHA256:gux9QvdUBTNfxBEpYgrrEsg8A4IU09kDhl/gPYcSqhg [email protected] (RSA)

256 SHA256:uyfYdlfHomrum6UDD+alsM/Bs8J4dCh/nvDkRO2tSdI [email protected] (ED25519)

They both are in the Authentication Keys list in SSH Keys section on my GitHub account

So, as far as I can see Ive covered the issues raised in the document. The only change I had to make was on the permissions, changing them to RW, and then updating ssh-agent, but still no change. Ive also generated completely new keys, and put in GitHub, but I still cant use these.

I'm developing 2 separate projects using VS Code connected to GitHub. I'm running Ubuntu 24.04.1 LTS on a Dell Latitude. The projects are in /home/website/mtbc and /home/website/blogApp. All works fine for the blogApp, but the other has developed a problem whenever I try to Sync Changes following a Commit. When I press Sync Changes I get the following messages:

 git pull --tags origin main
sign_and_send_pubkey: signing failed for RSA "/home/a___t/.ssh/id_rsa" from agent: agent refused operation
sign_and_send_pubkey: signing failed for ED25519 "/home/allentrev/.ssh/id_ed25519" from agent: agent refused operation
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I'd appreciate some help on how to problem solve the issue. I don't understand how it can work on one project but not the other. I'm going at it randomly at the moment and don't really know what I'm doing.

I've followed the steps in the GitHub docs SSH Troubleshooting Guide:

a) I'm not using Sudo anywhere. The Keys were generated and added to GitHub using my username.

b) I'm connected to [email protected]. After running ssh -vT [email protected] I get the console output contained here

https://gist.github/allentrev/546822136f46d257a906a16bd2d0c11b

c) I have always used [email protected]. If I use ssh -T [email protected] I get:

sign_and_send_pubkey: signing failed for RSA "/home/allent/.ssh/id_rsa" from agent: agent refused operation

sign_and_send_pubkey: signing failed for ED25519 "/home/allent/.ssh/id_ed25519" from agent: agent refused operation

[email protected]: Permission denied (publickey).

d) I have loaded keys: output to ssh-add -l -E sha256 is:

sign_and_send_pubkey: signing failed for RSA "/home/allent/.ssh/id_rsa" from agent: agent refused operation

sign_and_send_pubkey: signing failed for ED25519 "/home/allent/.ssh/id_ed25519" from agent: agent refused operation

These keys are being used: see contents off b)

e) Public keys are attached to account: Using ssh-add -l I get

4096 SHA256:gux9QvdUBTNfxBEpYgrrEsg8A4IU09kDhl/gPYcSqhg [email protected] (RSA)

256 SHA256:uyfYdlfHomrum6UDD+alsM/Bs8J4dCh/nvDkRO2tSdI [email protected] (ED25519)

They both are in the Authentication Keys list in SSH Keys section on my GitHub account

So, as far as I can see Ive covered the issues raised in the document. The only change I had to make was on the permissions, changing them to RW, and then updating ssh-agent, but still no change. Ive also generated completely new keys, and put in GitHub, but I still cant use these.

Share Improve this question asked Feb 2 at 11:45 allentallent 111 silver badge2 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 1

This query can be closed. I decided that my development machine was too insecure as to continue this path. I re-built my machine and the problems went away.

发布评论

评论列表(0)

  1. 暂无评论