Skip to content
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

Unable to resume a copy to S3 after network disconnection #11554

Closed
cyberduck opened this issue Jan 21, 2021 · 1 comment
Closed

Unable to resume a copy to S3 after network disconnection #11554

cyberduck opened this issue Jan 21, 2021 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 21, 2021

54a7b97 created the issue

When copying a few GB of files to an S3 bucket, if the network connection is lost and then reconnected, a dialog box appears with a retry option, however it never managed to re-connect to the S3 bucket, so it's not possible to complete the copy. After clicking retry I get a dialog saying "Connection failed", "DNS lookup for s3.amazonaws.com failed...."

Even though at the time, DNS resolution is working correctly on the machine.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 16, 2021

@dkocher commented

This is possibly caused due to caching somewhere in the stack. Try to restart Cyberduck prior resuming the transfer.

@cyberduck cyberduck closed this Feb 16, 2021
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant