File Upload Fails at 100 percent

[TheKevster101]

This ticket system is to report bugs and feature requests. For support, visit the help page first.

• If you have trouble connecting to a server or your login credentials are not valid, try to resolve the issue with the assistance of your hosting service provider. Any such ticket will be closed with a resolution of thirdparty.

Describe the bug
File Upload reaches 100% completion and uploading stops. The STOP button doesn't work (on any uploads). When attempting to close Cyberduck, I get an error saying "Transfer in progress - There are files currently being transferred. Quit Anyway?" After force quit and restart, the files show as Transfer Incomplete with 0B of 0B. I have left one case running for over 24 hours and it did not complete.

To Reproduce
Steps to reproduce the behavior:

1. Drag file to the desired folder on the cyberduck interface
2. Wait for upload to complete
3. See that it isn't complete but reads 100% and isn't uploading anymore.
4. Try again...

Expected behavior

File Upload reaches 100% completion and uploading stops. The STOP button doesn't work (on any uploads). When attempting to close Cyberduck, I get an error saying "Transfer in progress - There are files currently being transferred. Quit Anyway?" After force quit and restart, the files show as Transfer Incomplete with 0B of 0B. I have left one case running for over 24 hours and it did not complete.

Screenshots

Desktop (please complete the following information):

• OS: macOS Monterey
• Version 12.6.7

Log Files
Please include the log file. You can reach the logging output in Preferences → Connection.
cyberduck.log

Additional context

Thank you for any and all help!!!

[dkocher]

The error message from S3 is Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. ¹

<?xml version="1.0" encoding="UTF-8"?>
<Error>
    <Code>RequestTimeout</Code>
    <Message>Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.</Message>
    <RequestId>BRT7TG6EA5539GJS</RequestId>
    <HostId>5b2IQQNMLVviGGL/4e91FpbeY9/Z/pUqglHvH6e97J5CzEqXjKMnX3MDNIRgZmiRSyr1B02+h+U=</HostId>
</Error>

Footnotes

1. ↩