WPIntell

Source evidence

SSH 8.1 support

SSH SFTP Updater Support · support · 2022-04-26T15:52:00+00:00

mixedsentiment
mediumseverity
0.85relevance
5replies
Evidence onlycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

1 / 1 rows with source links

100.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

0 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
menloperk resolved
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. Hi, A test update of a theme on an install PHP 8.1.5 worked fine for me. I verified that this plugin was being use by first deliberately using a wrong password (which was then logged by the SSH/SFTP server), and then trying again with the correct server (which then logged the successful login). The underlying phpseclib library is also supported by its author on PHP 8.1, and we have no other reports of issues. Therefore, you will need to do further investigation into what is happening on your setup. Perhaps your PHP 8.1 install has different configuration somewhere to your PHP 8.0 setup which is preventing the network connection. Is there no further text after the error message given above? (The code has lines to output further information). David We are coming from version PHP 7.x, not 8.0. It’s still not working where I now see the below error message when trying to update to latest version of WP: Notice: Cannot connect to xxx.yyy.com:22. Error 60. Operation timed out in /usr/home/renek/public_html/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Net/SSH2.php on line 1201 Strangely enough nothing was changed on the SSH IP whitelisting when the update to 8.1 was performed where it was working before just fine and it is not working any longer. It seems obvious that a connection is blocked somehow. Can you tell me who is initiating the connection to our server? I hope it is not some external client using our credentials trying to setup a connection to our server?? Is it from localhost? Please can you give some more context? Btw, if we are setting up the connection from external then what site is it as it will be blocked if not explicitly whitelisted. > “Operation timed out” That means that there was no network connectivity in between your PHP install and the SSH server. To investigate that you will need to ask the operator of your webserver (i.e. where the PHP install is) to help you – it’s not something that the plugin has influence over or access to, and the setup of particular networks is not something that I as plugin author have any special insight into. David It appeared to be not only an upgrade to PHP8.1 but also a change in IP address where the alias for the hostname was removed from the server. Changed the config to connect to localhost:22 now and it’s back working. Thanks for your support. Case closed.

Comments

5 shown
David Anderson / Team Updraft 2022-04-30T11:48:00+00:00

Hi, A test update of a theme on an install PHP 8.1.5 worked fine for me. I verified that this plugin was being use by first deliberately using a wrong password (which was then logged by the SSH/SFTP server), and then trying again with the correct server (which then logged the successful login). The underlying phpseclib library is also supported by its author on PHP 8.1, and we have no other reports of issues. Therefore, you will need to do further investigation into what is happening on your setup. Perhaps your PHP 8.1 install has different configuration somewhere to your PHP 8.0 setup which is preventing the network connection. Is there no further text after the error message given above? (The code has lines to output further information). David

menloperk 2022-05-06T07:41:00+00:00

We are coming from version PHP 7.x, not 8.0. It’s still not working where I now see the below error message when trying to update to latest version of WP: Notice: Cannot connect to xxx.yyy.com:22. Error 60. Operation timed out in /usr/home/renek/public_html/wp-content/plugins/ssh-sftp-updater-support/phpseclib/Net/SSH2.php on line 1201 Strangely enough nothing was changed on the SSH IP whitelisting when the update to 8.1 was performed where it was working before just fine and it is not working any longer. It seems obvious that a connection is blocked somehow. Can you tell me who is initiating the connection to our server? I hope it is not some external client using our credentials trying to setup a connection to our server?? Is it from localhost? Please can you give some more context?

menloperk 2022-05-06T07:51:00+00:00

Btw, if we are setting up the connection from external then what site is it as it will be blocked if not explicitly whitelisted.

David Anderson / Team Updraft 2022-05-09T16:35:00+00:00

> “Operation timed out” That means that there was no network connectivity in between your PHP install and the SSH server. To investigate that you will need to ask the operator of your webserver (i.e. where the PHP install is) to help you – it’s not something that the plugin has influence over or access to, and the setup of particular networks is not something that I as plugin author have any special insight into. David

menloperk 2022-05-10T20:36:00+00:00

It appeared to be not only an upgrade to PHP8.1 but also a change in IP address where the alias for the hostname was removed from the server. Changed the config to connect to localhost:22 now and it’s back working. Thanks for your support. Case closed.