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

v8.2.1 S3 - "cannot read bucket location" #12746

Closed
pulberg opened this issue Jan 5, 2022 · 5 comments · Fixed by #12764
Closed

v8.2.1 S3 - "cannot read bucket location" #12746

pulberg opened this issue Jan 5, 2022 · 5 comments · Fixed by #12764
Assignees
Milestone

Comments

@pulberg
Copy link

@pulberg pulberg commented Jan 5, 2022

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
After upgrading cyberduck to v8.2.1 I am no longer able to connect to S3 bookmarks.

From the error popup, it looks like cyberduck is prepending the url with the bucket name and trying to resolve that -

mybucket-name.my.s3url.com

In my bookmarks the url is - https://my.s3url.com:9021/mybucket-name

Here is an excerpt from the debug logs (edited to remove org info)-

2022-01-05 10:46:49,919 [Thread-41] WARN ch.cyberduck.core.threading.BackgroundCallable - Failure BackgroundException{class=class ch.cyberduck.core.exception.ResolveFailedException, file=null, message='Cannot read bucket location.', detail='mybucket-name.my.s3url.com.', cause='java.net.UnknownHostException: mybucket-name.my.s3url.com'} running background task

Desktop (please complete the following information):

  • OS: macOS
  • Version: 12.1
@dkocher
Copy link
Contributor

@dkocher dkocher commented Jan 6, 2022

Make sure the URI with the bucket name included is not resolvable over DNS to allow us to automatically switch to path-style requests or explicitly use the connection profile S3 (Deprecated path style requests) available in Preferences → Profiles.

@dkocher dkocher closed this Jan 6, 2022
@pulberg
Copy link
Author

@pulberg pulberg commented Jan 6, 2022

@dkocher I think you missed the part where I said this behavior happened after I upgraded, this was all working fine previously I will run the checks you suggested, but i will also revert to v8.x to confirm the behavior, this should not be closed yet.

@pulberg
Copy link
Author

@pulberg pulberg commented Jan 6, 2022

I tested as you suggested, and my URI including the bucket name is not resolvable. So it would appear that the "automatic" switching to path-style in cyberduck is not working. Did something significant change from 8.1.1 to 8.2.x regarding this ability?

@pulberg
Copy link
Author

@pulberg pulberg commented Jan 6, 2022

@dkocher I tested the s3 functionality using my existing s3 bookmarks -

v8.0.0 - works
v8.0.2 - works
v8.1.0 - works
v8.1.1 - works
v8.2.0 - not working
v8.2.1 - not working

It appears that something changed in v8.2.x such that cyberduck no longer automatically switches to path-style requests.

@dkocher dkocher reopened this Jan 6, 2022
@dkocher
Copy link
Contributor

@dkocher dkocher commented Jan 6, 2022

Most probably a regression of 7f69ba1.

@dkocher dkocher added the bug label Jan 6, 2022
@dkocher dkocher added this to the 8.2.1 milestone Jan 7, 2022
dkocher added a commit that referenced this issue Jan 7, 2022
@dkocher dkocher linked a pull request that will close this issue Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants