Rate limited by Amazon

Hi there!

I’m using Amazon’s Cloud Drive via crypt with Plex.

I first have to say that when it works it’s awesome.

The ‘only’ problem I have is that 9 out of the 10 times I do something I get 500 Internal Server Error's. I get them when I start a movie, try to seek through a movie and when analyzing my library.
If I’m watching/starting a movie and I get the error the movie stops and Plex says “There is a problem with playing the item” and marks the item as “Unavailable”.

Here is a more detailed error:
rclone mount --read-only --allow-other --debug-fuse --dump-headers -v acdcrypt: /storage/acd

2017/01/17 14:23:40 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2017/01/17 14:23:40 HTTP RESPONSE (req 0xc......)
2017/01/17 14:23:40 HTTP/1.1 500 Internal Server Error
Content-Length: 30
Connection: keep-alive
Content-Type: application/vnd.error+json
Date: Tue, 17 Jan 2017 19:23:40 GMT
Server: Amazon-Cloud-Drive
X-Amzn-Requestid: ............

2017/01/17 14:23:40 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2017/01/17 14:23:40 pacer: Rate limited, sleeping for 660.772719ms (1 consecutive low level retries)
2017/01/17 14:23:40 pacer: low level retry 1/10 (error HTTP code 500: "500 Internal Server Error": response body: "{\"message\":\"Internal failure\"}")
2017/01/17 14:23:40 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I get it like 10 times and then Plex is going crazy.

Initially I thought I got rate limited by Amazon, but that probably isn’t it because I am not a heavy user. (I only uploaded 2 8gb movies (encrypted) and I haven’t even watched one)
I already searched GitHub and here but I can’t find any info about others getting rate limited. Because I thought it was a problem from Amazon’s side I already waited 24 hours but it didn’t help.

I also tried lots of mount options from some people on the forums but that doesn’t fix it.

Does someone else have the same problem and how can I fix it?

Thank you!

Can you try with latest beta, ncw just fixed some seek/retry problems with crypt.

@Ajki It was a combination of that and not enough disk space, it’s fixed now. Thank you!