• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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