• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

After upgrade to Plesk 12, FTP explicite TLS is broken

MoritzKK

New Pleskian
Unfortunately the encrypted FTP transfer is broken since Plesk upgraded to version 12.
There are two cases:
  • Passiv FTP without encryption on port 21: everthing workes fine.
  • Passiv FTP with explicite TLS encryption on port 21: The control connection can be established by using TLS on port 21 but the data transfer can't be established by using passive mode (ETIMEDOUT - Connection attempt timed out)

I thought it could be a firewall issue but i'm currently unable to diable the firwall for testing since the configuration of the firewall is unreachable after upgrading to plesk 12! See second thread: http://forum.parallels.com/showthread.php?306397-ERROR-Firewall-configuration
 
It is certainly a firewall issue since the connection to the given random DATA port is possible if the firewall is deactivated at all.
Strangely the problem only appears if TLS is enabled!
 
We encountered the same problem.
A solution would be really good.

Clients connecting will throw errors:
425 Unable to build data connection: no route to host
 
Back
Top