Viewing 9 replies - 16 through 24 (of 24 total)
  • Same issue here regarding the “Private key incorrect for xxxxx” message. I’ve not touched the private key so am pretty sure it’s not changed in any way.

    I had everything working fine, I was running 0.6.1 with WordPress 4.1.x and could update plugins OK. I then updated WP core to 4.2.2, the update applied fine but since doing so I can’t seem to add/remove/update anything, I just get the private key error.

    I’ve tried the version from trunk with expanded error messages, I now get an additional error:

    “Make sure that the key you are using is an RSA key and not a DSA key.”

    Further investigation … I’ve removed the version from trunk and rollved all the way back to 0.4.0, everything works great again.

    That’s without touching any private keys or anything else.

    Plugin Author TerraFrost

    (@terrafrost)

    0.7.0 has been released. The modal dialog is to restrictive imho and useful features had to be removed to accommodate it. In particular, key previewing.

    Also, in looking at the code, the old phpseclib_request_filesystem_credentials function had a fallback for browsers that didn’t support HTML5’s reading of the key whereas the new one didn’t.

    All is working again running 0.7.

    Thanks for your continued support with this plugin.

    This isn’t working for me. I have WP 4.2.2 and the 0.7 version of the plugin. I continue to get:
    Private key incorrect for wordpress
    Make sure that the key you are using is an RSA key and not a DSA key

    We have our wp-config.php linked up to our RSA key, which had worked before. Nothing has changed there.

    But also doesn’t allow me to even copy/paste or upload a new private key. So not even sure if I could do that manually if I wanted to. Can anyone upload the private key for SSH2?

    Plugin Author TerraFrost

    (@terrafrost)

    @blueion – What browser are you using?

    One thing I’m willing to do… we could make a little bet. I’ll bet you $50 USD that the issue is on your end (be it user error or a browser error or whatever). If I’m right you pay me $50 USD. If I’m wrong I’ll pay you $50 USD. To qualify you can either (1) email me auth info for a WordPress admin account on your site and SFTP credentials so that I may reproduce the issue or (2) you provide a patch that fixes this alleged issue. Note that a patch making this plugin work on, say, IE5 on Win98, although perhaps worthwhile, will not constitute a win for you.

    Plugin Author TerraFrost

    (@terrafrost)

    Another possibility: maybe you enabled mbstring.func_overload on the server and do not consider that to be any more relevant a change than the server uptime changing (even tho it is).

    Sorry, I don’t think we’re interesting on betting for help. I’ll continue to try and figure it out, but we are server administrators and not a basic user. We’ve set up SSH keys before for this and has worked. And we certainly don’t go near IE. Firefox or Chrome is being used. So I pretty much am sure it’s not something as basic as that.

Viewing 9 replies - 16 through 24 (of 24 total)
  • The topic ‘Plugin not working anymore 4.2’ is closed to new replies.