StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

haqq: move CometBFT RPC laddr off 8545 to 26657 (EVM json-rpc never bound) #71

Merged
claude merged 1 commits from haqq-init-cometbft-rpc-port into main 2026-09-05 08:41:50 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
claude commented 2026-09-05 08:34:18 +00:00
Collaborator
Copy Link

haqq/scripts/init.sh line 44 wrote [rpc] laddr = tcp://0.0.0.0:8545 into config.toml, the same port app.toml [json-rpc] uses (address 0.0.0.0:8545, ws 0.0.0.0:8546). CometBFT binds 8545 first, so the EVM json-rpc/ws servers never start: inside rpc-haqq-mainnet-1 on rpc-de-31 the only listeners are :8545 (CometBFT, eth_blockNumber -> -32601 Method not found) and p2p :10465; no 8546, no 26657. Traefik, dshackle and sync-status.sh all expect eth on 8545/8546, so haqq has served no EVM traffic since the 2026-09-02 image rebuild (referee: haqq@EU-West unavailable 72h; UNSERVED-NODE tripwire 0 ok upstreams on rpc-de-14). Introduced by 223c6940 (2026-08-04). Fix: laddr -> tcp://0.0.0.0:26657; json-rpc lines untouched; 26657 not exposed in compose. Asset-only, no regeneration. Class B: hand-maintained rpc file, single scope. Diag job f1fdf5cd, change job 450a23db. Deploy: rebuild image + recreate haqq-mainnet only on rpc-de-31 (keep /root/onsite-overrides/haqq-mainnet-skip-addrbook-as-seeds.yml on the compose -f list).

haqq/scripts/init.sh line 44 wrote [rpc] laddr = tcp://0.0.0.0:8545 into config.toml, the same port app.toml [json-rpc] uses (address 0.0.0.0:8545, ws 0.0.0.0:8546). CometBFT binds 8545 first, so the EVM json-rpc/ws servers never start: inside rpc-haqq-mainnet-1 on rpc-de-31 the only listeners are :8545 (CometBFT, eth_blockNumber -> -32601 Method not found) and p2p :10465; no 8546, no 26657. Traefik, dshackle and sync-status.sh all expect eth on 8545/8546, so haqq has served no EVM traffic since the 2026-09-02 image rebuild (referee: haqq@EU-West unavailable 72h; UNSERVED-NODE tripwire 0 ok upstreams on rpc-de-14). Introduced by 223c6940 (2026-08-04). Fix: laddr -> tcp://0.0.0.0:26657; json-rpc lines untouched; 26657 not exposed in compose. Asset-only, no regeneration. Class B: hand-maintained rpc file, single scope. Diag job f1fdf5cd, change job 450a23db. Deploy: rebuild image + recreate haqq-mainnet only on rpc-de-31 (keep /root/onsite-overrides/haqq-mainnet-skip-addrbook-as-seeds.yml on the compose -f list).
claude added 1 commit 2026-09-05 08:34:19 +00:00
haqq: fix CometBFT RPC port conflict - move [rpc] laddr from 8545 to 26657 db7ef4c8cd
claude merged commit 4c86367c5f into main 2026-09-05 08:41:50 +00:00
claude deleted branch haqq-init-cometbft-rpc-port 2026-09-05 08:41:50 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#71
Delete Branch "haqq-init-cometbft-rpc-port"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?