[Drive Destroyed]

I seem to have accidentally destroyed a drive yesterday. Not sure how I did it, and wasn't "drunk-admining" either lol :/ Only thing I can figure is perhaps I mis-clicked something and didn't realize.

 

So I have a feature request, perhaps this isn't how it happened, maybe it's just a fluke, I don't know. But can we perhaps separate these in the dialog? Maybe, move the destroy to a different place entirely? Or what I think would be better is to put a fail-safe in here where there is a "Protect drive from Destruction" feature, where unless a box unchecked, you simply CAN'T destroy the drive, unless you go in and positively un-check that box, THEN go and destroy it. Ideally, these would be in two separate locations (sort of like OUs in Active Directory).

 

The data wasn't critical, and I haven't suffered a loss, so I'm not concerned. But I am a little puzzled how it happened. 

[429.....]

Looks like it's working as normal for me at this point. 

[Amazon Cloud Drive: HTTP Status 429 errors]

I have this issue as well on ACD. No new chunks have been uploaded since yesterday. I reauthorized the drive, and that works fine but it still fails to mount. 

[Cluster Resizing]

Other than reformatting and starting over, is there a way to resize the clusters on a volume? I know that Acronis Disk Director can do it, but Acronis doesn't detect the cloud drive when I launch it. 

 

Any help is appreciated!

 

[Amazon Cloud Drive - Why is it not supported?]

I downloaded / installed the 768 build, and I was able to successfully reauthorize my drives. Keep up the great work guys!

[amazon api key not working]

This isn't a "Hey guys it's still broke wtf!" It's a "Hey guys, they changed stuff, check this out". So chill man.

 

But Yeah, the drive I'm using is fairly old; I'm using it for backup. I've got about 5 TB of data uploaded across 4 drives. /shrug, if that makes a difference. 

[amazon api key not working]

It looks like amazon's developer console has changed slightly (again). There is now a link in the "Security Profile Management" that says "Login with Amazon". Clicking this link will enable one of your security profiles to have the previously missing "Web Settings" tab.

 

It does ask for some new URL, a "Consent Privacy Notice URL" in addition to the "Return URL". I don't know if this privacy notice url really does anything other than displaying a privacy notice somewhere down the line, but filling it in with any seemingly random URL appears to make it happy. 

 

After getting the "Web Settings" tab to show up, you do get a Client ID and Client Secret. Entering them into Stablebit CloudDrive and clicking "Connect" (on an already existing volume, I was trying to reattach) I get this error message from stablebit (in a web broswer, with the crying emoticon):

 

 

Controller: Redirect

 

Action: AmazonCloudDrive

 

Error: Sorry, but the provider did not send us a valid secret code so we can't continue.

 System.Exception: Sorry, but the provider did not send us a valid secret code so we can't continue. at StableBitWeb.RedirectController.OAuth2Model.Validate() at StableBitWeb.RedirectController.AmazonCloudDrive(OAuth2Model Model) at lambda_method(Closure , ControllerBase , Object[] ) at System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass42.b__41() at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass8`1.b__7(IAsyncResult _) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<>c__DisplayClass39.b__33() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.b__49() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.b__36(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<>c__DisplayClass2a.b__20() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.b__22(IAsyncResult asyncResult)

[amazon api key not working]

Should we anticipate these issues getting resolved eventually? Or have you guys abandoned developing for the amazon cloud drive provider?

 

I'm OK with using an experimental provider and having hiccups, but I don't really want to start down this road if it's going to be abandoned in the near term.