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

OpenSwift Connection with Keystone V3 #11088

Closed
cyberduck opened this issue Jun 26, 2020 · 3 comments
Closed

OpenSwift Connection with Keystone V3 #11088

cyberduck opened this issue Jun 26, 2020 · 3 comments
Labels
bug core thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Jun 26, 2020

8745fd5 created the issue

Hello I can't open an OVH swift container with keystone v3.

I joined a screenshot wich show the credentials and parameters I'm using.

Can you help me ? I have 7 cyberducks licences that I use for cloud backups and I'm really annoyed by this because all my backups are down.

Best regards, Romain.


Attachments

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 29, 2020

@dkocher commented

Please refer to our documentation.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 29, 2020

8745fd5 commented

Hello,

I can't open an OVH private openstack container in SWIft (keystone v3) with Cyberduck or mountain duck.

I followed what's writen on the wiki page : wiki:help/en/howto/ovh I tried the OVH preconfigured signet but without success.

Can you help me please ?

PS : I have 7 paid cyberduck licenses that I do my clients backups with.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 22, 2020

3c57a9b commented

Doesn't work for me either anymore with Cyberduck 7.7.2.
I always get a 404 when trying to connect. I did follow the documentation, and tried regenerating a password, as well as creating a new user in the OpenStack console, to no avail. Last successful connection was June 7th, with Cyberduck 7.4.0 (when testing #10566).

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug core thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant