From my research on this forum, I can see quite a lot of people facing HTTP timeouts when trying to access their newly uploaded content through the public gateway.
This comment here suggests that the timeouts are expected when the data isn’t mirrored (solely owned by the uploader):
First question: is this confirmed? Is this documented?
I think most first time IPFS users all start their journey by
ipfs add [FILE] and straightaway expect this file to be served through the public gateway, which won’t be the case (in an expected way?).
Running two nodes locally, I can start confirming the above by trying to access through the gateway data newly added by NodeA, facing an in progress HTTP request, running an
ipfs get [HASH] on NodeB, and then seeing the HTTP request resolved instantly. Even an HTTP request on my phone on a different network is resolved instantly once a node (different from the uploader node) fetches the data (through the CLI, IPFS desktop or even the node’s local gateway).
Inspecting the DHT shows that the provider entry linking the uploader node to the hash of the uploaded data is successfully created.
ipfs dht findprovs [FILE_HASH] on any node retrieves the entry as soon as the data is uploaded, while the public gateway is still unable to serve the data.
If the DHT is fine, what is causing the gateway to hang?