Unauthorized error on speedy nodes

Technical Issue Reporting
#3

Thank you!

I’ve now given you a fresh API key and speedy node token, please try and let me know in return if it solved the issue.

#4

Thanks for your help @kresimir. All requests are working now. :+1:

1 Like
#5

Hi @kresimir i’ve been getting this error again for two days. Can you help me?

#6

I could also reset your speedy node token if you send me your email and current token in DM

#7

Hello I am also having this problem in production. Please help

#8

you have a new speedy node token now

#9

Thank you @cryptokid but the issue remains. Any idea what else could possibly causing this unahtorized error?

#10

if you are doing getLogs with more than 2k blocks you could also get that error

#11

We don’t but we do use getPastEvents – does that impact it?

#12

maybe it is the same thing as getLogs, what is the interval for block numbers that you use?

#13

10 seconds I believe

#14

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

#15

I don’t know what you mean by 10 seconds

#16

do you use a block range when trying to get those events?

#17

We call getPastEvents every 10 seconds from that block number to latest block number

#18

can you check the block interval then, from that block number to latest block number?

#19

It’s not more than 3-10 blocks at a time

#20

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?

#21

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

#22

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”