After 4.3 update I'm unable to update plugins or themes

I’m running
php 5.3.3 on rhel 6.7
libSSH Version => libssh2/1.4.2
libssh2 version => 1.2.2
banner => SSH-2.0-libssh2_1.2.2

Dunno if it’s helpful, but here’s mine:

PHP 5.4.44 on Amazon Linux AMI release 2015.03
libSSH Version => libssh2/1.4.2
libssh2 version => 1.2.2
banner => SSH-2.0-libssh2_1.2.2

Mine are like Navjot and mezinster’s:

PHP Version 5.5.9-1ubuntu4.11
extension version => 0.12
libssh2 version => 1.4.3
banner => SSH-2.0-libssh2_1.4.3

Just upgraded PHP to 5.6.12 and now I am being asked to verify FTP credentials. They are pre-filled but nothing happens whether I choose FTP or FTP(SSL) and try to proceed.

I’m running into the same problem.

PHP Version 5.5.9-1ubuntu4.11
extension version 0.12
libssh2 version 1.4.3
banner SSH-2.0-libssh2_1.4.3

I have the same issue.

The problem (unable to update plugins) ONLY happened AFTER I upgraded to 4.3 – so the culprit *IS* 4.3.

I have never had any problems (for lots of years) upgrading my wordpress install and/or my plugins.

Further, I have not changed a thing, absolutely nothing. No permissions, no settings, no added plugins, no deleted plugins.

I only upgraded to 4.3 and this happened.
I use FS_METHOD -> ssh2.

I have the same problem.

Before updating to the version 4.3 i didn’t have this problem.

Operating System : Linux (64 Bit)
Server : Apache/2.2.22 (Debian)
PHP Version : 5.4.39-0+deb7u2
libssh2/1.4.2

For reference, the tracking ticket for this issue: https://core.trac.www.ads-software.com/ticket/33480

Looks like the workaround is found.
/wp-admin/includes/class-wp-filesystem-ssh2.php

public function is_writable($file) {
/**$file = ltrim($file, '/');
*return is_writable('ssh2.sftp://' . $this->sftp_link . '/' . $file);
*/
// PHP will base it's writable checks on system_user === file_owner, not ssh_user === file_owner
return true;
}

I’ve succeed in updating everything now, but some strange feeling of suspicion is still here…

Thanks for sharing mezinster.

@dion Hulse, is this the definitive workaround we should go for or are you guys planning to launch a new update that fixes this without us having to modify any core files?

@dm652: This is the fix that is currently in the trunk code.
https://core.trac.www.ads-software.com/changeset/33688

A fix for 4.3.1 is still being worked on.

If you are having this problem right now and need a remedy, then patching your copy of WordPress now is fine. Any future updates to fix the issue will simply overwrite this file, so your custom patch won’t cause any harm.

4.3.1 will be released with above fix in it, although 4.3.1 won’t be rushed for this particular bug.

If you’re affected, and don’t wish to use the sftp plugin then altering the file to simply return true; is the recomended suggestion until 4.3.1 is released.

I was getting 500 errors with both theme and plugin updates. Using mezinster code suggestion – almost worked, and Dion Husle statement about return true; – got me most of the way. I needed to change it to return false; I am using mediatemple grid server. Seems to work now.

The change to /wp-admin/includes/class-wp-filesystem-ssh2.php listed above worked for me.