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

DNS resolution failure when reading bucket location #11678

Closed
cyberduck opened this issue May 18, 2021 · 15 comments
Closed

DNS resolution failure when reading bucket location #11678

cyberduck opened this issue May 18, 2021 · 15 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

50b180c created the issue

Seit dem Update auf 7.9.0 taucht der Fehler im Anhang auf.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please provide the log output.

@cyberduck
Copy link
Collaborator Author

ba20f9c commented

Hi,

I have exactly the same problem, since version 7.9.0.

I'm connecting to a self-hosted Scality Ring with S3.
The problem happens only when I set the bucket name in the "Path" field of the bookmark panel.

Jean-Rémy

@cyberduck
Copy link
Collaborator Author

ba20f9c commented

On the above screenshot, what I greyed out is the name Cyberduck trying to resolve, which is:
<bucket name (default Path)>.

I think that's the root cause of the problem.
In my case I can connect to but not to .

@cyberduck
Copy link
Collaborator Author

ba20f9c commented

Note: the last line of my %APPDATA%\cyberduck\cyberduck.log is from 2021-04-22.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 jrlacharnay]:

On the above screenshot, what I greyed out is the name Cyberduck trying to resolve, which is:
<bucket name (default Path)>.

I think that's the root cause of the problem.
In my case I can connect to but not to .

I cannot reproduce the problem testing against a Scality S3 installation. Please provide the log output.

@cyberduck
Copy link
Collaborator Author

ba20f9c commented

Replying to [comment:7 dkocher]:

Replying to [comment:4 jrlacharnay]:

On the above screenshot, what I greyed out is the name Cyberduck trying to resolve, which is:
<bucket name (default Path)>.

I think that's the root cause of the problem.
In my case I can connect to but not to .

I cannot reproduce the problem testing against a Scality S3 installation. Please provide the log output.

@cyberduck
Copy link
Collaborator Author

ba20f9c commented

Replying to [comment:7 dkocher]:

I cannot reproduce the problem testing against a Scality S3 installation. Please provide the log output.

Like I said above, my %appdata%\Cyberduck\cyberduck.log seems to not be updated anymore (last updated on 2021-04-22). Is there any setting to activate, or has the log file moved to a new location?

I even created a %appdata%\Cyberduck\default.properties with "logging=debug" in it, no change.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you please try if still see this issue with the current snapshot build by updating from within Cyberduck in ''Preferences → Update →
Automatically check for updates in → Snapshot Builds''.

@cyberduck
Copy link
Collaborator Author

ba20f9c commented

Yes, same issue with version 7.9.1 (34964).
And still no logs.

@cyberduck
Copy link
Collaborator Author

adc75a0 commented

The debug log works on my side without any issues (version 7.9.1 (34966)).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As a workaround please connect using the S3 (Deprecated path style requests) profile.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Relates to #10888 with fix in 586fc49.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #10956.

@cyberduck
Copy link
Collaborator Author

ba20f9c commented

Thanks, the workaround works perfectly!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In ddedab4.

@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.
Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants