You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running Cyberduck on Windows for an S3 compatible endpoint results in DNS failure. Debugging the problem indicates that the connected server is different than the specificed server in configuration. Oddly, this problem does not happen on Mac.
See below screenshot:
Note that configured server is ilkertemir.compat.objectstorage.us-ashburn-1.oraclecloud.com but popup specifies ilkertemir.compat.objectstorage.s3-us-ashburn-1.oraclecloud.com as attempted server (not clear where s3- comes from, this does not happen on Mac).
Running Cyberduck on Windows for an S3 compatible endpoint results in DNS failure. Debugging the problem indicates that the connected server is different than the specificed server in configuration.
Oddly, this problem does not happen on Mac.See below screenshot:
Note that configured server is ilkertemir.compat.objectstorage.us-ashburn-1.oraclecloud.com but popup specifies ilkertemir.compat.objectstorage.s3-us-ashburn-1.oraclecloud.com as attempted server (not clear where s3- comes from, this does not happen on Mac).
This example uses the following configuration file: https://svn.cyberduck.io/trunk/profiles/OCI%20Object%20Storage%20(us-ashburn-1).cyberduckprofile
The text was updated successfully, but these errors were encountered: