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

Wrong uri for Exoscale Object Storage #8579

Closed
cyberduck opened this issue Feb 12, 2015 · 1 comment
Closed

Wrong uri for Exoscale Object Storage #8579

cyberduck opened this issue Feb 12, 2015 · 1 comment
Assignees
Labels
bug low priority s3 AWS S3 Protocol Implementation worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

8441508 created the issue

Hello,

the base uri encoded in Duck and Cyberduck for Exoscale object storage access is:

  • ppsos.exo.io

This is Preproduction address. The default address should be:

  • sos.exo.io
@cyberduck
Copy link
Collaborator Author

@dkocher commented

The connection profile referenced from (https://trac.cyberduck.io/wiki/help/en/howto/exoscale) has set the default hostname to sos.exo.io.

@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 low priority s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants