New SFTP plugin available now

[ghisler(Author)]

What about my other question about the login method?

[JOUBE]

I edit my last answer to slow for your look at it. Please have a look at it now.

[JOUBE]

How about releasing the beta 6, which has been stable for a year, as a release? Then one could "play around" with subsequent versions without any problems and without disturbing standard users. After all, SFTP is now a mandatory part of the TC. Then you (and I) wouldn't have to keep referring to the Beta 6 version in the forum whenever problems arise.

[ghisler(Author)]

You mean you don't have problems with beta 6, only with beta 7? If this is the case, can you try
1. Use beta 7 with the following option added to the server section:
prefmethod1=ecdsa-sha2-nistp256
2. Use beta 6 with the following option added to the server section:
prefmethod1=ssh-ed25519

This way I could find out whether the problem is the beta version or the host key method.

[JOUBE]

Sorry, b5 not b6. b6 is - as ii wrote - horrible. b7 with the fix of b6 makes the problem

So release b5.

[ghisler(Author)]

1. Which Windows version are you using? I tried with a lot of servers, and never got the error you get:
- Fedora 40
- Fedora 41
- Alma Linux 8
- Raspberry PI OS Bookworm/PI5
- Raspbian/PI3
- Ubuntu 22.04 LTS
And some providers where I don't know the used operating system:
- Sourceforge.com
- Strato.de
- telekom.de
- Hetzner Storage Box

2. Maybe it would be easier for me if you just sent me the host name of one of your servers? I do not need a user name or password because the key exchange happens before the login. You can send it to cghisler (GMail).

[JOUBE]

Newest w11 The issue rised with Fedora42 on an intel cpu (N....) and with debian on a powerfull Raspi.. Important: first connect after a restart hours ago.

I never see this issue before over many years.. The issue comes with b7.

[JOUBE]

The W11 24H2 system here from which the connection is to be established has an Intel Core I5. Just to add this to the previous post.

What's missing is extended logging, which can often be generated with the -vv option (or similar). The library doesn't provide that? I actually assume it does. Please enable such a debug logging for the connaction process.

Everything after version B5 has now become a true beta again, which is a good thing. In contrast, Please note, version B5 is stable and the recommended version, which is the required version.

[Schultheis]

With beta version 7, the upload to my homepage is finally as fast as my maximum upload speed (use SCP for transfers, UploadBlockSize=46720), but the displayed transfer rate and the expected remaining time are utopian: My upload runs at 3 MB/s, the TC shows 53,324 kbytes/s, i.e. almost 18 times faster. And instead of 2 minutes, I have to wait more than half an hour for a larger file. Is it just me with this blatant display error?

[Schultheis]

One more question: I very often get the error “SCP upload error SCP_PROTOCOL (28)” when experimenting. It doesn't occur on my desktop computer at the moment, but on my notebook all the time, even though I have configured everything the same. Both times Windows 11 pro on the latest version.

[ghisler(Author)]

Beta 8 is available now:
https://www.totalcommander.ch/beta/sftpplug310b8.zip
The source code is available here:
https://www.totalcommander.ch/beta/sftpplug_src310b8.zip

I have enabled debug logging in the libssh2.dll now in beta 8. By default, it only logs errors (debuglog=128). But you can get more details by adding
debuglog=508
to the file sftpplug.ini below the connection name (in square brackets), e.g.

Code: Select all

[Connection name]
debuglog=508
server=192.168.0.1
...

The value of debuglog is a sum of LIBSSH2_TRACE_ values from libssh2.h:
2 Transfers
4 Key exchange
8 Authentication
16 Connection
32 SCP
64 SFTP
128 Errors
256 Public key
512 Low level socket functions

The suggested value 508 excludes transfers and low level socket functions.

2JOUBE
I was able to reproduce the error once with Fedora42, so it could be a bug or incompatibility with their server. Unfortunately I was unable to reproduce it after enable debug logging, so I couldn't investigate it any further. If you can reproduce it, please send me the debug log to my gmail address (cghisler at gmail dot com).

2Schultheis
Are you using a Hetzner storage box? SCP transfers on that box are seriously broken:
1. It doesn't support single quoted names when a file contains spaces, only double quotes. Beta 8 should address that.
2. Uploads no longer work after downloading a single file, you need to disconnect and reconnect. No fix for that so far.

[Schultheis]

2Schultheis
Are you using a Hetzner storage box? SCP transfers on that box are seriously broken:
1. It doesn't support single quoted names when a file contains spaces, only double quotes. Beta 8 should address that.
2. Uploads no longer work after downloading a single file, you need to disconnect and reconnect. No fix for that so far.

It's a connection to my Homepage at IONOS. Where can I find the log file?

[ghisler(Author)]

You need to enable logging for plugins in Total Commander, menu Configuration - Options - FTP (this also handles all plugins).

[Schultheis]

In the log I see "Read-only file system". This error only occurs on my notebook, I can upload a file on the desktop computer. How can this be? What could possibly be the cause of the error on my notebook? Why is the file system on IONOS not writable from the notebook?

[Schultheis]

Download does not work, too!