# Backup uploads are not protected against 429s

**URL:** https://meta.discourse.org/t/backup-uploads-are-not-protected-against-429s/372139
**Category:** Bug
**Tags:** backups
**Created:** [June 29, 2025, 4:31am UTC](https://meta.discourse.org/t/backup-uploads-are-not-protected-against-429s/372139 "2025-06-29T04:31:20Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [June 29, 2025, 4:31am UTC](https://meta.discourse.org/t/backup-uploads-are-not-protected-against-429s/372139/1 "2025-06-29T04:31:20Z")

</div>

When uploading a backup, I am constantly hitting 429s, which results in the entire upload failing, resulting in me being forced to upload via CLI. This is because the frontend is not properly handling 429 responses. My personal suggestion is to either remove ratelimiting on that endpoint or just have the client properly handle it.

 ![image](https://global.discourse-cdn.com/meta/original/4X/9/4/3/9435e667f407d5e88e0c7c96b949b7e9fc7f4960.png)

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 30, 2025, 4:09am UTC](https://meta.discourse.org/t/backup-uploads-are-not-protected-against-429s/372139/2 "2025-06-30T04:09:53Z")

</div>

oh, those parts look really really small.

Maybe the fix is twofold, relax rate limiting and use larger chunks.

Will alert the team in case they have ideas.

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [June 30, 2025, 9:27pm UTC](https://meta.discourse.org/t/backup-uploads-are-not-protected-against-429s/372139/4 "2025-06-30T21:27:40Z")

</div>

Must be an issue with the Uppy chunk size. It’s strange that nobody else encountered this before. I thought our default chunk size was 5 MB. I’ll investigate. I’m pretty sure our Uppy uploader doesn’t handle 429 codes, but I’ll check if we can relax the rate limit a bit. But I think it’s just the default rate limit kicking in.