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
Comments
Please provide the log output. |
Hi, I have exactly the same problem, since version 7.9.0. I'm connecting to a self-hosted Scality Ring with S3. Jean-Rémy |
On the above screenshot, what I greyed out is the name Cyberduck trying to resolve, which is: I think that's the root cause of the problem. |
Note: the last line of my %APPDATA%\cyberduck\cyberduck.log is from 2021-04-22. |
Replying to [comment:4 jrlacharnay]:
I cannot reproduce the problem testing against a Scality S3 installation. Please provide the log output. |
Replying to [comment:7 dkocher]:
|
Replying to [comment:7 dkocher]:
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. |
Can you please try if still see this issue with the current snapshot build by updating from within Cyberduck in ''Preferences → Update → |
Yes, same issue with version 7.9.1 (34964). |
The debug log works on my side without any issues (version 7.9.1 (34966)). |
As a workaround please connect using the S3 (Deprecated path style requests) profile. |
Thanks, the workaround works perfectly! |
Seit dem Update auf 7.9.0 taucht der Fehler im Anhang auf.
Attachments
Screenshot 2021-05-19 182028.png
(23.9 KiB)cyberduck.PNG
(10.3 KiB)The text was updated successfully, but these errors were encountered: