Sftp client class you will "always" get the
SftpException object - if the error was caused by a
IOException or anything else, the original exception will be stored in
I wrote "always" because you can get
ArgumentException, but those are obvious.
We also try to map well known socket errors to a human readable messages. E.g. socket error code 11001 = "No such host is known."
However, you can always access the inner
SocketException and read the additional related socket error data for yourself.
Now, to the issue of the log showing errors, but no error is thrown on the client and the file is being uploaded successfully (if I understand it correctly).
The error is probably caused at the server side only, after the file upload is finished and the server and client did not communicate properly to close the socket.
Can you please try it with the latest version of Rebex Tiny SFTP Server?
If the issue is still present, can you please try it with the latest version of Rebex client as well?
To diagnose the issue, we would need logs from both sides (of the same session). If you want us to analyze the issue, please create VERBOSE log on both sides and send it to firstname.lastname@example.org, so we can see what was happening on both client and server (which commands followed by which ones with timestamps).