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

Server hostname changes resulting DNS failure #10292

Closed
cyberduck opened this issue Mar 30, 2018 · 2 comments
Closed

Server hostname changes resulting DNS failure #10292

cyberduck opened this issue Mar 30, 2018 · 2 comments
Assignees
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Mar 30, 2018

57cbee5 created the issue

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:

external image

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

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 2, 2018

57cbee5 commented

It appears that this happens when the region key in the profile is different than what is in the endpoint URL. For instance

  • If the server endpoint is namespace.compat.us-ashburn-1.oraclecloud.com and region is us-ashburn-1, this will problem will not happen.

  • If the server endpoint is namespace.compat.us-phoenix-1.oraclecloud.com and region is us-ashburn-1, this problem will happen.

Problem is persistent across macOS and Windows.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Sep 4, 2018

@dkocher commented

I cannot reproduce this problem with [milestone:6.7.3 6.7.3].

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants