Cyberduck Mountain Duck CLI

#9228 closed defect (worksforme)

Logging in to vault.ecloud.co.uk

Reported by: Anisha Owned by:
Priority: normal Milestone:
Component: s3 Version: 4.7.3
Severity: normal Keywords:
Cc: Architecture:
Platform: Windows 7

Description (last modified by dkocher)

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

Change History (5)

comment:1 follow-up: Changed on Jan 25, 2016 at 5:10:05 PM by dkocher

  • Resolution set to thirdparty
  • Status changed from new to closed

Please contact your web hosting service provider for assistance.

comment:2 in reply to: ↑ 1 Changed on Jan 25, 2016 at 5:22:26 PM by Anisha

Replying to 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

comment:3 Changed on Jan 26, 2016 at 10:01:00 AM by Anisha

  • Resolution thirdparty deleted
  • Status changed from closed to reopened

Can this be reopened please

comment:4 Changed on Jan 26, 2016 at 10:11:27 AM by dkocher

  • Description modified (diff)

comment:5 Changed on Jan 26, 2016 at 10:14:04 AM by dkocher

  • Component changed from core to s3
  • Description modified (diff)
  • Resolution set to worksforme
  • Status changed from reopened to closed
  • Summary changed from Logging in to Logging in to vault.ecloud.co.uk

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.

Note: See TracTickets for help on using tickets.