Hi Geolffrey,
we has a temporary issue. Create a new project and try again. Let us know how you go.
Warm regards,
Chris | Infura | ConsenSys
Hi @chris.paterson, thank you for answering so quickly.
Issue persisting with a new project:
https://mainnet.infura.io/v3/2c9aded0297647a3b0d408e0f4749aaf
Regards and thank you
Hi Geolffrey,
our apologies, this was supposed to have been fixed 15 hours ago. I have reported your experience back to the team. In the mean time I suggest you create yet another project and try again.
Warm regards,
Chris | Infura | ConsenSys
1 Like
Hi there,
Same problem here. It was working yesterday with a new project ID, today I just added some more methods in the allowed whitelist, but changes where kind of ignored…
I have just created a brand new project, and the curl from the getting started section is not working (neither the connection from my web3.js project):
✘ isma@laptop ~ curl https://mainnet.infura.io/v3/e9e66c4812d84ec4b56eba2bcd1cbbdd
-X POST
-H “Content-Type: application/json”
-d ‘{“jsonrpc”:“2.0”,“method”:“eth_blockNumber”,“params”:[],“id”:1}’
invalid project id
Hi there,
There is a delay within our database at the moment, causing newly created projects to take some time before being usable. I suggest trying to use an older project if you have one available.
Our team has been working intensely on this and have implemented a fix, but it might take a while until the data catches up.
1 Like
I create a new project and it works, Thank you!
Hi everyone!
The issue with invalid project id has been resolved. The processor is currently catching up with lag still, but it seems it’s going well.
Please let us know if you are still facing any issues with it.
1 Like
Hi @lovekosmas the problem still persists. I am still experiencing the problem. I am worried can we use Infura for production apps at the moment? Thanks
@dev79, could you open a support ticket? https://infura.io/contact
I would need more info from you, such as the email associated with the account as we’ll as project id you are using.
I will NOT ask to share it here.
Hi @lovekosmas thanks. I’ve just opened the ticket via the contact page as you requested, looking forward to your feed back.
1 Like
Hi @lovekosmas, I opened a ticket and got the same old advice, to delete the project and create another one. I’ve done this at least 3 times and it’s not working. I am trying out Infura’s IPFS service with the plan to use it for production. Can you at least level with me is Infura production ready at this point in time? I can’t have users on a trial and error basis when they are using the app. Thanks in advance
what to do if you have already reached the limit of 3 project IDs?
@dev79 We weren’t able to locate the project id you have provided.
If the deletion of the project and creating a new one doesn’t work, and you are getting the same error, this must be something out of the ordinary since the issue was fixed a while ago.
I would ask you to reply to the email providing those project ids for us to look at - please note the project should be active.
@Abhinav_Agarwal, you can reach out to the Infura team https://infura.io/contact requesting the number of projects you would like your account be increased to.
Hi @lovekosmas,
I followed the advice from Natalia, to delete and try a different project, still no joy. I have also replied your email.
The problem is solved!!!
here it is:
In the infura site:
Step 1. Create IPFS project with card info
Step 2. replace the following code with your old code
const projectId = ‘2E8Kps3Xij…’; //(Step 3. Place the project id from your infura project)
const projectSecret = ‘b222afc94…’; //(Step 4. Place the project_secrect from your infura project)
const auth = 'Basic ’ + Buffer.from(projectId + ‘:’ + projectSecret).toString(‘base64’);
const ipfsClient = require(‘ipfs-http-client’)
const ipfs = ipfsClient.create({
host: “ipfs.infura.io”,
port: 5001,
protocol: “https”,
apiPath: “/api/v0”,
headers: {
authorization: auth,
},
});
Step 5. Save and npm start
1 Like
I read through all the replies, double, triple checked my ID, went back and created new keys. Nothing has helped. How is it acceptable to have the debugging solution to keep trying until something works? This is obviously something that many people are running into and somehow remaking keys is fixing it?!
Is there an approximate amount of IDs I need to create before one will work?
Hi @Sam_Slivinski,
there was a DB sync issue some time ago where recreating the key solved the issue, this solution is no longer relevant (you can see many ppl doing it without success). The problem must be elsewhere. Post your code and we can check it out for you.
It’s usually here:
const auth = 'Basic ’ + Buffer.from(projectId + ‘:’ + projectSecret).toString(‘base64’);
printing out the value of auth and carefully checking it against the documented requirement or examples you can find also in the docs often helps.
Warm regards,
Chris