You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi folks, we have used cyberduck for a while with no issues at all. This week hover we are experiencing this I/O Error: Illegial sftp Packet Len:34944. I tested with 4.2.1 and a older version 4.1.2 and both error in the same way. I suspect this si not a cyberduck error but it shows as one. What could be causing this? Is there a way in cyberduck to fix this problem wether its a cyberduck issuer not?
We apreciate the help - BTW I am testing on Mac OSX 10.7 and 10.6 - 2 different machines obviously.
Sending a screenshot of the error.
Thanks
Bill
Thanks for the response. Someone had seen this before at our head office and removed many of the files in the specific sftp folder, problem has gone! So it seems too many files in the destination caused this to happen. How many is to many is an interesting question at the moment.
Thanks for the response. Someone had seen this before at our head office and removed many of the files in the specific sftp folder, problem has gone! So it seems too many files in the destination caused this to happen. How many is to many is an interesting question at the moment.
Thanks
Bill
Please report this error to the server vendor as well as I suspect it to be a server software bug.
Hi folks, we have used cyberduck for a while with no issues at all. This week hover we are experiencing this I/O Error: Illegial sftp Packet Len:34944. I tested with 4.2.1 and a older version 4.1.2 and both error in the same way. I suspect this si not a cyberduck error but it shows as one. What could be causing this? Is there a way in cyberduck to fix this problem wether its a cyberduck issuer not?
We apreciate the help - BTW I am testing on Mac OSX 10.7 and 10.6 - 2 different machines obviously.
Sending a screenshot of the error.
Thanks
Bill
Attachments
Cyberduck.png
(73.5 KiB)The text was updated successfully, but these errors were encountered: