You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to avoid having to specify ' --http.corsdomain "*" ' in the l2_execution_engine (geth fork) docker compose and not having to rely on a browser extension to fix the cors.
Fixed with this commit where we change the node address to that of the websocket address, because the websockets cors is already set to public out of the box
Trying to avoid having to specify ' --http.corsdomain "*" ' in the l2_execution_engine (geth fork) docker compose and not having to rely on a browser extension to fix the cors.
I already tried web3/web3.js#2559 (comment) but it's outdated and not working anymore.
The plan is running both the node and dashboard on localhost so they should be able to communicate without problems from what I'm reading.
https://geth.ethereum.org/docs/interacting-with-geth/rpc gives a little more info
The text was updated successfully, but these errors were encountered: