New SFTP plugin available now

[ghisler(Author)]

Yes, I have checked your log. You can see that the plugin sends scp '/filename' because the SFTP server sends paths relative to the base directory. If scp interprets this as an absolute path, it can't write there. Could you send me a log for a failed transfer with scp disabled too, please?

[Schultheis]

It is in the same place with the same name. However, there was no error message this time. Should I try to get an error again without SCP?

[Schultheis]

Another observation: I no longer receive a log file, although it is configured. I don't know why I was able to create a log file in the first place.
After restarting the TC, a log is generated again.

[Schultheis]

And now I have a log file for an error-free transmission with scp: sftp_mit_SCP.log

[Schultheis]

Finally sftp_ohne_SCP_mit_Fehler.log

[ghisler(Author)]

Unfortunately I haven't received anything yet via e-mail. Could you send it again to my GMail address, please? cghisler at gmail dot com. Thanks!

[ghisler(Author)]

Beta 9 is available now:
https://www.totalcommander.ch/beta/sftpplug310b9.zip
The source code is unchanged because I only made changes to the libssh2 dll:
1. I have reduced the overhead from debug logging, in the hope that the login error can be reproduced with it now.
2. By user request, I have added support for login with password+second factor in separate messages, used by the Bitvise SSH server.

[JOUBE]

1. I have reduced the overhead from debug logging, in the hope that the login error can be reproduced with it now.

Still the same option debuglog=508? I have enabled logging to file again, sorry, but I need it by some reasons. I haven't get the error in the meantime (even at the time I do not log to file), but I haven't connected in the meantime to so many servers, that are rebooted shorttime before.

[ghisler(Author)]

Yes, same debuglog value. The beta reduces calls to the debug function for disabled logging types.
Or you could use debuglog=132 (errors + key exchange only) to reduce the debugging lines in the log.

Maybe I should just keep the logging functions? They don't seem to have a negative impact on transfer speed when not adding debuglog, and they fix the timing(?) problem.

[Schultheis]

Apparently I can't provoke an error without SCP.

[Schultheis]

Still not working with SCP. Log will follow by e-mail.

[JOUBE]

Maybe I should just keep the logging functions? They don't seem to have a negative impact on transfer speed when not adding debuglog, and they fix the timing(?) problem.

Yes, of cause, independent of the timing(?) problem, it is a must to have the option to enable this extended debug logging.

[JOUBE]

Still not working with SCP. Log will follow by e-mail.

is this not that what Hetzner answered. Scp is not working at port 22. Because of error in implementation of there Server? What is with port 23?

[Schultheis]

With “Use SCP for everything” there seem to be no errors. But there is another shortcoming: After logging in, I always end up in the root directory of the server and I don't see any way to automatically switch to the correct directory, as is done without the option.

[ghisler(Author)]

2Schultheis
Oh, that explains it, it's as I suspected! SFTP seems to expect directories relative to your home folder, while SCP expects directories relative to the root of the system.

don't see any way to automatically switch to the correct directory

Either double click/press Enter on "~" in the list to go to the home directory. Or change the configuration of the connection from
your_server_name
to
your_server_name/home/your_user_name