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
Hello,
first I'd link to thank all the developers and the community surrounding CyberDuck. I'm a professional webdesigner and I couldn't live without it.
Now let's go straight to the topic.
Many users around the web have a problem with Cyberduck when dealing with cheap hosting service (e.g. aruba and many others for Italy). Uploading folders with several files and subfolders always results in "Read Timeout Error". In the log you can see the server not responding at any command given by the client. Eg. type 1, change folder.. no response. Some misconfigured hosts automatically start ignoring a connection sending too many commands at a too high rate.
And no change in Cyberduck configuration seem to solve this.
The problem disappears using FtpFox.
The difference is that when a server is not responding anymore FtpFox, after a quite short timeut, sends a QUIT command and then immediately logs again in, restarting the upload from the point it was interrupted without first checking all the uploaded files modification dates. And this makes the magic: everything is uploaded correctly!
I really hope this can help.
The text was updated successfully, but these errors were encountered:
Hello,
first I'd link to thank all the developers and the community surrounding CyberDuck. I'm a professional webdesigner and I couldn't live without it.
Now let's go straight to the topic.
Many users around the web have a problem with Cyberduck when dealing with cheap hosting service (e.g. aruba and many others for Italy). Uploading folders with several files and subfolders always results in "Read Timeout Error". In the log you can see the server not responding at any command given by the client. Eg. type 1, change folder.. no response. Some misconfigured hosts automatically start ignoring a connection sending too many commands at a too high rate.
And no change in Cyberduck configuration seem to solve this.
The problem disappears using FtpFox.
The difference is that when a server is not responding anymore FtpFox, after a quite short timeut, sends a QUIT command and then immediately logs again in, restarting the upload from the point it was interrupted without first checking all the uploaded files modification dates. And this makes the magic: everything is uploaded correctly!
I really hope this can help.
The text was updated successfully, but these errors were encountered: