配置Git SSH访问替代HTTPS：协作者SSH密钥添加与验证遇阻

Hey Mike, since you’ve already got SSH working for this user on a test server, the issue in production is almost certainly an environment-specific configuration quirk. Let’s walk through targeted checks to fix this:

• Verify SSH key permissions and location
  SSH is strict about file permissions—if your private key is readable by others, it’ll refuse to use it. Run these commands in production to lock down permissions:

  chmod 700 ~/.ssh
  chmod 600 ~/.ssh/id_rsa  # Replace with your key filename if you used a custom name
  

  Double-check that your private key is actually stored in ~/.ssh/ (or the custom path you specified when generating it).

• Force Git to use your specific SSH key
  If production has multiple SSH keys (e.g., for other services), Git might be trying the wrong one. Create or edit ~/.ssh/config to explicitly map GitHub to your key:

  Host github.com
    User git
    IdentityFile ~/.ssh/your-key-filename
    IdentitiesOnly yes
  

  Test the connection with ssh -T git@github.com—you should see a message like "Hi [user]! You've successfully authenticated..." if it works.

• Confirm your Git remote is correctly set
  Even if you set the remote earlier, it’s worth double-checking. Run:

  git remote -v
  

  Make sure the origin entry shows git@github.com:user/project.git (not the HTTPS URL). If it’s wrong, update it with:

  git remote set-url origin git@github.com:user/project.git
  

• Check ssh-agent integration
  If you’re using ssh-agent to manage keys, ensure your key is added to the agent in production:

  ssh-add -l
  

  If your key isn’t listed, add it with ssh-add ~/.ssh/your-key-filename. Note: If you’re running this in a non-interactive shell (e.g., a deploy script), you might need to set up agent forwarding or use a passphrase-less key (though passphrase-less keys are less secure—only use this if necessary).

• Dig into verbose logs for errors
  If none of the above works, capture detailed debug output to pinpoint the issue:

  • Test SSH connection directly: ssh -vvv git@github.com
  • Test a Git operation with SSH debug: GIT_SSH_COMMAND="ssh -vvv" git pull
    Look for lines like "Permission denied", "No such file or directory", or "Host key verification failed"—these will tell you exactly what’s breaking.

If you hit a specific error in the logs, share those details and we can narrow it down further!

内容的提问来源于stack exchange，提问作者Mike Nagler