Strange Behavior

[remon]

I have been using Capistrano for many years , now I am facing a strange behavior

when I run cap deploy

it first ask for the server password , I type it and everything works fine , then my local passphrase key , also it works fine .

when it asks for the passphrase keys for the remote server keys , I need first to type 2 Enter Keys to make it work for the first passphrase key , for the second passphrase key , any key I press (with or without Enter key ) , it is abort the whole process

    [serverID] executing command
 ** [serverID :: out] Enter passphrase for key '/home/deployer/.ssh/id_rsa':
Password: (works with 2 Enter Keys )
 ** [serverID :: out]
 ** [serverID :: out] Enter passphrase for key '/home/deployer/.ssh/id_rsa':
Password: (Any Key I press , it continue and throw permission denied error)
 ** [serverID :: out]
 ** [serverID :: out] Permission denied (publickey).
 ** [serverID :: out]
 ** [serverID :: out] fatal: Could not read from remote repository.

I am using capistrano 2.13.5 ( I updated it to the latest version and nothing changed )

ruby 2.2.6p396

Rails 3.2.22

net-ssh , 3.2.0

in deploy.rb file I set these values

set :pty,  false

default_run_options[:pty] = true
ssh_options[:forward_agent] = true

[mattbrictson]

I am using capistrano 2.13.5

Unfortunately we don't officially support capistrano 2.x any more. We will not be making any more v2 releases, so if this is a bug it will not likely be fixed. Therefore I will be marking this as "closed". Sorry!

If you haven't already done so, try asking your question on Stack Overflow as well to see if anyone there can help. That is where support issues (as opposed to bugs) are usually discussed and solved.

[remon]

The same error also on the latest version of Capistrano also the latest version of net-ssh

after that I downgraded to v2

@mattbrictson

[mattbrictson]

Ah, thanks for clarifying. I'll reopen the issue.

[remon]

I checked the shell also I got these

It was working for years with me , I don't know what is the problem
@mattbrictson