raiden
raiden copied to clipboard
HTTPError 403 when using infura
Description
One of the devs of stakenet is stuck on an unsettled channel while using infura. Upon start the Raiden node tries to settle two channels because SettleTimeout
is reached and an ETH-RPC call is triggered by ContractSendChannelSettle
.
Infura answers with
this = <RaidenService node:0x4E1aB8B6dc9F30E8e25Eb3fa15b59fF7F26c53f3>
running = 0
subtask = <Greenlet "rs-handle_blocking_events" at 0x7fd19b6c7710: <bound method RaidenService._handle_events of <RaidenService node:0x4E1aB8B6dc9F30E8e25Eb3fa15b59fF7F26c53f3>>(ChainState(block_number=10937333 block_hash=0x1629, [ContractSendChannelSettle(triggered_by_block_hash)>
exc = HTTPError('403 Client Error: Forbidden for url: https://mainnet.infura.io/v3/90f9884699a4438d8bcccd8da8a6ce12')
which leads to the crash of the corresponding greenlet.
Infura's 403
The above error of infura comes AFAIK from two possible reasons
- required secret is set
- Allowlist is activated
Both of the cases is not true for the used infura ID.
Proposal
I'm in collaboration with one of the stakenet devs to see if an ETH client (without using infura) lets the channel settle. If so we can be sure that this is an infura related issue. We should further investigate why infura is dropping the RPC call.
Maybe this can be a hint