New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: S3 Server "Failed to Respond" Following 26 GB Upload #8697
Comments
Do you get the error message in the Transfer or in the Browser window? |
Replying to [comment:2 dkocher]:
The Transfer window. Thanks! |
Set the hidden setting |
Replying to [8697 dag02005]:
|
Thanks for the fast reply! I quit out of Cyberduck, and in the Terminal, I entered...
After relaunching Cyberduck, I tried the upload again and the error still happened. |
Please post the transcript from the log drawer of the Transfers window. Choose ⌘-L on Mac or right-click the toolbar from the Transfers window and choose Log on Windows |
Sure thing. I tried to upload it again to reproduce the problem, and it gave a more complex, drawn-out version of the bug. Here's the transcript of the end...
|
Looks like the
and also update to the latest snaphot build. |
Hello,
Big fans of Cyberduck! For work, it's very important that we be able to upload files >10GB to our S3 server. Cyberduck worked great for this on our old system, but on a new MacPro with Yosemite, we keep getting a perplexing error message.
Every time the upload is almost finished (99% or more) it gives us an error message that server "Failed to respond". This happens every time. Oddly, if I hit refresh the entire file does appear to be on the server, but I'm not sure if it's complete and functional. I've included the transcript below...
Thank you. Keep up the great work, and let us know if there's any info you need from us!
The text was updated successfully, but these errors were encountered: