A user writes with an error they have received while connecting to their FTPS server.
Bad encoding: wrong tag (expected 48 but read 10)
This is an error that occurs while parsing the server certificate that is sent back from the FTPS server. We couldn't figure out why it was happening, as the certificate the user sent us (which was the same certificate the server is using) parsed correctly. Our conclusion was that the server or the network was somehow corrupting the certificate.
After a few days the user responded with:
I have the problem sorted out, sorry for consuming so much of your time when the problem was not at all related to edtftpj-pro.
Anyways, I would like to share the solution, you were so right that when the server was sending the certificate it was getting altered , we have a firewall Checkpoint SmartDefense which has the FTP Bounce attack prevention on with the action "Monitor Only" but unfortunately it was not only monitoring but also changing the packet(seems to be a bug in SmartDefense).
