This looks like a firewal issue. ftp tries to change the port after starting the encrypted connection and this port seems to be closed on your server. You should consider to define a port range in pure-ftpd and then pen this port range in yur firewall as well.

So pure-ftpd does not seem to listen to any other port than 21 (that does not change when I define a PassivePortRange setting).

Click to expand...

Thats ok, as the other ports are only used dynamically for the running ftp conection. there are no listeners on these ports as the connection is initiated trough port 21 and then handed over to the other port.

I defined a PassivePortRange between 50110 and 50310, re-checked the firewall and restarted pureftpd.

FTPs is now partly working, but still cannot be used. This is what is happening:

1. I start the connection from the FTP client, filezilla in this case. I use explicit TLS (port 21)
2. Filezilla asks me to accept the certificate, which I do.
3. The connection is initiated, and port negotiation takes place. When I execute "netstat -npl | grep ftp" I get