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

Jump to bottom

Logging in to vault.ecloud.co.uk #9228

Closed
cyberduck opened this issue Jan 25, 2016 · 4 comments
Closed

Logging in to vault.ecloud.co.uk #9228

cyberduck opened this issue Jan 25, 2016 · 4 comments
Labels
bug s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

63a3e29 created the issue

Hi,

I have used the below credentials to login, we have previously logged in using these credential as another user but now they will not work

To Setup the CyberDuck program for the first time and link it to the eVault, the username and password details you need are :-
Your Unique Access and Secret Keys
Your access and secret keys act as a username and password. You may configure contact-level access to the eCloud Vault and its API keys through the contact management screen.
Host	vault.ecloud.co.uk
Please ensure that the secret key found above is not human-readable in your application

Can you please assist

Kind regards
Anisha
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please contact your web hosting service provider for assistance.

@cyberduck
Copy link
Collaborator Author

63a3e29 commented

Replying to [comment:1 dkocher]:

Please contact your web hosting service provider for assistance.

Hi

We are there support and we provide everything. We have contacted our third party who look after the cloud servers but they said to come to you

Kind regards
Anisha

@cyberduck
Copy link
Collaborator Author

63a3e29 commented

Can this be reopened please

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This works just fine here. Make sure to select S3 as the protocol to use. Now please request your credentials to be changed as these have been exposed in this issue tracker.

@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.
Assignees
No one assigned
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck