CURLE_PARTIAL_FILE: server did not report OK, got 451

[nhldata]

I have a server that's syncing local files over FTP to an external server (using TLS 1.2) not under my control. This has been working fine for months. Then suddenly I started getting errors on certain file-transfers last week. The error is...

Cannot write file "ftp://[REMOVED]".
CURLE_PARTIAL_FILE: server did not report OK, got 451
451 0.011 seconds (measured here), 1.39 Mbytes per second [curl_easy_perform]


Testing the FTP transfers manually via third party software (Filezilla + TotalCommander) works fine.

I've tried to disable local firewall (ESET + Defender). No difference.

Disabled / Enabled (tested both) "Fail-safe file copy". No difference.

I update to latest version of FreeFileSync (Version 11.26 64bit) on friday. No difference.

Anyone got any suggestions /ideas?

[therube]

Oh, only a WAG, but in your instance, maybe --tlsv1.2 needs to be specifically passed?

(Now, how to do that, that's a different matter?)

[Zenju]

451 = "Requested action aborted. Local error in processing. " https://en.wikipedia.org/wiki/List_of_FTP_server_return_codes

One would probably need to look at the FTP server logs to find out which "local error" exactly has happened.