Hi,
I just updated several things on a user website, including to the latest version of sftp-updater (it’s listed as 0.8.7 on the plugins page). After years of using this plugin, it now fails.
Starting at the update page, when I type the password, it fails with the error
Private key incorrect for user<br>Make sure that the key you are using is an RSA key and not a DSA key.
But we are not using keys, just passwords. I can still log in as that user, so there’s nothing wrong with SSH on the server.
Please help and thank you in advance.
Pammy
]]>Any plans for php 8.2 support? As far as I can tell, it’s working in an 8.2 environment, but is throwing a number of deprecation messages (e.g., “Deprecated: Creation of dynamic property Net_SFTP::$attributes is deprecated in?/var/www/html/example_site/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Net/SFTP.php?on line?445“)
]]>PHP 8.3.2
Unsupported operand types: string + string in /var/www/sites/sakhgupuny/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Net/SFTP.php:3569
3569 –> $start = strtok(microtime(), ‘ ‘) + strtok(”); // https://php.net/microtime#61838
3570 –> $result = $this->_send_channel_packet(NET_SFTP_CHANNEL, $packet);
3571 –> $stop = strtok(microtime(), ‘ ‘) + strtok(”);
replaced with plain microtime(true) to get numeric microtime directly
]]>PHP Warning: Trying to access array offset on value of type bool in /var/www/historicwoodfield.ca/html/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php on line 263, referer: https://historicwoodfield.ca/wp-admin/update-core.php
]]>I am trying to use your plugin on a new WordPress installation, with PHP 8.1. php-ssh2 is not installed (I know your plugin doesn’t use it). After I activate it, I go to the Plugins director and try to delete the ‘Hello Dolly’ plugin. The popup comes up, the dialog has all greyed boxes (because I’ve auto populated them in wp-config). I select SSH2 and then Proceed. The screen flashes and returns me to the same popup screen. I have enabled WP_DEBUG and php error logging, but nothing ever shows in either.
]]>The link on the Plugin page (https://www.ads-software.com/plugins/ssh-sftp-updater-support/) at “b) Others as detailed in the official WP codex” points to https://codex.www.ads-software.com/Editing_wp-config.php#WordPress_Upgrade_Constants
The correct link is: https://developer.www.ads-software.com/apis/wp-config-php/#wordpress-upgrade-constants
]]>We are using your plugin:- SSH SFTP Updater Support
we want to know if your plugin is compatible with PHP 8.1 or not.
We would love to know ASAP.
]]>Hello, recently i’ve been considering WP’s built-in FTP functionality for the purpose of remote uploading images from media library to the CDN service with a limited WP integration.
I’ve found about WP configs constants definitions that are supporting ‘FTP_CONTENT_DIR’ and ‘FTP_PLUGINS_DIR’ and so tried to define ‘FTP_UPLOADS’
by adding a new constant definition into:
wp-admin/includes/class-wp-filesystem-base.php
public function find_folder( $folder ) {
--
if ( stripos( $this->method, 'ftp' ) !== false ) {
$constant_overrides = array(
'FTP_BASE' => ABSPATH,
'FTP_CONTENT_DIR' => WP_CONTENT_DIR,
'FTP_PLUGIN_DIR' => WP_PLUGIN_DIR,
'FTP_UPLOADS' => WP_UPLOAD_DIR,
Afterwards i’ve set the wp-config.php:
//FTP
define('FS_METHOD', 'direct');
define('FTP_BASE', '/export/home/123-user/htdocs/uploads/');
//define('FTP_CONTENT_DIR', '/export/home/123-user/htdocs/');
define('FTP_UPLOADS', '/export/home/123-user/htdocs/uploads/');
//define('UPLOADS', 'uploads');
define('FTP_USER', '123-user');
define('FTP_PASS', 'password123');
define('FTP_HOST', '123-user.server.co');
/* That's all, stop editing! Happy publishing. */
No server errors but also no files transferred with the above customization.
Is there possibility that above technique could work with your plugin SSH SFTP Updater Support?
Any advice on this subject really appreciated, thank you regards
I’m preparing to upgrade php to version 8.0. We’re currently running 7.4. I ran the php compatibility tool (which oddly enough can only check up to 7.3), and it flagged a plugin – this one. The scan generated 49 errors.
I note that the plugin was last updated about 4 weeks ago, so it’s kind of hard to believe that the compatibility tool is accurate.
This is the entire report. What’s going on? Is this real? Will this plugin work if I upgrade to php 8.0?
FILE: /home/vvfhorg/public_html/blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/bootstrap.php
-----------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
-----------------------------------------------------------------------------------------------------------------
10 | WARNING | INI directive 'mbstring.func_overload' is deprecated since PHP 7.2
-----------------------------------------------------------------------------------------------------------------
FILE: /home/vvfhorg/public_html/blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Net/SFTP/Stream.php
-----------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
-----------------------------------------------------------------------------------------------------------------------
200 | WARNING | Global with anything other than bare variables is discouraged since PHP 7.0. Found ${$host}
-----------------------------------------------------------------------------------------------------------------------
FILE: /home/vvfhorg/public_html/blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/Random.php
-------------------------------------------------------------------------------------------------------------------------------------------------------
FOUND 5 ERRORS AFFECTING 2 LINES
-------------------------------------------------------------------------------------------------------------------------------------------------------
77 | ERROR | Function mcrypt_create_iv() is deprecated since PHP 7.1 and removed since PHP 7.2; Use random_bytes() or OpenSSL instead
77 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
119 | ERROR | Function mcrypt_create_iv() is deprecated since PHP 7.1 and removed since PHP 7.2; Use random_bytes() or OpenSSL instead
119 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
119 | ERROR | The constant "MCRYPT_DEV_URANDOM" is deprecated since PHP 7.1 and removed since PHP 7.2
-------------------------------------------------------------------------------------------------------------------------------------------------------
FILE: /home/vvfhorg/public_html/blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/Base.php
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FOUND 44 ERRORS AND 2 WARNINGS AFFECTING 26 LINES
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
651 | WARNING | Since PHP 7.0, functions inspecting arguments, like func_get_args(), no longer report the original value as passed to a parameter, but will instead provide the current value. The parameter "$method" was used, and possibly changed (by reference), on line 649.
829 | ERROR | Function mcrypt_generic_init() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
829 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
862 | ERROR | Function mcrypt_generic_init() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
862 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
865 | ERROR | Function mcrypt_generic() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
865 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
870 | ERROR | Function mcrypt_generic() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
870 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
879 | ERROR | Function mcrypt_generic() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
879 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
889 | ERROR | Function mcrypt_generic() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
889 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
892 | ERROR | Function mcrypt_generic_init() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
892 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1141 | ERROR | Function mcrypt_generic_init() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1141 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1169 | ERROR | Function mcrypt_generic() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1169 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1174 | ERROR | Function mcrypt_generic() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1174 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1183 | ERROR | Function mdecrypt_generic() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1186 | ERROR | Function mcrypt_generic_init() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1186 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1648 | ERROR | Function mcrypt_list_algorithms() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1648 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1727 | ERROR | Function mcrypt_module_close() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1727 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1728 | ERROR | Function mcrypt_module_close() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1728 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1733 | ERROR | Function mcrypt_module_close() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1733 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1846 | ERROR | The constant "MCRYPT_MODE_ECB" is deprecated since PHP 7.1 and removed since PHP 7.2
1847 | ERROR | The constant "MCRYPT_MODE_CBC" is deprecated since PHP 7.1 and removed since PHP 7.2
1849 | ERROR | The constant "MCRYPT_MODE_NOFB" is deprecated since PHP 7.1 and removed since PHP 7.2
1850 | ERROR | The constant "MCRYPT_MODE_STREAM" is deprecated since PHP 7.1 and removed since PHP 7.2
1853 | ERROR | Function mcrypt_module_open() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1853 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1854 | ERROR | Function mcrypt_module_open() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1854 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1860 | ERROR | Function mcrypt_module_open() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1860 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
1860 | ERROR | The constant "MCRYPT_MODE_ECB" is deprecated since PHP 7.1 and removed since PHP 7.2
1865 | ERROR | Function mcrypt_generic_init() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead
1865 | ERROR | Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
2558 | WARNING | Function create_function() is deprecated since PHP 7.2; Use an anonymous function instead
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
]]>
How do you change what port the updater is trying to use for SSH?
]]>Hi there!
I’ve had a report from a user of our plugin that a fatal error is being caused when trying to run it in conjunction with your plugin:
https://www.ads-software.com/support/topic/activation-impossible-fatal-error/
I’ve see some other posts in your support forum that allude to the same issue, and that the plugin author (me, in this case) is using the filesystem wrong, eg:
https://www.ads-software.com/support/topic/php-fatal-error-uncaught-error-12/
I’m hoping you could direct me to which part of the code is incorrect, as I though we are checking to see if things have failed before proceeding to write files etc…
Existing code for initialising the filesystem (we do things like creating a folder, and checking if that succeeded, and write a file, and check if that succeeded).
This is an extract:
global $wp_filesystem;
WP_Filesystem();
$filesystem = $wp_filesystem;
$dir_exists = $filesystem->exists( $cl_dir );
if ( ! $dir_exists ) {
$mk_dir_result = $filesystem->mkdir( $cl_dir ); // Try to create the folder
if ( ! $mk_dir_result ) {
// log error
if ( defined( 'WP_DEBUG' ) ) {
if ( WP_DEBUG === true ) {
error_log( esc_html__( "Custom Layouts: Unable to write folder, info:", 'custom-layouts' ) );
error_log( esc_html( $filesystem->errors->get_error_message() ) );
}
}
}
else {
$dir_exists = true;
}
}
Any help in resolving this would be appreciated ??
]]>My ISP updated PHP to version 8.1 recently. Since the update, the updater is not working anymore. It was working fine before. I know PHP 8.1 support for WP may not be official but it seems to me everything is working fine. I can just get no updates automatically any longer! Can we please get a version that supports PHP 8.1?! It’s been out now for half a year.
What I am getting is this:
“An automated WordPress update has failed to complete – please attempt the update again now.”
When I try to attempt the update manually I get:
“ERROR: There was an error connecting to the server, Please verify the settings are correct.”
Of course, none of the settings (FTP/SSH Username; FTP/SSH Password; Connection Type=SSH2) have changed.
]]>hello and good day
just came across this plugin – and i have to say. the description looks very very prominsing.
note: i am on a root server and the server admin enables me to use sftp-client (like filezilla and WinSCP [no SSH itself ) to do all kinds of upload to the server.
question: untill now i have difficulties to get a auto-update option for themes and plugins – since here we need to have the ftp-credentials (and method)
i am looking for a method to keep my WordPress install up-to-date and installing plugins in a hassle-free manner:
since it is not so easy if i server uses SFTP. i need a tool or a method to do this.
are there methods, ways and workaround for doing so – e.g. using phopseclib to remedy these deficiency!?
i have also had a look here: https://www.ads-software.com/support/article/editing-wp-config-php/#wordpress-upgrade-constants
Question: can i use your tool – the ��SSH SFTP Updater Support�� for WordPress uses phpseclib to remedy this deficiency.
To use it, after installing and activating the plugins, add the necessary constants early in the code in your wp-config.php:
a) define(‘FS_METHOD’, ‘ssh2’);
b) Others as detailed in the official WP codex
note – i am not on the SSH-level of access to the server. this means i do not have ssh-access- i only use sftp-clients – and subsequently i only have these credentials etc.
many thanks in advance for your help
ps: Background: well i have heard t hat many wordpress-uses are not able to update/upgrade their WordPress and plugins to a newer version without providing their FTP connection information. This is a difficult issue – since WordPress can��t write to the /wp-content folder directly.
Well: how to go round this issue:
a. one method is to define the FTP details in the wp-config.php file so WordPress will remember it.
b. write-access to /wp-content folder: another way and method is to provide WordPress with write access to the /wp-content folder by accessing the FTP root file and changing the folder file permission (CHMOD)
to 775 rather than the default 755 and 644.
But wait: there is a interesting workaround for doing so: we can do this by defining constant, FS_METHOD in the wp-config.php file. this way bypasses WordPress��s recurring prompts – and doing so we allow the wordpress auto-updates of the files to work.
a. Open /wp-config.php
– located at wordpress/wp-config.php
b. Insert FS_METHOD
write the following line of code to the wp-config.php file, just below every other line of code.
define('FS_METHOD','direct');
FS Method
what do you say to this workaround to this alternative method?
]]>Hello,
I installed plugin SSH SFTP Updater Support, I set some SSH credentials and then uninstalled. Now when I want to install any plugin I have this error The ssh2 PHP extension is not available even I have to fill some FTP credentials. Thank you for your suggestions in advance.
Does “ssh sftp Updater” plugin work with “Duo” two factor authentication?
It doesn’t seem to be working
Thanks
]]>Hello
I’m encountering a PHP Fatal error: Uncaught Error when updating Gravity Forms. According to Gravity Forms support it is a conflict with the SSH SFTP Updater Support plugin.
Call to a member function stat() on bool in /usr/share/wordpress/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php:262
Is this a known issue and what can I do to continue using both Gravity Forms and SSH SFTP Updater Support?
Thanks
]]>Hi. Good morning.
One question. I’m actually using this plugin but is the plug in compatible with PHP 8.1?
Thank you so much for your help.
Regards
]]>Hi, recently the “SSH SFTP Updater Support” started showing an error all of a sudden, it had to be deactivated so the admin could log in WP dashboard.
The full error message displayed was:
Fatal error: Uncaught Error: Call to a member function stat() on bool in /var/www/html/wordpress/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php:262 Stack trace: #0 /var/www/html/wordpress/wp-content/plugins/responsive-menu/v4.0.0/inc/classes/class-style-manager.php(121): WP_Filesystem_SSH2->is_dir() #1 /var/www/html/wordpress/wp-includes/class-wp-hook.php(301): RMP\Features\Inc\Style_Manager->save_style_css_on_file() #2 /var/www/html/wordpress/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters() #3 /var/www/html/wordpress/wp-includes/plugin.php(470): WP_Hook->do_action() #4 /var/www/html/wordpress/wp-content/plugins/responsive-menu/v4.0.0/inc/classes/class-rmp-migration.php(103): do_action() #5 /var/www/html/wordpress/wp-includes/class-wp-hook.php(303): RMP\Features\Inc\RMP_Migration->migrate() #6 /var/www/html/wordpress/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters() #7 /var/www/html/wordpress/wp-includes/plugin.php(470): WP_Hook->do_action() #8 /var/www/html/wordpress/wp-co in /var/www/html/wordpress/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php on line 262
We are using the latest 0.8.4 version. Any idea what could have caused this?
Thank you.
]]>Just received this email saying that WordPress found an error in one of my plugins, SSH SFTP Updater Support.
Page where the error was identified (https://www.****.com/wp-admin/admin.php?page=aioseo-tools)
WordPress version 5.8.1
Current theme: Newspaper (version 11.3.1)
Current plugin: SSH SFTP Updater Support (version 0.8.4)
PHP version 7.4.3
Error Details
================
An error of type E_ERROR was caused on line 253 of the file /var/www/***.com/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php. Error message: Uncaught Error: Call to a member function stat() on bool in /var/www/***.com/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php:253
Stack trace:
Stack trace:
#0 /var/www/***.com/wp-content/plugins/all-in-one-seo-pack/app/Common/Tools/BadBotBlocker.php(257): WP_Filesystem_SSH2->exists()
#1 /var/www/***.com/wp-content/plugins/all-in-one-seo-pack/app/Common/Traits/Helpers/Vue.php(284): AIOSEO\Plugin\Common\Tools\BadBotBlocker->getLogSize()
#2 /var/www/***.com/wp-content/plugins/all-in-one-seo-pack/app/Common/Admin/Admin.php(864): AIOSEO\Plugin\Common\Utils\Helpers->getVueData()
#3 /var/www/***.com/wp-includes/class-wp-hook.php(303): AIOSEO\Plugin\Common\Admin\Admin->enqueueAssets()
#4 /var/www/***.com/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters()
#5 /var/www/***.com/wp-includes/plugin.php(470): WP_Hook->do_action()
#6 /var/www/***.com/wp-admin/admin-header.php(102): do_action()
#7 /var/www/***.com/wp-admin/admin.php(239): require_once(‘/var/www/***..`
================
In the admin area of wordpress shows:
Warning: ftp_fget() expects parameter 1 to be resource, null given in /var/www/***.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 146
================
]]>After spending tremendous time to make this plugin work, I realized that SSH public/private keys have a myriad of different formats – just to name few: OpenSSH, ssh.com, RFC4716, PEM … Just to let you know, when this plugin asks you to paste your private key PEM format is expected. This means that your key needs to have a form like:
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,901B2323AB2234235180151
... (key contents) ...
-----END RSA PRIVATE KEY-----
Keys starting with “BEGIN OPENSSH PRIVATE KEY” seem not to be accepted.
To convert your private key from OpenSSH to PEM use:
cp .ssh/id_rsa .ssh/id_rsa.bak
ssh-keygen -p -m PEM -f .ssh/id_rsa
Type your passphrase 3 times and you will get the required key saved in .ssh/id_rsa (the old one will be backed up in .ssh/id_rsa.bak).
]]>Hello, I was using this plugin successfully with my previous WordPress site running on my own server: Nginx with PHP 5.6 (I think from memory) on Rasbian/Debian Wheezy. I rebuilt the server with Rasberry OS/Debian Buster and PHP 7.4.
Wordpress is working fine apart from this plugin. I recreated the SSH user and keys and believe these are okay as I can login outside of PHP with them.
The NGINX log shows:
2021/03/02 06:42:39 [error] 556#556: *15111 open() "/mnt/webfiles/websites/cabincontrol.tlcb.uk404.html" failed (2: No such file or directory), client: 10.5.248.122, server: cabincontrol.tlcb.uk, request: "GET /favicon.ico HTTP/1.1", host: "cabincontrol.tlcb.uk", referrer: "https://cabincontrol.tlcb.uk/heating.html"
2021/03/02 08:36:49 [error] 556#556: *35635 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to undefined function xml_parser_create() in /mnt/webfiles/websites/79th.tlcb.uk/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/RSA.php:1468
Stack trace:
#0 /mnt/webfiles/websites/79th.tlcb.uk/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/RSA.php(1785): Crypt_RSA->_parseKey()
#1 /mnt/webfiles/websites/79th.tlcb.uk/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php(97): Crypt_RSA->loadKey()
#2 /mnt/webfiles/websites/79th.tlcb.uk/wp-admin/includes/file.php(1861): WP_Filesystem_SSH2->connect()
#3 /mnt/webfiles/websites/79th.tlcb.uk/wp-admin/includes/class-wp-upgrader.php(193): WP_Filesystem()
#4 /mnt/webfiles/websites/79th.tlcb.uk/wp-admin/includes/class-plugin-upgrader.php(293): WP_Upgrader->fs_connect()
#5 /mnt/webfiles/websites/79th.tlcb.uk/wp-admin/includes/ajax-actions.php(4452): Plugin_Upgrader->bulk_upgrade()
#6 /mnt/webfiles/websites/79th.tlcb.uk/wp-includes/class-wp-hook.php(287): wp_ajax_upd" while reading response header from upstream, client: 10.5.248.124, server: 79th.tlcb.uk, request: "POST /wp-admin/admin-ajax.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.4-fpm.sock:", host: "79th.tlcb.uk", referrer: "https://79th.tlcb.uk/wp-admin/plugins.php"
I’m sure it’s a dependency I have not installed. I installed:
php7.4-ssh2
and is at version: 1.2+0.13-9+0~20210223.17+debian10~1.gbp17d23d
and
php-phpseclib
which is at version: 2.0.14-1
What am I missing?
thanks
]]>Error: The web server does not support sftp
]]>I’m getting a set of notices in the “Site Language” section of General Settings:
Notice: Trying to access array offset on value of type bool in /var/www/html/example/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php on line 263
Notice: Trying to access array offset on value of type bool in /var/www/html/example/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php on line 263
Notice: Trying to access array offset on value of type bool in /var/www/html/example/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php on line 258
Notice: Trying to access array offset on value of type bool in /var/www/html/example/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php on line 263
These look like PHP 7.4 issues, but I’m not certain how to resolve them. Any advice? Thanks!
]]>Is it possible to somehow allow WordPress to remember the FTP credentials so I can setup automatic updates, without the need to enter the SFTP password every time I need to update a theme or plugin?
]]>Hi David,
I am getting the following error when trying to activate the Mollie Ideal Plugin when having SSH SFTP updater plugin active.
Do you have a solution for this, or is the fault in the mollie-payments-for-woocommerce plugin ? i did post the error on their forum Click here
]]>Fatal error: Uncaught Error: Call to a member function stat() on boolean in /home/mydomain/public_html/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php:253 Stack trace: #0 /home/mydomain/public_html/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php(439): WP_Filesystem_SSH2->exists(��/home/dutchshop����) #1 /home/mydomain/public_html/wp-content/plugins/mollie-payments-for-woocommerce/mollie-payments-for-woocommerce.php(66): WP_Filesystem_SSH2->find_folder(��/home/dutchshop����) #2 /home/mydomain/public_html/wp-content/plugins/mollie-payments-for-woocommerce/mollie-payments-for-woocommerce.php(58): deleteWPTranslationFiles() #3 /home/mydomain/public_html/wp-includes/class-wp-hook.php(287): mollie_wc_plugin_activation_hook(��) #4 /home/mydomain/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(��, Array) #5 /home/mydomain/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #6 /home/mydomain/public_html/wp-admin/plugins.php(193): in /home/mydomain/public_html/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php on line 253
I am assuming this is an issue with my theme, but I want to make sure, and if you could possibly help out and see what the theme is doing wrong that I can be like hey, you’re doing this wrong (like not checking something with the filesystem first)
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.5.1
Current theme: Avada Child (version 1.0.0)
Current plugin: SSH SFTP Updater Support (version 0.8.2)
PHP version 7.4.11
Error Details
=============
An error of type E_ERROR was caused in line 262 of the file /opt/websites/wp-com/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php. Error message: Uncaught Error: Call to a member function stat() on bool in /opt/websites/wp-com/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php:262
Stack trace:
#0 /opt/websites/wp-com/wp-admin/includes/file.php(1438): WP_Filesystem_SSH2->is_dir()
#1 /opt/websites/wp-com/wp-content/themes/Avada/includes/class-fusion-builder-demos-importer.php(304): unzip_file()
#2 /opt/websites/wp-com/wp-content/themes/Avada/includes/class-fusion-builder-demos-importer.php(115): Fusion_Builder_Demos_Importer->extract_demo_data_zip()
#3 /opt/websites/wp-com/wp-content/themes/Avada/includes/class-avada-init.php(198): Fusion_Builder_Demos_Importer->__construct()
#4 /opt/websites/wp-com/wp-includes/class-wp-hook.php(287): Avada_Init->init_fb_demos_importer()
#5 /opt/websites/wp-com/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#6 /opt/websites/wp-com/wp-includes/plugin.php(478): WP_Hook->do_action()
#7 /opt/websites/wp
Aloha, we are wondering if you folks have been able to get this plugin working with the new “update by uploading ZIP files” feature in WordPress 5.5:
https://www.ads-software.com/support/wordpress-version/version-5-5/#security
Basically, WordPress 5.5 includes support for manually updating themes and plugins to a new version by uploading a ZIP file.
However, we are running into a problem where it keeps asking for credentials when trying to update a theme or plugin by uploading a ZIP file.
Example:
in wp-admin single site mode, go to:
1. Plugins > Installed Plugins
2. Click Add New button
3. Click Upload Plugin button
4. Click Choose File and navigate to your ZIP file
5. Click Install Now
6. Enter your SFTP/SSH credentials via this plugin
7. If the version numbers differ between the installed version and the ZIP file, you will see a new screen (as of WordPress 5.5) comparing them and asking whether you want to proceed.
8. Click Replace current with uploaded. You will be taken back to step #6, and will loop between steps 6-8 indefinitely without actually updating.
See screenshot for what step #7 looks like:
]]>
I am using WordPress with ec2 of aws.
Since ec2 only supports sftp, not ftp, uploading is not possible by adding plug-ins in the wordpress dashboard.
So I tried to manually upload the plugin.
However, it was uploaded normally in Filezilla, but the plugin does not appear in the dashboard.
I want to know which part to check. ??
]]>I am working on two Woocommerce stores in WordPress for development purposes. I use the SSH SFTP Updater Support plugin, but when I updated WordPress to 5.5, SSH SFTP Updater Support plugin will not let the products edit area work properly in Woocommerce. When I deactivate the SSH SFTP Updater Support plugin, the product edit areas works properly. I need both to work properly.
I get this error message in an email:
“Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, SSH SFTP Updater Support.
Error Details
=============
An error of type E_ERROR was caused in line 257 of the file /home/**********/public_html/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php. Error message: Uncaught Error: Call to a member function stat() on boolean in /home/**********/public_html/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php:257”
I have numerous other WordPress sites that are not Woocommerce. They do not have any issues with the SSH SFTP Updater Support plugin after updating WordPress. Any ideas why this is only affecting Woocommerce stores? Any help would be appreciated. Thank you!
]]>I ran the PHP Compatibility Checker against PHP 7.3, and got the following warnings.
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/class-wp-filesystem-ssh2.php
——————————————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
——————————————————————————————————————–
32 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
——————————————————————————————————————–
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Math/BigInteger.php
———————————————————————————————————————
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
———————————————————————————————————————
254 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
———————————————————————————————————————
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Net/SSH2.php
————————————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————————————–
857 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
————————————————————————————————————–
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Net/SFTP.php
————————————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————————————–
291 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
————————————————————————————————————–
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/Hash.php
—————————————————————————————————————-
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
—————————————————————————————————————-
154 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
—————————————————————————————————————-
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/RC4.php
—————————————————————————————————————
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
—————————————————————————————————————
165 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
—————————————————————————————————————
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/Base.php
———————————————————————————————————————————-
FOUND 0 ERRORS AND 40 WARNINGS AFFECTING 21 LINES
———————————————————————————————————————————-
497 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
763 | WARNING | Function mcrypt_generic_init() is deprecated since PHP 7.1; use OpenSSL instead
763 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
796 | WARNING | Function mcrypt_generic_init() is deprecated since PHP 7.1; use OpenSSL instead
796 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
799 | WARNING | Function mcrypt_generic() is deprecated since PHP 7.1; use OpenSSL instead
799 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
804 | WARNING | Function mcrypt_generic() is deprecated since PHP 7.1; use OpenSSL instead
804 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
813 | WARNING | Function mcrypt_generic() is deprecated since PHP 7.1; use OpenSSL instead
813 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
823 | WARNING | Function mcrypt_generic() is deprecated since PHP 7.1; use OpenSSL instead
823 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
826 | WARNING | Function mcrypt_generic_init() is deprecated since PHP 7.1; use OpenSSL instead
826 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1072 | WARNING | Function mcrypt_generic_init() is deprecated since PHP 7.1; use OpenSSL instead
1072 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1100 | WARNING | Function mcrypt_generic() is deprecated since PHP 7.1; use OpenSSL instead
1100 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1105 | WARNING | Function mcrypt_generic() is deprecated since PHP 7.1; use OpenSSL instead
1105 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1114 | WARNING | Function mdecrypt_generic() is deprecated since PHP 7.1; use OpenSSL instead
1117 | WARNING | Function mcrypt_generic_init() is deprecated since PHP 7.1; use OpenSSL instead
1117 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1579 | WARNING | Function mcrypt_list_algorithms() is deprecated since PHP 7.1; use OpenSSL instead
1579 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1658 | WARNING | Function mcrypt_module_close() is deprecated since PHP 7.1; use OpenSSL instead
1658 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1659 | WARNING | Function mcrypt_module_close() is deprecated since PHP 7.1; use OpenSSL instead
1659 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1664 | WARNING | Function mcrypt_module_close() is deprecated since PHP 7.1; use OpenSSL instead
1664 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1784 | WARNING | Function mcrypt_module_open() is deprecated since PHP 7.1; use OpenSSL instead
1784 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1785 | WARNING | Function mcrypt_module_open() is deprecated since PHP 7.1; use OpenSSL instead
1785 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1791 | WARNING | Function mcrypt_module_open() is deprecated since PHP 7.1; use OpenSSL instead
1791 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
1797 | WARNING | Function mcrypt_generic_init() is deprecated since PHP 7.1; use OpenSSL instead
1797 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
———————————————————————————————————————————-
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/Rijndael.php
——————————————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
——————————————————————————————————————–
286 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
——————————————————————————————————————–
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/TripleDES.php
———————————————————————————————————————
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
———————————————————————————————————————
201 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
———————————————————————————————————————
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/RSA.php
—————————————————————————————————————
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
—————————————————————————————————————
487 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
—————————————————————————————————————
FILE: ……../blog.vvfh.org/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Crypt/Random.php
———————————————————————————————————————————
FOUND 0 ERRORS AND 4 WARNINGS AFFECTING 2 LINES
———————————————————————————————————————————
74 | WARNING | Function mcrypt_create_iv() is deprecated since PHP 7.1; use OpenSSL instead
74 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
113 | WARNING | Function mcrypt_create_iv() is deprecated since PHP 7.1; use OpenSSL instead
113 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1 – use openssl (preferred) or pecl/mcrypt once available instead.
———————————————————————————————————————————