Hi @kresimir i’ve been getting this error again for two days. Can you help me?
I could also reset your speedy node token if you send me your email and current token in DM
Hello I am also having this problem in production. Please help
you have a new speedy node token now
Thank you @cryptokid but the issue remains. Any idea what else could possibly causing this unahtorized error?
if you are doing getLogs with more than 2k blocks you could also get that error
We don’t but we do use getPastEvents – does that impact it?
maybe it is the same thing as getLogs, what is the interval for block numbers that you use?
10 seconds I believe
Is there anything we can do for now? There’s a lot of events in prod that we’re unable to process because of this
I don’t know what you mean by 10 seconds
do you use a block range when trying to get those events?
We call getPastEvents every 10 seconds from that block number to latest block number
can you check the block interval then, from that block number to latest block number?
It’s not more than 3-10 blocks at a time
But sometimes we do need to do a lot more than that. like 10k-20k blocks from the past. Is there a special node we can use in that case?
if you need to do 10-20k blocks, you should do them with multiple requests and each request with a maximum of 2k block, there was this restriction with maximum 2k nodes added few days ago
Hey @cryptokid this issue is not going away. We went back to using Infura.
Now the error message changed to: Error: Invalid JSON RPC response: “fromBlock must be less than or equal to toBlock”
what where the parameters from when you got that error? it looks like fromBlock was greeter than toBlock from that error message
