Plugin not working anymore 4.2

Just released a new version – lmk if it works for you!

I have been successfully using the plugin at version 0.4. This morning version 0.6 was offered as well as WP 4.2.2. I try things out on a “sandbox” that I run locally. I installed the 0.6 SSH SFTP Updater Support plugin first then when trying to update WP to 4.2.2 I got a message “Are you sure you want to do this?” and a “retry” link. Clicking retry produced a loop back to the retry screen. It would not update WP. I re-installed version 0.4 of SSH SFTP Updater Support and then successfully upgraded WP to 4.2.2 on the sandbox. I then re-installed version 0.6 and tried to install another plugin – (Hello Dolly) – That was successful. I then tried to remove it and it took me to the “Delete Plugin” screen. Clicking “yes, delete these files” took me to the enter “connection information” screen. I entered the information and was again sent back to the “Delete Plugin” screen. This loop continued. No files were deleted. The SSH SFTP Updater Support plugin greatly simplifies upgrades to my live site but it appears that 0.6 is not working well and I have not updated it on my live site. I updated WP to 4.2.2 with the 0.4 version of SSH SFTP Updater Support. Thank you. Jim

I just downloaded WordPress 3.9 and installed 0.6 of this plugin and was able to both install other plugins and update to WordPress 4.2.2 with this plugin. See the screenshots below:

https://i.stack.imgur.com/JQtSM.png
https://i.stack.imgur.com/9qdmA.png

So I’m not able to recreate the loop you describe in your post when upgrading WordPress. Maybe you’re upgrading from a different version?

That said, deleting plugins on 4.2.2 does seem to be an issue with v0.6 of this plugin. I am looking into it now. Thanks for the heads up!

@ziggy43 – try the 0.6.1 release.

Looking good now. I have installed 0.6.1 on “sandbox” and was able to delete “Hello Dolly” plugin. I was also able to upgrade another plugin that offered an upgrade today.

FYI I was upgrading WP from 4.2.1 to 4.2.2 when I discovered the original “retry – are you sure you want to do this” error. I have not been offered any additional WP upgrades to try it on. Thanks a big bunch for your quick response. Jim

I was able to do a “re-install” of 4.2.2 on “sandbox” using version 0.6.1. Not sure if that totally proves it but again looks good. Thanks

I can’t update the plugin either. I’m on WP 4.2.2.

When I go to “Update plugins” and check the update box for this plugin I get to a page titled “Connection Information”

Under that is this – the fields are grayed out though so I can’t edit them:

To perform the requested action, WordPress needs to access your web server. Please enter your FTP or SSH credentials to proceed. If you do not remember your credentials, you should contact your web host.

Hostname
FTP/SSH Username
FTP/SSH Password

Without this plugin being updated I can’t install other plugins. I know you just released an update to 6.1 but not working for me.

I’m not an expert so not sure how to go around this without being able to update the plugin.

Any ideas?

Thanks.

It also says at top “Private key incorrect”

Newest release, seeing the same thing, “Private Key Incorrect” downgraded to older version and it works. What can we send to help debug?
Only error I see is ” PHP Notice: Undefined variable: allow_relaxed_file_ownership in /home/html/wp-content/plugins/ssh-sftp-updater-support/sftp.php on line 37″
WP 4.2.2
PHP 5.3.2-1ubuntu4.30

Only error I see is ” PHP Notice: Undefined variable: allow_relaxed_file_ownership in /home/html/wp-content/plugins/ssh-sftp-updater-support/sftp.php on line 37″

I’m pretty darned sure that that issue was fixed in 0.6.1. ie. the version you should be running if you are indeed running the latest version.

Regardless, what version of WordPress are you using? Can you post a copy of your sftp.php? Post it on pastebin.com and post a link here.

As for the “Private Key Incorrect”… two possibilities I can think of off hand.

1. The private key really is incorrect.
2. You’re using selinux

idk if the logging techniques I used to debug previous versions of WordPress will work with 4.2. If not I’ll need to come up with new ones. I need to investigate that and how to come up with a reliable selinux test.

I have a busy next few days but I’ll try to squeeze it in.

I can’t add any plugins or update any others now. Nothing changed on server side – my key didn’t change. With this new version I can’t do anything.

Not sure how to revert back to the old one. Can you please fix the “Private Key Incorrect” issue soon please? Everything is grayed out on that screen so I couldn’t upload a new key even if I had one.

Thanks

First, I think you should probably create a new topic instead of posting in this one.

Not sure how to revert back to the old one.

SFTP in with a regular SFTP client?

Can you please fix the “Private Key Incorrect” issue soon please?

You’re assuming that there actually is anything I can do to fix it. If you really are using the incorrect private key there’s no amount of code changes that I can make that’ll make it work.

If it’s an issue with you using selinux… well again there’s not a whole heck of a lot I can do. I might be able to make the plugin present a warning if you’re using selinux but if fsockopen() can’t connect fsockopen() can’t connect and I can’t change that in PHP.

Everything is grayed out on that screen so I couldn’t upload a new key even if I had one.

FWIW, a lot of this code is copy / pasted from WordPress’s built-in functionality. phpseclib_request_filesystem_credentials_modal is pretty much copy / pasted from wp-admin/includes/file.php. There are some slight differences but those differences are very slight.

Anyway, quoting from the function:

<input name="hostname" type="text" id="hostname" aria-describedby="request-filesystem-credentials-desc" class="code" placeholder="<?php esc_attr_e( 'example: www.www.remarpro.com' ) ?>" value="<?php echo esc_attr($hostname); if ( !empty($port) ) echo ":$port"; ?>"<?php disabled( defined('FTP_HOST') ); ?> />

<td><input name="username" type="text" id="username" value="<?php echo esc_attr($username) ?>"<?php disabled( defined('FTP_USER') ); ?> size="40" /></td>

<td><input name="password" type="password" id="password" value="<?php if ( defined('FTP_PASS') ) echo '*****'; ?>"<?php disabled( defined('FTP_PASS') ); ?> size="40" /></td>

The only time a field is disabled is if you’ve defined an FTP_* constant corresponding to that field. Presumably you’d do these definitions in wp-config.php altho I guess technically they could be done anywhere. So check that.

It worked before – now with the update it doesn’t work. Same topic as header. It worked fine until 6.1.

I’ll have a dev friend take a look. I spend most of my time creating sites and less on the backend/server side.

The latest version in trunk adds some expanded error messages.

Also, if you want some fast diagnosing give me SFTP access. Email the credentials to [email protected].

That said, one issue that still needs to be fixed… so I removed the textarea to save on screen real estate but the RSA key is still being cached there. What this means is that you can’t see what the RSA key is. You can’t preview it. So I think I need to bring back the textarea, maybe as a modal or some such.