Capistrano 部署在 git:check 上失败 - 权限被拒绝(公钥)

Question

本地操作系统：Windows 10 Pro(使用Git Bash作为我的终端)

登台服务器操作系统：Ubuntu 16.04 LTS

我一直在努力在我的临时服务器上进行基本的 Capistrano 部署。我按照本指南设置了Capistrano。

部署过程在git:check阶段总是失败，因为据称无权访问我在 GitLab 上的存储库。我确定我的 SSH 代理转发工作正常，因为我能够通过 SSH 连接到我的服务器并使用我的 SSH 密钥访问 GitLab。SSH 密钥未存储在我的服务器上的任何位置：

$ ssh [e-mail]
deploy@MyServer:~$ ssh -T [e-mail]
debug1: client_input_channel_open: ctype [e-mail] rchan 2 win 65536 max 16384
debug1: channel 1: new [authentication agent connection]
debug1: confirm [e-mail]
Welcome to GitLab, Alexander!debug1: channel 1: FORCE input drain

到目前为止，关于这个问题的问题都没有对我有用。

这是我的部署文件：

部署.rb

set :application, "myapp"
set :branch, "master"
set :repo_url, "[e-mail]:MyApp/myapp.git"
# Defaults to false
# Skip migration if files in db/migrate were not modified
set :conditionally_migrate, true
set :ssh_options, { forward_agent: true }
set :rvm_ruby_version, '2.2.6'
# Default deploy_to directory is /var/www/my_app_name
set :deploy_to, "/var/www/#{fetch(:application)}/"
set :deploy_user, "deploy"
# Tells Capistrano to store config/database.yml file inside a directory called /shared, which is meant for any files
# we want to persist between deploys
set :linked_files, fetch(:linked_files, []).push('config/database.yml', 'config/secrets.yml')
# Directories that are meant to persist between deploys, and they will also be stored inside /shared
set :linked_dirs, fetch(:linked_dirs, []).push('bin', 'log', 'tmp/pids', 'tmp/cache', 'tmp/sockets', 'vendor/bundle', 'public/system', 'public/uploads')
# The specs that should be run before deployment is allowed to continue
set :tests, []
# Delayed Job Config: https://github.com/AgileConsultingLLC/capistrano3-delayed-job
set :delayed_job_workers, 3
# Keep the last 5 deploys for rollback purposes
set :keep_releases, 5
namespace :deploy do
after :restart, :clear_cache do
on roles(:web), in: :groups, limit: 3, wait: 10 do
# Here we can do anything such as:
# within release_path do
#   execute :rake, 'cache:clear'
# end
end
end
end

staging.rb

set :stage, :staging
set :rails_env, :staging
role :app, %w{[e-mail]}
role :web, %w{[e-mail]}
role :db,  %w{[e-mail]}

这是我部署时的 Capistrano 调试日志：

$ bundle exec cap staging deploy --trace
** Invoke staging (first_time)
** Execute staging
** Invoke load:defaults (first_time)
** Execute load:defaults
** Invoke rvm:hook (first_time)
** Invoke passenger:rvm:hook (first_time)
** Invoke passenger:test_which_passenger (first_time)
** Execute passenger:test_which_passenger
** Execute passenger:rvm:hook
** Execute rvm:hook
** Invoke rvm:check (first_time)
** Execute rvm:check
rvm 1.29.3 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin [https://rvm.io]
ruby-2.2.6
ruby 2.2.6p396 (2016-11-15 revision 56800) [x86_64-linux]
** Invoke bundler:map_bins (first_time)
** Invoke passenger:bundler:hook (first_time)
** Execute passenger:bundler:hook
** Execute bundler:map_bins
** Invoke deploy:set_rails_env (first_time)
** Execute deploy:set_rails_env
** Invoke deploy:set_linked_dirs (first_time)
** Execute deploy:set_linked_dirs
** Invoke deploy:set_rails_env
** Invoke deploy (first_time)
** Execute deploy
** Invoke deploy:starting (first_time)
** Execute deploy:starting
** Invoke deploy:check (first_time)
** Invoke git:check (first_time)
** Invoke git:wrapper (first_time)
** Execute git:wrapper
00:00 git:wrapper
01 mkdir -p /tmp
✔ 01 [e-mail] 0.286s
Uploading /tmp/git-ssh-myapp-staging-localuser.sh 100.0%
02 chmod 700 /tmp/git-ssh-myapp-staging-localuser.sh
✔ 02 [e-mail] 0.277s
** Execute git:check
00:01 git:check
01 git ls-remote [e-mail]:MyApp/myapp.git HEAD
01 Permission denied (publickey).
01 fatal: Could not read from remote repository.
01
01 Please make sure you have the correct access rights
01 and the repository exists.
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as [e-mail]: git exit status: 128
git stdout: Nothing written
git stderr: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/runners/parallel.rb:15:in `rescue in block (2 levels) in execute'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/runners/parallel.rb:11:in `block (2 levels) in execute'
Caused by:
SSHKit::Command::Failed: git exit status: 128
git stdout: Nothing written
git stderr: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/command.rb:99:in `exit_status='
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/backends/netssh.rb:169:in `execute_command'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/backends/abstract.rb:141:in `block in create_command_and_execute'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/backends/abstract.rb:141:in `tap'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/backends/abstract.rb:141:in `create_command_and_execute'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/backends/abstract.rb:74:in `execute'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/capistrano-3.10.1/lib/capistrano/scm/git.rb:77:in `git'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/capistrano-3.10.1/lib/capistrano/scm/git.rb:38:in `check_repo_is_reachable'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/capistrano-3.10.1/lib/capistrano/scm/tasks/git.rake:19:in `block (4 levels) in eval_rakefile'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/backends/abstract.rb:93:in `with'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/capistrano-3.10.1/lib/capistrano/scm/tasks/git.rake:18:in `block (3 levels) in eval_rakefile'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/backends/abstract.rb:29:in `instance_exec'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/backends/abstract.rb:29:in `run'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sshkit-1.15.1/lib/sshkit/runners/parallel.rb:12:in `block (2 levels) in execute'
Tasks: TOP => deploy:check => git:check
The deploy has failed with an error: Exception while executing as [e-mail]: git exit status: 128
git stdout: Nothing written
git stderr: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
** Invoke deploy:failed (first_time)
** Execute deploy:failed

** DEPLOY FAILED
** Refer to log/capistrano.log for details. Here are the last 20 lines:

DEBUG [6b6ba2d0] Finished in 0.471 seconds with exit status 0 (successful).
DEBUG [c6e2d7dc] Running ~/.rvm/bin/rvm 2.2.6 do ruby --version as [e-mail]
DEBUG [c6e2d7dc] Command: ~/.rvm/bin/rvm 2.2.6 do ruby --version
DEBUG [c6e2d7dc]       ruby 2.2.6p396 (2016-11-15 revision 56800) [x86_64-linux]
DEBUG [c6e2d7dc] Finished in 0.608 seconds with exit status 0 (successful).
INFO [fd5500a8] Running /usr/bin/env mkdir -p /tmp as [e-mail]
DEBUG [fd5500a8] Command: /usr/bin/env mkdir -p /tmp
INFO [fd5500a8] Finished in 0.286 seconds with exit status 0 (successful).
DEBUG Uploading /tmp/git-ssh-myapp-staging-localuser.sh 0.0%
INFO Uploading /tmp/git-ssh-myapp-staging-localuser.sh 100.0%
INFO [f33d4873] Running /usr/bin/env chmod 700 /tmp/git-ssh-myapp-staging-localuser.sh as [e-mail]
DEBUG [f33d4873] Command: /usr/bin/env chmod 700 /tmp/git-ssh-myapp-staging-localuser.sh
INFO [f33d4873] Finished in 0.277 seconds with exit status 0 (successful).
INFO [86d3cd5a] Running /usr/bin/env git ls-remote [e-mail]:MyApp/myapp.git HEAD as [e-mail]
DEBUG [86d3cd5a] Command: ( export GIT_ASKPASS="/bin/echo" GIT_SSH="/tmp/git-ssh-myapp-staging-localuser.sh" ; /usr/bin/env git ls-remote [e-mail]:MyApp/myapp.git HEAD )
DEBUG [86d3cd5a]       Permission denied (publickey).
DEBUG [86d3cd5a]       fatal: Could not read from remote repository.

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

我尝试手动运行 Capistrano 在本地和远程服务器上尝试的命令，它们都成功了。我真的很困，任何帮助将不胜感激！

Answer 1

按照以下步骤将公有密钥添加到存储库设置中的部署密钥列表中：

本地计算机设置：

1. 检查您的本地系统是否有~/.ssh/id_rsa.pub密钥文件。如果没有，请创建一个新的：

   $ ssh-keygen -t rsa
   

2. 在设置中将新创建的公钥~/.ssh/id_rsa.pub添加到存储库的部署(访问)密钥中：

   • 位桶 ：
     • https://confluence.atlassian.com/bitbucket/set-up-ssh-for-git-728138079.html#SetupSSHforGit-Step4.InstallthepublickeyonyourBitbucketaccount
   • Github ：
     • https://developer.github.com/v3/guides/managing-deploy-keys/#deploy-keys
   • GitLab ：
     • https://docs.gitlab.com/ce/ssh/README.html#deploy-keys

3. 将密钥加载到ssh-agent：

   检查ssh-agent是否正在运行，如果没有，则启动 ssh 代理

   $ ssh-agent /bin/bash
   

   将id_rsa密钥添加到代理：

   $ ssh-add ~/.ssh/id_rsa
   

   注意：有时，如果您在部署期间收到">拒绝访问存储库"错误，则需要在每次部署之前完成此步骤(步骤 - 3)。

4. 将本地 SSH 密钥添加到部署服务器授权密钥文件(请记住将端口号替换为自定义端口号)：

   $ cat ~/.ssh/id_rsa.pub | ssh -p port_num user@server_ip 'cat >> ~/.ssh/authorized_keys'
   

参考：https://www.digitalocean.com/community/tutorials/deploying-a-rails-app-on-ubuntu-14-04-with-capistrano-nginx-and-puma

部署.rb

尝试更改deploy.rb文件中的ssh_options，如下所示：

set :ssh_options, { forward_agent: true, user: "deploy", auth_methods: ['publickey'], keys: %w(~/.ssh/privatekey.pem) }

将~/.ssh/privatekey.pem替换为 SSH 私钥文件路径的路径。

部署：

只需运行cap staging deploy即可部署到服务器。

根据需要将部署命令中的staging替换为环境cap。

Answer 2

感谢所有回答的人，我设法找到了解决方案！罪魁祸首是 Git Bash，无论出于何种原因，当我运行chmod 700 ~/.ssh时，它没有将我的~/.ssh目录的权限更改为 0700。这阻止了 SSH 代理转发在 Capistrano 部署时工作，但在我手动 SSH 进入服务器时则无法正常工作。我决定尝试在 Windows 上的 Ubuntu 上使用 Bash (BUW) 而不是 Git Bash，果然，我的部署奏效了！我将相同的配置和密钥从 Git Bash 复制到 BUW。唯一的区别是我能够将 BUW~/.ssh目录的权限更改为 0700。话虽如此，这是我问题的解决方案：

1. 创建部署密钥并将其添加到 GitLab

正如 @Onur 和 @grizzthedj 以及 M @Gokul所示，我需要为 GitLab 创建一个部署密钥并在我的服务器上对其进行授权。这是我是如何做到的：

1. 在本地计算机上生成新的 SSH 密钥：ssh-keygen -t rsa -b 4096
2. 复制公钥的输出：cat ~/.ssh/id_rsa.pub
3. 通过 SSH 连接到我的服务器
4. 将公钥添加到~/.ssh/authorized_keys末尾
5. 回到我的本地计算机，打开浏览器，登录 GitLab，转到我的存储库页面，然后将公钥粘贴到">存储库>>部署密钥"中的
设置

阿拉伯数字。使用 BUW 而不是 Git Bash

1. 在我的本地计算机上，我设置 BUW 以使用此 SO 答案中的说明在会话加载时启动 SSH 代理。
2. 更改~/.ssh的权限：chmod 700 ~/.ssh

3. 启动 SSH 代理并向其中添加我的部署密钥：

   eval $(ssh-agent -s)
   ssh-add ~/.ssh/id_rsa
   

我已经从我的 deploy.rb文件中删除了set :ssh_options行，因为它在没有它的情况下工作得很好。

就是这样！看起来从现在开始我将使用 BUW 进行部署。

Answer 3

根据您的cap deploy输出，从笔记本电脑到服务器的SSH连接似乎不是问题。

00:00 git:wrapper
01 mkdir -p /tmp
✔ 01 [e-mail] 0.286s
Uploading /tmp/git-ssh-myapp-staging-localuser.sh 100.0%
02 chmod 700 /tmp/git-ssh-myapp-staging-localuser.sh
✔ 02 [e-mail] 0.277s 

此问题是当 capistrano 尝试通过 SSH 运行git ls-remote [e-mail]:MyApp/myapp.git HEAD时。

您需要将公钥添加到 GitLab 中的 SSH 密钥中，因为 SSH 代理转发要求在所有目标系统上安装公钥。Gitlab，在你的例子中，是一个目标系统。

cat ~/.ssh/id_rsa.pub    # Copy the contents of your public key(filename may be different)

登录到 GitLab，并将公钥粘贴到存储库的 SSH 密钥(可在存储库设置中找到)中，您应该很好。

您还需要在ssh_options中指定用于创建 SSH 密钥的用户。

set :ssh_options, {
forward_agent: true,
user: 'deploy',
}

Answer 4

您还需要为存储库定义远程服务器的公钥。显然，您的计算机可以访问存储库，但服务器无法访问。

要获取默认公钥，您可以查看~/.ssh/id_rsa.pub也可以使用ssh-keygen -t rsa -b 4096 -C "[e-mail]"生成一个公钥 不要忘记在服务器中使用ssh-add来初始化公钥。

希望对你有帮助

Answer 5

对于那些将来遇到此问题寻找替代方案的人：

有关此问题的大多数搜索都建议添加 SSH 密钥。如果您确定它们已经添加，并且ssh -T [e-mail](或您正在使用的任何 git 服务)显示您已登录，并且设置了代理转发，那么在遇到相同问题时在 Windows 上对我有用的另一种方法是安装 PuTTY。安装后：

• 打开 PuTTYGen>转换>导入密钥(如果您有要使用的密钥;否则，请生成一个新密钥)
• 跑步选美(包含在 PuTTY 中)
• 在系统托盘中找到选美，右键单击，然后"添加密钥">
• 添加上述密钥
• 像以前一样cap deploy运行

我在另一篇关于在 Windows 上使用 Capistrano 时响应长度错误的 SO 文章中发现了这种方法，因此表面上它也适用于这些情况。这可能是因为Windows上的net-ssh需要Pageant才能工作。

Answer 6

我遇到了类似的问题，对我来说，我所要做的就是将我的SSH密钥添加到GitHub。可在此处找到此过程的文档：https://docs.github.com/en/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account