Skip to content

Commit

Permalink
fix(docs-site): omitted L1 HTTP endpoint from taiko client flags (#18798
Browse files Browse the repository at this point in the history
)
  • Loading branch information
brachsterX authored Jan 21, 2025
1 parent 076f5f0 commit a3e08ff
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ This error can occur if there are issues with your L1 node, such as it being out

### Block batch iterator callback error error="failed to decode tx list: beacon client not found"

Potential Solution #1: Set L1_BEACON_HTPP in .env file and restart your node.
Potential Solution #1: Set L1_BEACON_HTTP in .env file and restart your node.

Potential Solution #2: It's possible that the endpoint either lacks WebSocket (ws) support or is malformed. To address this error, ensure the following:
- Your L1 node is operating correctly.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -75,14 +75,13 @@ This guide will help you start up a Taiko RPC node using [simple-taiko-node](htt
For Mainnet, the L1 Node will need to be an Ethereum node; for Testnet, the L1 Node will need to be an Etherem testnet (Holesky) node.
</Aside>

Next, you will set the L1 node endpoints. If you are running a local L1 node, you cannot reference the L1 endpoints as `http://127.0.0.1:8545`, `ws://127.0.0.1:8546` and `http://127.0.0.1:5052` because that is local to inside the simple-taiko-node Docker networking. Instead you can try:
Next, you will set the L1 node endpoints. If you are running a local L1 node, you cannot reference the L1 endpoints as `ws://127.0.0.1:8546` and `http://127.0.0.1:5052` because that is local to inside the simple-taiko-node Docker networking. Instead you can try:

- Using `host.docker.internal` (see: [stack overflow](https://stackoverflow.com/questions/24319662)).
- Using the private ip address of your machine (use something like `ip addr show` to get this ip address).

After getting the address of the L1 node, set the following L1 node endpoints in your `.env` file. Here is an example:

- `L1_ENDPOINT_HTTP=http://192.168.1.15:8545`
- `L1_ENDPOINT_WS=ws://192.168.1.15:8546`
- `L1_BEACON_HTTP=http://192.168.1.15:5052`

Expand Down

0 comments on commit a3e08ff

Please sign in to comment.