New SFTP plugin available now

[Schultheis]

Now I've copied wcx_ftp.ini and sftpplug.ini from my desktop to my notebook: Same error! Cannot copy from my notebook to my homepage.

[Schultheis]

Now I have the error on my desktop, too. I didn't change anything. I saw the error with Bety 7 and now with Beta 8. Filezilla does work!

[Schultheis]

The plugin is not stable when connecting to my homepage. Sometimes it works, sometimes not.

[Schultheis]

If I can't copy anything to the homepage, I can still delete a file on the homepage. I imagine a read-only file system to be different!

[ghisler(Author)]

This can have two reasons:
1. You used different credentials (user name+password), or
2. You set a different start directory (by specifying it behind the server name, e.g. ionos.com/home/schultheis)

[Schultheis]

This can have two reasons:
1. You used different credentials (user name+password), or
2. You set a different start directory (by specifying it behind the server name, e.g. ionos.com/home/schultheis)

Both are always identical. Currently it does not work on any computer.

[ghisler(Author)]

Do you only get this for SCP transfers? Filezilla doesn't use SCP when connecting via SFTP.

[Schultheis]

I get it with and without SCP.

[JOUBE]

Beta 8 is available now:

I now have time to install b8 and will enable extended logging.

Please note, it is important to release a version with the last updates, specially with the speeding up transfer features of the year 2024, to prevent requests about this point, like in the past in the forum.

SFTP is nowadays an important essential part of Tc in professional environments, and not an appendage, as you might think when you have it as plugin.

[JOUBE]

The plugin is not stable when connecting to my homepage. Sometimes it works, sometimes not.

I can not actually confirm anything like this with the SFTP plugin, but perhaps the new extended logging will help to find the problem.

Additional:

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.

https://www.google.de/search?q=scp+fehler+28
Error 28 in the context of SFTP or SCP (Secure Copy Protocol) usually refers to an error that occurs when there is not enough stack space in a program to complete an operation.

Maybe to many programms running in background?

[Schultheis]

Here is the relevant part of the log file:

[libssh2] 1863.055928 Conn: channel_read() wants 1 bytes from channel 1/1 stream #0
[libssh2] 1863.055928 Conn: channel_read() wants 1 bytes from channel 1/1 stream #0
[libssh2] 1863.055928 Conn: channel_read() wants 1 bytes from channel 1/1 stream #0
[libssh2] 1863.055928 Conn: channel_read() wants 1 bytes from channel 1/1 stream #0
[libssh2] 1863.055928 Conn: 43 bytes packet_add() for 1/1/0
[libssh2] 1863.055928 Conn: increasing read_avail by 43 bytes to 43/2097151
[libssh2] 1863.055928 Conn: channel_read() got 1 of data from 1/1/0
[libssh2] 1863.055928 Conn: channel_read() wants 42 bytes from channel 1/1 stream #0
[libssh2] 1863.055928 Conn: channel_read() got 42 of data from 1/1/0 [ul]
[libssh2] 1863.055928 SCP: got 01 scp: /sftpplug.ini: Read-only file system

[libssh2] 1863.055928 Failure Event: -28 - failed to send file

But I'm able to delete files!

[JOUBE]

Which user are you connecting as? Which checkboxes are checked in the connection's options? Which attributes should be set (644?)? This error 28 is just a result of the supposedly(?) write-protected file system.Therefore, I think the miscommunication can be found far earlier in the log. Please simply email the entire log to ghisler(author), whom he mentioned in a recent post to me in this thread.

[JOUBE]

2ghisler(author). After setting 508 for a few connections and running some initial tests, I'm fairly certain that the error doesn't occur when extended debug logging is enabled. It's actually a timing issue, which is easily resolved simply by writing the log to a file (open file, write, close). So, somewhere in the connection process itself, even without logging, a slightly longer wait for a response from the server must be set. This can probably be passed in when calling the corresponding function in the lib.

[ghisler(Author)]

2JOUBE
Try disabling FTP logging in Configuration - Options - FTP. Then open an ftp or sftp connection and keep it open in the background to see the 2 line log window. This way you should be able to see the log messages without writing them to disk.

2Schultheis
Maybe scp somehow escapes the home directory jail and tries to write the file to the actual root directory?

[Schultheis]

2Schultheis
Maybe scp somehow escapes the home directory jail and tries to write the file to the actual root directory?

How should I recognize this? I always see the correct directory as the target directory, from which I can also delete files. Have you already looked at the log file?