# Upload reach api rate limit

**URL:** https://discourse.nixos.org/t/upload-reach-api-rate-limit/64468
**Category:** Help
**Created:** [May 19, 2025, 10:39pm UTC](https://discourse.nixos.org/t/upload-reach-api-rate-limit/64468 "2025-05-19T22:39:32Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Felipe-9](https://discourse.nixos.org/user_avatar/discourse.nixos.org/felipe-9/32/29744_2.png) [@Felipe-9](https://discourse.nixos.org/u/Felipe-9)
#### Post date: [May 19, 2025, 10:39pm UTC](https://discourse.nixos.org/t/upload-reach-api-rate-limit/64468/1 "2025-05-19T22:39:32Z")

</div>

Whenever im trying to update the system `nix flake update` i frequently get the api limit reached error.

anyone else having this problem?

---

<div class="post-metadata">

### Author: ![smkuehnhold](https://discourse.nixos.org/user_avatar/discourse.nixos.org/smkuehnhold/32/4326_2.png) [@smkuehnhold](https://discourse.nixos.org/u/smkuehnhold)
#### Post date: [May 19, 2025, 11:14pm UTC](https://discourse.nixos.org/t/upload-reach-api-rate-limit/64468/2 "2025-05-19T23:14:11Z")

</div>

I had this happen to me in the past with an app that had a self-updater script combined with a service that was poorly written (by me). I believe it was noisetorch.

At startup, it would try to update itself in a way that nix doesn’t like and fail. Presumably by fetching a tarball from GH. And because the service was written to repeat on failure without a limit, this would repeat ad nauseam.

The problem also didn’t bubble up immediately because I started on a relatively new version. It took some time for the version I had installed to drift away from the latest and then this setup blew up on me.

---

<div class="post-metadata">

### Author: ![NobbZ](https://discourse.nixos.org/user_avatar/discourse.nixos.org/nobbz/32/7022_2.png) [@NobbZ](https://discourse.nixos.org/u/NobbZ)
#### Post date: [May 20, 2025, 5:53am UTC](https://discourse.nixos.org/t/upload-reach-api-rate-limit/64468/3 "2025-05-20T05:53:26Z")

</div>

This is a common problem, and is probably even more common after GH reduced the limit even further recently.

Your best option is to set an `access-tokens` for GH in your nix configuration.

---

<div class="post-metadata">

### Author: ![sokai](https://discourse.nixos.org/user_avatar/discourse.nixos.org/sokai/32/34234_2.png) [@sokai](https://discourse.nixos.org/u/sokai)
#### Post date: [May 20, 2025, 1:56pm UTC](https://discourse.nixos.org/t/upload-reach-api-rate-limit/64468/4 "2025-05-20T13:56:45Z")

</div>

@Felipe-9 Maybe this thread can help u out: [Flakes: Provide GitHub API Token for rate limiting?](https://discourse.nixos.org/t/flakes-provide-github-api-token-for-rate-limiting/18609)

---

<div class="post-metadata">

### Author: ![Felipe-9](https://discourse.nixos.org/user_avatar/discourse.nixos.org/felipe-9/32/29744_2.png) [@Felipe-9](https://discourse.nixos.org/u/Felipe-9)
#### Post date: [May 21, 2025, 12:47pm UTC](https://discourse.nixos.org/t/upload-reach-api-rate-limit/64468/5 "2025-05-21T12:47:07Z")

</div>

i guess having greater rate limit would indeed help, that is until they lower further. i when i have time i will give it a try, will be using sops tho.
