ACD BAN/Alternatives discussion (error HTTP code 429)

aaaand again

httping -l -G -c 3 "https://cdws.eu-west-1.amazonaws.com/drive/v1/nodes?filters=kind%3AFOLDER+AND+isRoot%3Atrue"
PING cdws.eu-west-1.amazonaws.com:443 (/drive/v1/nodes?filters=kind%3AFOLDER+AND+isRoot%3Atrue):
connected to 54.239.32.36:443 (375 bytes), seq=0 time=49972.44 ms
connected to 54.239.34.70:443 (375 bytes), seq=1 time=22705.82 ms
connected to 54.239.32.36:443 (375 bytes), seq=2 time=59308.86 ms
--- https://cdws.eu-west-1.amazonaws.com/drive/v1/nodes?filters=kind%3AFOLDER+AND+isRoot%3Atrue ping statistics ---
3 connects, 3 ok, 0.00% failed, time 134989ms
round-trip min/avg/max = 22705.8/43995.7/59308.9 ms

unwillingly switched over to my gdrive mounts until i can see that these issues are fixed :\

I can feel your pain :slight_smile:


and mtr 54.239.39.139

Unfortunately ACD has become more unreliable… If that was even possible. I likely will not renew.

1 Like

Hopefully it will be fixed, once rclone implements serialized DB I will switch to gdrive as main, but still plan to keep ACD for backup.

Who knows if tomorrow google or amazon does something stupid and completely limits usefulness of their drives.

Months ago hubic was a great and then ultra fuckup with bandwith limiting.

like clockwork - ACD http roundtrip times keep rising from 110ms to 25000ms and more around 19:00 (MEST) , again…

1 Like

Yup during this time it always deteriorate

few minutes later

Rate exceeded strikes back!

Been having this error. HTTP code 429: “429 Too Many Requests”. Anything I can do?

I am experiencing this as well.
¯_(ツ)_/¯

Me too. Hopefully amazon didnt ban rclone like acd_cli.

acd_cli has been banned?

Also experiencing 429s.

@sixhoursago : see this thread https://github.com/yadayada/acd_cli/pull/562

acd_cli_oa was banned so there is no way for it to authenticate to ACD anymore.
Since the only other way to get it to auth is to build your own authentication app and Amazon does not allow API access to anyone anymore (your app must be whitelisted after an approval process and I was already denied), it’s effectively impossible to get acd_cli to authenticate anymore (unless you find someone that has an existing auth service and is willing to share).
I suspect that with acd_cli tanking a few days ago, everyone migrated over to rclone and since rclone mount spams the API far more than acd_cli did, Amazon may have noticed a significant increase in usage and shut it down…

or it’s just another ACD API outage… crossing fingers.

1 Like

I’m getting the 429 just on a mount request.

I get very consistent 429s on an rclone ls acd:/… It seems like it may have been banned…

As you may notice, this thread is almost 1 month old and started when people had this EXACT same issue. I believe it was fixed within 24 hours last time.

Unless you have inside knowledge, why spread “fud” about you thinking rclone is banned? just because of the unfortunate acdcli situation? Let’s just wait and see before freaking out.

in the mean time, those of you considering moving from acd to gdrive, may want to check out multicloud. I am currently using multicloud transferring my files from acd and getting decent speeds to gdrive… the fastest i have ever seen actually.

I’m leaning toward rclone getting extra users due to the aci_cli thing and so may have gone over the currently setup limit for ACD.

The one potential bad thing though is I just tried goodsync and it is working fine so doesn’t look to be a global issue with the CLI but could still be too many current overall requests and ACD will need to inrease the limit for the security key.

We’ll just have to wait and see.

damn. fingers crossed