ACD BAN/Alternatives discussion (error HTTP code 429)

#1

I’m getting the following error for EVERYTHING i do on ACD, copy, mount, even ls. I called ACD support and they can’t see the problem.

(error HTTP code 429: "429 Too Many Requests": response body: "{\"message\":\"Rate exceeded\"}")

I’ve seen this error before but only intermittently. And google isn’t really helping. I’m hoping someone here has had this issue before and can help. Please :worried:

2 Likes
Rclone stalls on ACD upload: "done, 0 Bytes/s, ETA: 0s" and must be restarted
Amazon Drive Encryption
#2

I just started getting these errors around 20 minutes ago too. I can download from the website but everything else fails. I can’t offer a solution but there is some comfort in knowing you are not alone.

2017/04/18 13:59:15 DEBUG : pacer: low level retry 4/10 (error HTTP code 429: "429 Too Many Requests": response body: "{\"message\":\"Rate exceeded\"}")

#3

I’ll add a big “ditto” here. I have my rclone config on two servers (in the same location) and I’m getting the response on both machines. Even simple commands like “rclone lsd acd:” don’t complete. And with the -vv option, I get repeating 429 errors.

#4

I was uploading and the final (largest) file has been stuck on this for an hour or so

2017/04/18 14:27:03 DEBUG : pacer: Rate limited, sleeping for 3m30.635967561s (11 consecutive low level retries)
2017/04/18 14:27:03 DEBUG : pacer: low level retry 1/10 (error HTTP code 429: "429 Too Many Requests": response body: "{\"message\":\"Rate exceeded\"}")`
#5

Same thing here, been going on the last hour. Nothing working right now.

#6

Mine seems ok. Regional? Im in Florida, USA

#7

Utah, USA, but I get the same result with VPN connections to LA and Seattle.

#8

Same here guys 20 minutes ago started with this crap. Amazon is pure shit it is a shame not a service ! Europe Netherlands.

#9

Nope it is worldwide. Amazon is a shame.

#10

I have tried from Utah and California, both getting Rate Exceeded error.

#11

I just downloaded 50GB in the last few. Wierd. working fine @ 100Megabits.

#12

We should all raise a huge complaint and ask a refund ! Let’s do a collective one against those lame bastard !

1 Like
#13

What’s weird, is the web interface is working. (Not that I can play encrypted movies from the web interface.) I thought I’d gotten my account frozen, but I logged in fine to the web.

#14

calisro where are u located ?

#15

Florida USA. Im not sure my endpoint its US based.

#16

Same thing here, thank god I saw this, I thought I broke something…

1 Like
#17

ah wait. there she blows. I can download data from my mount but not issue API calls.

└─> rclone -vv ls robacd-cryptp:
2017/04/18 14:41:14 DEBUG : rclone: Version “v1.36-22-gbc25190β” starting with parameters [“rclone” “-vv” “ls” “robacd-cryptp:”]
2017/04/18 14:41:14 DEBUG : pacer: Rate limited, sleeping for 666.145821ms (1 consecutive low level retries)
2017/04/18 14:41:14 DEBUG : pacer: low level retry 1/10 (error HTTP code 429: “429 Too Many Requests”: response body: “{“message”:“Rate exceeded”}”)
2017/04/18 14:41:14 DEBUG : pacer: Rate limited, sleeping for 235.010051ms (2 consecutive low level retries)
2017/04/18 14:41:14 DEBUG : pacer: low level retry 2/10 (error HTTP code 429: “429 Too Many Requests”: response body: “{“message”:“Rate exceeded”}”)
2017/04/18 14:41:15 DEBUG : pacer: Rate limited, sleeping for 287.113937ms (3 consecutive low level retries)
2017/04/18 14:41:15 DEBUG : pacer: low level retry 3/10 (error HTTP code 429: “429 Too Many Requests”: response body: “{“message”:“Rate exceeded”}”)

but directly from my cached mount works fine. Sorry its messed up here too. That probably why the website works. Different methods for API calls I guess.

#18

Yes web works for me too dude. Still not working I start to be really annoyed by this I will raise a complaint now with the customer support

#19

Same here! Using the NA-endpoint (North-American), but my server resides somewhere in Germany. Getting the exact same issue, can’t even LS or mount my drives without getting the message.

#20

I won’t be unmounting until this is fixed… I hope… ! Glad I set the cache to expire in 100 days. :slight_smile: