The Coding Journal ツ

Home

Impressum

x3ro’s Toolkit

After updating my net-ssh gem to 2.6.x I started getting this error message from Capistrano:

ArgumentError: Could not parse PKey: no start line

The private key in question was completely fine though, given that it had been working in several other applications, including openssh itself, for quite some time. There seem to be some weird issues with net-ssh 2.6.x and Capistrano at the moment, and so I simply downgraded to v2.5.2 and everything worked fine once again:

Keep deploying :)

After updating my net-ssh gem to 2.6.x I started getting this error message from Capistrano: ArgumentError: Could not parse PKey: no start line The private key in question was completely...

Ted Lilley on February 12, 2013 at 5:44 am said: I had a similar error which was because I didn’t have a matching public key file for my private. Not sure if it’s related to your issue. The fix was to run ssh-keygen -y -f ~/.ssh/id_rsa > ~/.ssh/id_rsa.pub . Reply ↓ Lucas Jenß on April 15, 2013 at 12:41 pm said: That actually worked. I keep my private keys in a separate folder, but moving the public key to the same folder as the private key actually fixed the problem… Thanks! Reply ↓ Marcello Barnaba on May 28, 2014 at 6:11 pm said: Thank you, you saved the day. Reply ↓

I had a similar error which was because I didn’t have a matching public key file for my private. Not sure if it’s related to your issue.

The fix was to run

Lucas Jenß on April 15, 2013 at 12:41 pm said: That actually worked. I keep my private keys in a separate folder, but moving the public key to the same folder as the private key actually fixed the problem… Thanks! Reply ↓

That actually worked. I keep my private keys in a separate folder, but moving the public key to the same folder as the private key actually fixed the problem… Thanks!

Marcello Barnaba on May 28, 2014 at 6:11 pm said: Thank you, you saved the day. Reply ↓

Thank you, you saved the day.

erthad on April 8, 2013 at 11:49 am said: I’ve run into the same issue when I was using Omnibus. After I’ve reinstalled Chef from gems the problem went away. Reply ↓

I’ve run into the same issue when I was using Omnibus. After I’ve reinstalled Chef from gems the problem went away.

Yazmin on April 13, 2013 at 4:14 am said: That is so interesting… I just got this error out of the blue tonight, having run no updates. I tried your solution first and Ruby started barking on deploy. Ted’s matching public key solution was my fix. Reply ↓

That is so interesting… I just got this error out of the blue tonight, having run no updates. I tried your solution first and Ruby started barking on deploy. Ted’s matching public key solution was my fix.

Steve on May 16, 2013 at 2:18 pm said: Yup, matching the keys was the fix for me too. More specifically, I ran into this same error message while using Cloud9 IDE ( https://c9.io/ ). I decided to try my repo into a browser based editor as long as I could still configure its sandbox and use Capistrano to deploy my Rails app. Now it works, Thanks Lucas and Ted! Reply ↓

Yup, matching the keys was the fix for me too.

More specifically, I ran into this same error message while using Cloud9 IDE ( https://c9.io/ ). I decided to try my repo into a browser based editor as long as I could still configure its sandbox and use Capistrano to deploy my Rails app. Now it works, Thanks Lucas and Ted!

Pingback: Tips for Creating OpenShift Apps with Windows https://www.openshift.com/blogs/tips-for-creating-openshift-apps-with-windows | doc.cloudgear.io

Your email address will not be published. Required fields are marked *

Name *

Email *

Website

Comment

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>