Removal of IPFS un-authenticated API and non-authenticated Public IPFS gateway

Announcements
1

Hey everyone,

We’re removing today the support for non-authenticated IPFS API requests and public non-authenticated IPFS gateway, please subscribe for updates here: Infura Status - Removal of IPFS un-authenticated API and non-authenticated Public IPFS gateway

Thanks,
Traian

1 Like
2

A couple of points to emphasise:

  • your data previously uploaded to IPFS is still there, nothing is lost, it just has to be accessed with a different gateway URL:
if you’ve previously been accessing a CID with this URL:

https://ipfs.infura.io/ipfs/CID

now you’ll need to create a dedicated gateway and access it via:

https://<your_gw_name>.infura-ipfs.io/ipfs/CID
3

Hi @traian.vila im in a bit of a pickle i have an application in JAVA that was built around the Infura public gateway, im now unable to instantiate my ipfsClient
IPFS ipfs = new IPFS("/dnsaddr/ipfs.infura.io/tcp/5001/https");
I keep getting project id required i tried using my dedicated gateway but that didn’t help either how do i work around this problem?

4

Hey, for the gateway, you just need to change the public gw into your dedicated gw url.
Your ipfsClient needs to pass authentication now, that endpoint /dnsaddr/ipfs.infura.io/tcp/5001/https doesn’t change.

Is this the lib you’re using ? https://github.com/ipfs-shipyard/java-ipfs-http-client

5

yes it is im not sure how to pass the authentication with it?

6

yeah, I don’t think that this client actually supports auth, I’ve scanned the source code a bit but haven’t found anything. You could simply not use this lib and rely on the java httpclient, see an example here Http Basic Authentication in Java using HttpClient? - Stack Overflow