Open
Description
Description
Geth has enforced the use of JWT Token authentication in its nodes since The Merge, now that the Beacon Chain must connect to the EL. While trying to connect my Chainlink node to the my Geth node, I get the following error message:
RPCClient returned error (Holesky) logger=EVM.17000.Node.Lifecycle.Unreachable node=(primary)Holesky:ws://geth:8546:http://geth:8551 nodeName=Holesky nodeOrder=100 nodeState=Dialed nodeTier=primary stacktrace=github.com/smartcontractkit/chainlink-framework/multinode.(*node[...]).verifyChainID
Failed to verify chain ID for node [email protected]/node.go:275 chainID=17000 err=RPCClient returned error (Holesky): primary http (http://geth:8551) call failed: 401 Unauthorized: missing token
errVerbose=401 Unauthorized: missing token
Your Environment
Chainlink Node 2.21.0 at commit eaa03c3a8ceb71d3e469b077f60a578af2532fe5
Geth/v1.15.4-stable-8ccca244/linux-amd64/go1.24.0
Steps to Reproduce
- Run geth enabling RPC-API with authentication:
$ geth --http --ws --authrpc.jwtsecret jwtsecret
- Run you Chainlink providing the IP and ports of the EL using
HTTPURL
WSURL
.
Additional Information
Metadata
Metadata
Assignees
Labels
No labels