Skip to content

[DEVEL] Accept JWT Token to connect with Geth node #16762

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
willianpaixao opened this issue Mar 13, 2025 · 0 comments
Open

[DEVEL] Accept JWT Token to connect with Geth node #16762

willianpaixao opened this issue Mar 13, 2025 · 0 comments

Comments

@willianpaixao
Copy link
Contributor

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

  1. Run geth enabling RPC-API with authentication:
$ geth --http --ws --authrpc.jwtsecret jwtsecret
  1. Run you Chainlink providing the IP and ports of the EL using HTTPURL WSURL.

Additional Information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant