# Files are rarely available through public gateways

**URL:** <https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144>\
**Category:** Help\
**Tags:** go-ipfs\
**Created:** [October 31, 2023, 7:19am UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144 "2023-10-31T07:19:49Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\
**Post date:** [November 28, 2023, 5:24pm UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144/21 "2023-11-28T17:24:15Z")

</div>

Btw, if you notice that the accelerated DHT client consumes too much resources, consider trying out [Optimistic Provide](https://github.com/ipfs/kubo/blob/master/docs/experimental-features.md#optimistic-provide). You can read more in the config docs.

---

<div class="post-metadata">

**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\
**Post date:** [November 28, 2023, 7:16pm UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144/22 "2023-11-28T19:16:42Z")

</div>

What happened to `ReprovideSweep`? I thought that was the best possible solution to the problem. Is that still being worked on?

---

<div class="post-metadata">

**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\
**Post date:** [November 28, 2023, 8:36pm UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144/23 "2023-11-28T20:36:11Z")

</div>

I believe it’s actively being worked on, but not yet available: [Amino (the Public IPFS DHT) is getting a facelift | IPFS Blog & News](https://blog.ipfs.tech/2023-09-amino-refactoring/#reprovidesweep-performance)

---

<div class="post-metadata">

**Author:** ![michalgrzegorczyk](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/michalgrzegorczyk/32/8080_2.png) [@michalgrzegorczyk](https://discuss.ipfs.tech/u/michalgrzegorczyk)\
**Post date:** [November 29, 2023, 8:28am UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144/24 "2023-11-29T08:28:56Z")

</div>

The first test with AccelerateD was not successful. The machine restarts every few hours at night. Now I have scaled it to 4 cpu.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/ipfs1/original/2X/1/1fe53c6ab943da623aa290baf7fc3d0d4b5a988a.png)

While looking through the logs, I found this:

```auto
ERROR fullrtdht fullrt/dht.go:450 key not found in map

```

Unfortunately, I cannot reproduce this error. It showed up two days ago.

stats provide output:

```auto
{
  TotalProvides: 4,
  LastReprovideBatchSize: 0,
  AvgProvideDuration: 1137900918,
  LastReprovideDuration: 0,
}

```

`/api/v0/bitswap/reprovide` - returns timeout. I guess this is not a valid response.

---

<div class="post-metadata">

**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\
**Post date:** [November 29, 2023, 11:19am UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144/25 "2023-11-29T11:19:36Z")

</div>

Strange. I’m not sure why this is happening.

Can you try to run the following commands and share the output:

Get a count of blocks in your repo

```auto
$ ipfs repo ls | wc -l 

```

Verify all blocks in your repo (to make sure their not corrupt)

```auto
$ ipfs repo verify

```

---

<div class="post-metadata">

**Author:** ![michalgrzegorczyk](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/michalgrzegorczyk/32/8080_2.png) [@michalgrzegorczyk](https://discuss.ipfs.tech/u/michalgrzegorczyk)\
**Post date:** [November 30, 2023, 5:55am UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144/26 "2023-11-30T05:55:53Z")

</div>

```auto
...api/v0/repo/ls" | wc -l :
282672

.../api/v0/repo/verify" | grep -v '"Msg":""' :
{"Msg":"verify complete, all blocks validated.","Progress":0}

```

I’ll try “optimistic provide” today. Unfortunately, aceleratedht and 4 cpu the problem persists. Node restarted after a much longer time.

---

<div class="post-metadata">

**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\
**Post date:** [December 6, 2023, 10:15am UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144/27 "2023-12-06T10:15:40Z")

</div>

@michalgrzegorczyk Any update on how it went with optimistic provide?

---

<div class="post-metadata">

**Author:** ![michalgrzegorczyk](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/michalgrzegorczyk/32/8080_2.png) [@michalgrzegorczyk](https://discuss.ipfs.tech/u/michalgrzegorczyk)\
**Post date:** [December 8, 2023, 12:47pm UTC](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144/28 "2023-12-08T12:47:03Z")

</div>

In terms of resource consumption, it has improved significantly. The service does not restart and has constant RAM/CPU usage

Unfortunately, the files are still inaccessible through public gateways.

`stats/provide` output:

```auto
{
  TotalProvides: 605377,
  LastReprovideBatchSize: 305774,
  AvgProvideDuration: 599048403,
  LastReprovideDuration: 216694024809842,
}

```

[Previous page](https://discuss.ipfs.tech/t/files-are-rarely-available-through-public-gateways/17144.md?page=1)