berachain-mainnet-reth: fix Traefik ipallowlist on empty WHITELIST #65

Closed
claude wants to merge 1 commits from issue-3492 into main
Collaborator

Summary

berachain-mainnet-reth-archive-trace: Traefik ipallowlist middleware was disabling the entire router when WHITELIST env was empty, causing 404s and marking the node "error" in DRPC despite the node being healthy and syncing.

Fix

Traefik middleware now provides default 0.0.0.0/0 (permissive) when WHITELIST is empty or unset, keeping the router active.

Verification

  • Node containers restart with Traefik router enabled
  • Node continues syncing normally (health state recovers)
  • rpc commit: 8aee5fbccd

(vibe-node issue #3492)

## Summary berachain-mainnet-reth-archive-trace: Traefik ipallowlist middleware was disabling the entire router when WHITELIST env was empty, causing 404s and marking the node "error" in DRPC despite the node being healthy and syncing. ## Fix Traefik middleware now provides default 0.0.0.0/0 (permissive) when WHITELIST is empty or unset, keeping the router active. ## Verification - Node containers restart with Traefik router enabled - Node continues syncing normally (health state recovers) - rpc commit: 8aee5fbccd7f (vibe-node issue #3492)
claude added 1 commit 2026-08-13 02:10:34 +00:00
Author
Collaborator

merge-bot (del-018): classified B (hand-maintained rpc file(s), single scope). Auto-merge after a 72h objection window - comment 'hold' to block.

merge-bot (del-018): classified B (hand-maintained rpc file(s), single scope). Auto-merge after a 72h objection window - comment 'hold' to block.
Author
Collaborator

Closing as a SECURITY regression, not merging: ${WHITELIST:-0.0.0.0/0} fails OPEN - an empty whitelist would expose every node RPC route to the entire internet. The empty-WHITELIST 404 this fixes is the fail-CLOSED half of that trade; the root cause was hosts never getting their whitelist seeded, fixed 2026-08-22..24 (first-boot seeding step + hourly unserved-node tripwire detection B). If berachain needs a specific allowance it should be an explicit entry, never a default-open.

Closing as a SECURITY regression, not merging: ${WHITELIST:-0.0.0.0/0} fails OPEN - an empty whitelist would expose every node RPC route to the entire internet. The empty-WHITELIST 404 this fixes is the fail-CLOSED half of that trade; the root cause was hosts never getting their whitelist seeded, fixed 2026-08-22..24 (first-boot seeding step + hourly unserved-node tripwire detection B). If berachain needs a specific allowance it should be an explicit entry, never a default-open.
claude closed this pull request 2026-08-26 02:42:28 +00:00

Pull request closed

Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#65