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

Getting "Listing directory / failed." error on all accounts #10253

Closed
cyberduck opened this issue Feb 27, 2018 · 2 comments
Closed

Getting "Listing directory / failed." error on all accounts #10253

cyberduck opened this issue Feb 27, 2018 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 27, 2018

655a51a created the issue

Haven't had to use Cyberduck for a while - when I started it today to prepare for a client demo, all configured accounts are returning a dialog box error: "Listing directory / failed." "Connect to s3.amazonaws.com:443 [s3.amazonaws.com/54.231.72.58] failed: Operation not permitted (connect failed). The connection attempt was rejected. The server may be down, or your network may not be properly configured.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2018

655a51a commented

This morning I noticed a pending Cyberduck update to 6.4.2, which I did just before updating MacOS to 10.13.3. I haven't run Cyberduck in a few weeks, but tried to run it just after my system came back up. All my configured accounts were returning the error in the description - it is unusable as things stand now, unclear why.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2018

@dkocher commented

Duplicate for #10237. Version 6.4.3 is now available in the Mac App Store fixing the issue with “connect failed” errors when attempting to connect due to missing codesigning entitlements. Unfortunately, this was caused by a bug in the Mac App Store processing and signing of application submissions.

Loading

@cyberduck cyberduck closed this Feb 27, 2018
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 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