Missing IPFS hash?

We have a pinned IPFS has which we uploaded 2 days but nothing shows when i query for it?

Any ideas?




Hey James, can you share the code/request you’re using to try and access this and the response you’re receiving?

using https in chrome like this - http://ipfs.infura.io/ipfs/QmVUGEBsCH416TMKSeobzYwhPqjyfAEZELFZjdznxsbBSV

Any ideas on this one @mike ?

Were you able to retrieve the pin the day you pinned it? Or has it always been unretrievable?

I believe so, it was generated by a user of one of our dApps which has been working fine for a while now and the code hasn’t change for a bit either. The IPFS hash is then seeded in the contract on mainnet, this time though nothing shows when we query for it.

I can tell them to regenerate it today but wanted to know what happened to it ideally.



Unfortunately the best path is to re-pin it and confirm everything is working. We are building out systems that will better allow visibility to the API key owner into what has been pinned/retrieved/etc.

Thanks, I will remove the record and ask the user to re-upload.

Should we be using an API key on IPFS - we do for our ETH node access to have not seen and docs or info on IPFS access keys?


The IPFS endpoint does now support using dashboard generated Project IDs and Secrets, it’s not enforced yet and we will be updating our docs very soon to show exactly how to use them with requests.

We have another incident last night of a pinned image which is now giving us a Gateway Timeout? Any ideas @mike https://ipfs.infura.io/ipfs/QmcfGZ7ot8UqBPhgu9ShTNxt8bhsyFWw99ZMBdfUeXoy4k

Is there a way to prevent this and is this a known issue? Unfortunately these images are used to construct ERC721 tokens which are then out of our control so the user experience from a dapp perspective is very bad when the user not long sees the image.

Any suggestions would help greatly.

I have also upload the image again to test the suggested fix, it generates the same hash a expected but I still then get a 504 timeout when looking it up.



Hi James, we pushed a fix that should resolve the 504 errors you’re seeing, can you test it now?

Unfortunately not @mike I am still seeing strange behaviour such as hashes timing out and hashes which never resolve and just seem to hang. These are all new uploads if this helps, existing IPFS hashes seem to resolve fine.

This is an example of an image uploaded which now appears to now resolve, I get a 502 instead? - https://ipfs.infura.io/ipfs/QmYJVCx6qE9neiqMpaSdWWN5reoXFaf7NhTEP7AfKoyAG6 - it was created at approx May-27-2019 02:25am UTC - I manaully fixed this by getting the original image and pushing it again

I also saw this in our logs on friday night, it was preventing new files being upload at all - I haven’t seen it before and haven’t seen it since but it may help:

Error: open /data/ipfs/blocks/V4/put-198839627: too many open files



Heres another one - https://ipfs.infura.io/ipfs/QmefQ84mE6nXSmcswuinACZwoHeuzuzaPhS99qJt3F6qmn - it feel like this is happening nearly every time something is pinner - is there any ideas on a solution or work around to thi? Cheers in advance

Thanks James, we are looking into it, will get back to you asap.

Also happening to me, they sometimes just hang and when they finally come back like 6~10 mins later they come back with a 502 bad gateway:

cURL request: curl -H ‘Host: ipfs.infura.io:5001’ -H ‘user-agent: my-proj/21 CFNetwork/897.15 Darwin/17.5.0’ -H ‘accept: /’ -H ‘accept-language: en-us’ --compressed ‘https://ipfs.infura.io:5001/api/v0/cat/QmNigoPbtAvkvVLX2a5zwXNrB5kHNqScUi8XzaC1xGEmdq

response after 10 mins when it hangs:


<head><title>502 Bad Gateway</title></head>

<body bgcolor=“white”>

<center><h1>502 Bad Gateway</h1></center>



Thanks @mike - I see you guys are putting out a fix for some of the bits mentioned on this thread - https://status.infura.io/incidents/5skqqhvsy74d -

thanks again

We will keep an eye on the service and let you know if problems appear.



@mike @jamesmorgan Any updates on this issue? I am also developing a dapp and my ipfs hashes resolve seemingly randomly. Nothing changed in my code but this issue started a couple weeks ago. IPFS requests through infura gateway sometimes hang but on page refresh they resolve, or sometimes they don’t and timeout after several minutes. Files will be perfectly fine and loading but upon retrying several will hang, or not, as I said seemingly random.

const ipfsClient = require('ipfs-http-client');
const ipfs = new ipfsClient({
  host: 'ipfs.infura.io',
  port: 5001,
  protocol: 'https'

const getJson = async ipfsHash => {
  let res = await ipfs.get(ipfsHash);

  const buffer = res[0].content;

  const utf8Decode = new window.TextDecoder('utf-8');
  const string = utf8Decode.decode(buffer);

  const object = JSON.parse(string);

  return object;

Was working fine for several months, now getting random hangs when loading data.

What response are you receiving when the request fails? When this happens are you trying to access files that you did not originally pin using our API?

No response, request just hangs indefinitely. I am adding the files through infura api. Upon adding ipfs hash will resolve, data can be accessed intermittently.

Once the hash is accessible, does it ever become inaccessible?