[Cyberduck-trac] [Cyberduck] #11678: DNS resolution failure when reading bucket location
Cyberduck
trac at cyberduck.io
Wed May 26 15:03:42 UTC 2021
#11678: DNS resolution failure when reading bucket location
------------------------+-------------------------
Reporter: demoki2020 | Owner: dkocher
Type: defect | Status: assigned
Priority: normal | Milestone: 7.9.1
Component: s3 | Version: 7.9.0
Severity: normal | Resolution:
Keywords: | Architecture:
Platform: |
------------------------+-------------------------
Old description:
> Seit dem Update auf 7.9.0 taucht der Fehler im Anhang auf.
New description:
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.
--
Comment (by jrlacharnay):
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)>.<server name>
> >
> > I think that's the root cause of the problem.
> > In my case I can connect to <server name> but not to <bucket>.<server
name>
>
> I cannot reproduce the problem testing against a Scality S3
installation. Please provide the [wiki:help/en/support#LoggingOutput log
output].
--
Ticket URL: <https://trac.cyberduck.io/ticket/11678#comment:8>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list