I'm just wondering.... could this not be an ancient
Filezilla bug which has put it's head up again?
I don't use Filezilla myself.
Which gives me even more the feeling that it's a Filezilla issue, because normally ssl is not generated for ip. I know that ZeroSSL can create for ip, but only for http traffic. So to me this is very odd.
On the other hand, it could also be that pure-ftpd still not supports PROT P which makes it a pure-ftpd issue.
If it's working fine using ip, does it also work fine using the hostname of the server (like server.somedomain.com)?
