The bonder sync is producing numerous, non-blocking errors with a "403 Forbidden"
See original GitHub issueAll instances of the bonder (live and local) are producing unexpected errors. This does not appear to be negatively affecting anything and it appears to not block anything, however, this should be well understood and fixed.
To reproduce, run the bonder locally and observe errors. Alternatively, look at existing, recent bonder logs.
Some data points:
- They all appear to give the same error:
403 Forbidden
- They all appear on the Hop mainnet RPC endpoint
Some examples of errors from running locally:
2021-12-17T14:41:43.595-08:00 WARN <id: 244536375> retry attempt #1 failed with error "missing revert data in call exception (error={"reason":"bad response","code":"SERVER_ERROR","status":403,"headers":{"date":"Fri, 17 Dec 2021 22:41:43 GMT","content-type":"text/html","content-length":"118","connection":"close","server":"nginx/1.21.4"},"body":"<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n</body>\r\n</html>\r\n","requestBody":"{\"method\":\"eth_call\",\"params\":[{\"from\":\"0x2a6303e6b99d451df3566068ebb110708335658f\",\"to\":\"0x22b1cbb8d98a01a3b71d034bb899775a76eb1cc2\",\"data\":\"0x57344e6f000000000000000000000000d8781ca9163e9f132a4d8392332e64115688013a\"},\"latest\"],\"id\":137,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","url":"<HOP_MAINNET_ENDPOINT>"}, data="0x", code=CALL_EXCEPTION, version=providers/5.5.0)". retrying again in 2 seconds.
[AsyncFunction (anonymous)] 244536375 {
data: '0x57344e6f000000000000000000000000d8781ca9163e9f132a4d8392332e64115688013a',
to: '0x22B1Cbb8D98a01a3B71D034BB899775A76Eb1cc2',
from: '0x2A6303e6b99d451Df3566068EBb110708335658f'
} undefined
2021-12-17T14:41:35.688-08:00 WARN <id: 244558208> retry attempt #1 failed with error "bad response (status=403, headers={"date":"Fri, 17 Dec 2021 22:41:35 GMT","content-type":"text/html","content-length":"118","connection":"close","server":"nginx/1.21.4"}, body="<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n</body>\r\n</html>\r\n", requestBody="{\"method\":\"eth_getLogs\",\"params\":[{\"fromBlock\":\"0xd2f53b\",\"toBlock\":\"0xd2f541\",\"address\":\"0xb8901acb165ed027e32754e0ffe830802919727f\",\"topics\":[\"0x78e830d08be9d5f957414c84d685c061ecbd8467be98b42ebb64f0118b57d2ff\"]}],\"id\":108,\"jsonrpc\":\"2.0\"}", requestMethod="POST", url="<HOP_MAINNET_ENDPOINT>", code=SERVER_ERROR, version=web/5.5.1)". retrying again in 2 seconds.
[AsyncFunction (anonymous)] 244558208 {
address: '0xb8901acB165ed027E32754E0FFe830802919727f',
topics: [
'0x78e830d08be9d5f957414c84d685c061ecbd8467be98b42ebb64f0118b57d2ff'
],
fromBlock: 13825339,
toBlock: 13825345
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
What Is the 403 Forbidden Error and How to Fix It (8 Methods ...
403 forbidden errors can cause a great deal of frustration as they will prohibit you from accessing a resource. They mainly occur due...
Read more >Red Hat Satellite 6 fails to sync repositories with 403 ...
Issue. Red Hat Satellite 6 throwing 403 forbidden errors while syncing repositories from customer portal. Repository sync fails with following ...
Read more >403 Forbidden error: What it is and how to fix it - Allconnect.com
A 403 error is an HTTP status code that means “access denied.” If you ever had a treehouse as a kid, you may...
Read more >The requested URL returned error: 403 Forbidden #39 - GitHub
That error means you are using wrong credential or wrong repo: Username needs to be the user, not the email; Ensure you provide...
Read more >Troubleshoot Azure Digital Twins: Error 403 (Forbidden)
Learn how to diagnose and resolve error 403 (Forbidden) failed service requests from Azure Digital Twins.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For debugging purposes, I created a new ELB and tested using Infura, Alchemy, and Quicknode RPC urls.
I can confirm that the
403
error only occurs when using Infura as the RPC url, which happens to occur randomly but frequently.Random
403
errors with InfuraNo random
403
error with AlchemyNo random
403
error with QuicknodeEndpoints have been updated: