The Get NFT metadata api, sometimes returns an ipfs url. I would expect the api to return a proper ipfs url (ipfs://), but it gives me an http url which seem to be internal to Moralis: https://ipfs.moralis.io:2053/ipfs/.... That url doesn’t work, it gives me a 403. This seem to be a bug, it should give me back the ipfs url, or it should allow me to use the http url it gives me.
Hi @paul-aldora
Sry for the late reply. I can confirm you that the https://ipfs.moralis.io:2053/ipfs/ path still works.
Can you share the ipfs hash which is returning error 403?
@johnversus one example is:
https://ipfs.moralis.io:2053/ipfs/bafybeibqch4za325rjzva4nxtgrjd4k4qdf6dval4jwjxbtpj2dyt6qjhy/15538.json
403: error code 1020
Hi @paul-aldora
We dont support hashes that start with bafy...
In this case you need to fix the URL when you find bafy hash in the URL.
Replacing ipfs.moralis.io:2053 with ipfs.io should fix it.
https://ipfs.io/ipfs/bafybeibqch4za325rjzva4nxtgrjd4k4qdf6dval4jwjxbtpj2dyt6qjhy/15538.json
1 Like
What I don’t understand, is that the api returns the incorrect url. It should just return an url starting with ipfs:// in this case, not a non working https url?
This was a know issue from our end. We will fix it in future versions.
1 Like