Hello @rsjethani , the solution is to set up go-ethereum to use your API key, which has to be v3 . You can follow the Getting Started guide here to create your v3 API key.
Hi I have the same problem. Yesterday (10 feb 2020) I started to get error 403 when getting new blocks and transactions. I had no problem before. I use v3. My access token is 11 month old.
I still continue to receive block headers but suddenly getting error 403 for any request (block or transactions).
I tried to create a new access_token without a difference.
Any idea ?
Thanks
Hi @Sean_Infura, we are also getting the same issue (getting 403 on the “https://rinkeby.infura.io/v3/<INFURA_KEY>”. It started some days ago as well. Should we generate new API keys?
Hi @tarrenceva . I’m not able to reproduce this without knowing more about how you are configuring and running your graph-node perhaps the Graph Protocol team can provide more insights into what their node is doing. My initial thought is that the graph node is attempting to access archival state data (blocks older than 128 from the head of the chain). Because of the significant resources archival nodes require, access to archival state on Infura requires our archival data subscription add-on explained here: https://infura.io/docs/ethereum/add-ons/archiveData. If you think that the graph node does not need archival data please provide more logging or error messages and I’d be happy to look into this more with you.