• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

After upgrade to Plesk 12, FTP explicite TLS is broken

M

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
 
You must log in or register to reply here.

Similar threads

R
Issue Unable to connect to FTP via
Replies
4
Views
798
kilowhisky65
K
A
Issue FTP - Insecure server, it does not support FTP over TLS.
Replies
3
Views
699
Alban Staehli
A
P
Resolved Remote FTP Backup fails after upgrade to Plesk Obsidian 18.0.68 Update 1
Replies
8
Views
851
embrem
E
Gh()st
Issue Remote Storage FTP(S) Issue
Replies
1
Views
1K
paulrm
P
C
Issue Errors with Plesk scheduled backups
Replies
2
Views
1K
cmartinez127
C
Back
Top