ISSUES WITH CREATING ETH KEY PLEASE HELP #18701
Description
[I have my UI up and a running but can seem to create or register ETH keys]
[I managed to make a working config and I'm using endpoints from Infura, i made sure I'm on the main-net so i can make my node a working one. I have good OCR, OCR2, and P2P keys but can't register my evm chains key. Here is a copy of my commands and their results. as well as how my config is set up. Anytime i try to create a key it says no chain ID but i already tested my infura endpoints and it does read and communicate fine.]
root@Node:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
87092fd71d33 smartcontract/chainlink:2.24.0 "chainlink node star…" 47 minutes ago Up 28 minutes (healthy) 0.0.0.0:6688-6689->6688-6689/tcp, [::]:6688-6689->6688-6689/tcp chainlink-node
root@Node:~# cat /root/cl/config.toml
[WebServer]
AllowOrigins = "*"
SecureCookies = false
HTTPPort = 6688
HTTPSPort = 0
AuthenticationMethod = "local"
[WebServer.Sessions]
Secure = false
SessionTimeout = "48h"
SameSite = "None"
[Log]
Level = "debug"
[P2P]
Enabled = false
[EVM]
Enabled = true
[[EVM.Chains]]
ChainID = 1
Enabled = true
ChainType = "ethereum"
FinalityDepth = 1
MinIncomingConfirmations = 1
[[EVM.Chains.Nodes]]
Name = "mainnet-infura"
WSURL = "DELETED FOR SECURITY"
HTTPURL = "DELETED FOR SECURITY"
[GasEstimator]
Mode = "BlockHistory"
BlockHistorySize = 25
BlockHistoryDelay = 1
[Database]
URL = "postgresql://doadmin:REST OF LINK HERE, DELETED FOR SECURITY"
root@Node:~# docker run --rm -it --entrypoint sh smartcontract/chainlink:2.24.0
$ which chainlink
/usr/local/bin/chainlink
$ chainlink chains evm list
Get "http://localhost:6688/v2/chains/evm": dial tcp [::1]:6688: connect: connection refused
$ chainlink keys eth create --evmChainID 1
Post "http://localhost:6688/v2/keys/evm?evmChainID=1": dial tcp [::1]:6688: connect: connection refused
$ curl -I https://mainnet.infura.io/v3/DELETED FOR SECURITY
HTTP/2 200
date: Sun, 13 Jul 2025 22:01:24 GMT
content-type: application/json
access-control-allow-origin: *
$ curl -I https://mainnet.infura.io/v3/SECURE
HTTP/2 200
date: Sun, 13 Jul 2025 22:01:28 GMT
content-type: application/json
access-control-allow-origin: *
$ exit
Additional Information
I've used chatgpt to try and help me create keys and it walks me through this loop of trying to change my config back and forth. i almost thing i have something wrong with my version or how i set up my config file. Once i figure out my chainID not registering issue i can officially start trying to run my chainlink node.