CURLE_RECV_ERROR FFS v11.2 on Windows 10

Discuss new features and functions
Posts: 9
Joined: 31 Oct 2020

pschait

I've installed and set a source on FTPS server and destination on local USB attached disk.
Once the compare is started every arount 20 second I get:
CURLE_RECV_ERROR: OpenSSL SSL_read: Connection was reset, errno 10054 [curl_easy_perform]

The source folder is on a linux based system of around 1.5TB
The source FTP server is proftpd
The TLS OPENSSL based.

The error message is constatly shown every around 20 seconds. Forcing to click on 'retry' till the next error message.

FFS is quite good and useful software but I suspect it's lacking of stability on CURL or another library.
What can I do? Is there any stability difference compared with the 'donation' version?
Can I try the 'donation' version if it solves the above issue? I'm happy to donate for a working FTPS sync with FFS.

Kind regards.
User avatar
Site Admin
Posts: 7211
Joined: 9 Dec 2007

Zenju

The error code could be a clue:
10054 = WSAECONNRESET = "An existing connection was forcibly closed by the remote host."
Posts: 9
Joined: 31 Oct 2020

pschait

You're right. FYI: with FileZilla everything's fine (till now).
Could be something related to CURL?
Googling a bit I've found this https://curl.haxx.se/mail/lib-2017-07/0071.html maybe it could be related?
Posts: 9
Joined: 31 Oct 2020

pschait

I need to correct myself regarding the FileZilla transfer. The error appear also on FileZilla with ECONNABORTED message. So both application behave the same way, confiming the source of the problem on remote host.
The big difference between the two programs is that FileZilla doest stop, instead it goes ahead with the transfer and put the failed transfer in the 'uncompleted trasfer tab' giving the user the possibility to manually reprocess filed transfer in the trasfer queue.
Is it possible to put in FFS a mechanism to automatically go ahead if a trasfer fail? (AuomaticRetry Checkmark?)
Posts: 9
Joined: 31 Oct 2020

pschait

I've installed v.11.3 and found in the filter an automatic retry and set to 2 seconds.
This option solves the mentioned problem. Hope this could be helpful to somebody else.