Skip to content
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

Error ECONNREFUSED when using offckb independently #206

Open
tea2x opened this issue Jan 9, 2025 · 1 comment
Open

Error ECONNREFUSED when using offckb independently #206

tea2x opened this issue Jan 9, 2025 · 1 comment

Comments

@tea2x
Copy link

tea2x commented Jan 9, 2025

Hi everyone, thank you for your excellent project. Spinning up a CKB node is so easy with offckb.

After offckb node I tried running offckb deploy and offckb transfer independently. They both produces theECONNREFUSED error. For example:

$ offckb deploy --target ./build/sphincsplus_lock --config offckb.config.ts
node:internal/deps/undici/undici:11731
    Error.captureStackTrace(err, this);
          ^

TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11731:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async TransportHttp.request (/Users/tung/.nvm/versions/node/v18.19.1/lib/node_modules/@offckb/cli/node_modules/@ckb-ccc/core/dist.commonjs/client/transports/http.js:12:28)
    at async ClientPublicTestnet.send (/Users/tung/.nvm/versions/node/v18.19.1/lib/node_modules/@offckb/cli/node_modules/@ckb-ccc/core/dist.commonjs/client/jsonRpc/index.js:254:22)
    at async ClientPublicTestnet.findCellsPagedNoCache (/Users/tung/.nvm/versions/node/v18.19.1/lib/node_modules/@offckb/cli/node_modules/@ckb-ccc/core/dist.commonjs/client/jsonRpc/index.js:225:34)
    at async ClientPublicTestnet.findCellsPaged (/Users/tung/.nvm/versions/node/v18.19.1/lib/node_modules/@offckb/cli/node_modules/@ckb-ccc/core/dist.commonjs/client/client.js:91:21)
    at async ClientPublicTestnet.findCellsOnChain (/Users/tung/.nvm/versions/node/v18.19.1/lib/node_modules/@offckb/cli/node_modules/@ckb-ccc/core/dist.commonjs/client/client.js:98:43)
    at async ClientPublicTestnet.findCells (/Users/tung/.nvm/versions/node/v18.19.1/lib/node_modules/@offckb/cli/node_modules/@ckb-ccc/core/dist.commonjs/client/client.js:121:26)
    at async SignerCkbPrivateKey.getAddressObjs (/Users/tung/.nvm/versions/node/v18.19.1/lib/node_modules/@offckb/cli/node_modules/@ckb-ccc/core/dist.commonjs/signer/ckb/signerCkbPublicKey.js:48:26)
    at async SignerCkbPrivateKey.findCells (/Users/tung/.nvm/versions/node/v18.19.1/lib/node_modules/@offckb/cli/node_modules/@ckb-ccc/core/dist.commonjs/signer/signer/index.js:138:25) {
  cause: Error: connect ECONNREFUSED ::1:8114
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
    errno: -61,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '::1',
    port: 8114
  }
}
@RetricSu
Copy link
Collaborator

RetricSu commented Jan 9, 2025

hmm, not sure why this happens but it seems strange to me that it used the address: '::1' ipv6 ? the node should be running in the ipv4 address 127.0.0.1:8114 why does it choose the ipv6

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

2 participants