Return to Question

--- EDIT 2021-09-27 ---

Turns out my bitcoind was not syncing due having enough swap and server constantly shuts down / kernel panic.

After syncing and reenabled swap... it is back to the orginal error message but at a different location (node:internal/process/task_queues:78:11) and there seems to be some communication going on between lndhub with bitcoind! :)

bitcoind getblockchaininfo: {
  result: {
    chain: 'main',
    blocks: 702459,
    headers: 702459,
    bestblockhash: '0000000000000000000a45d676fc178cc7603ca7908af2ed1701137a848db5d3',
    difficulty: 18997641161758.95,
    mediantime: 1632764543,
    verificationprogress: 0.9999990028709793,
    initialblockdownload: false,
    chainwork: '0000000000000000000000000000000000000000221092943f73a5bddde80438',
    size_on_disk: 416306659033,
    pruned: false,
    softforks: {
      bip34: [Object],
      bip66: [Object],
      bip65: [Object],
      csv: [Object],
      segwit: [Object],
      taproot: [Object]
    },
    warnings: ''
  },
  error: null,
  id: '883e89b6-7c7e-4cd5-aa8e-a6e54879ae62'
}
lnd failure
Error: 2 UNKNOWN: encoding/hex: invalid byte: U+002F '/'
    at Object.callErrorFromStatus (/opt/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24)
    at Object.onReceiveStatus (/opt/LndHub/node_modules/@grpc/grpc-js/src/client.ts:338:36)
    at Object.onReceiveStatus (/opt/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34)
    at Object.onReceiveStatus (/opt/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
    at /opt/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
    at processTicksAndRejections (node:internal/process/task_queues:78:11) {
  code: 2,
  details: "encoding/hex: invalid byte: U+002F '/'",
  metadata: Metadata {
    internalRepr: Map(1) { 'content-type' => [Array] },
    options: {}
  }
}

I updated bitcoin-core to v22. now lnd seems to be somewhat working, and now I have to figure out how to get rpc to run for lnd, as below seems to indicate "rpc is not running"?

I updated bitcoin-core to v22. now lnd is giving a different error from rpcperms/interceptor.go... and I have to figure out how to get rpc to run for lnd, as below seems to indicate "rpc is not running"...

I guess my next step is probably to add some print statements somewhere in the LnhHub code. Will update this post after I do that.

LnhHub logs:

https://github.com/pangyuteng/bitcoin-lndhub/blob/main/docker-compose.yml
bictoind: https://github.com/pangyuteng/bitcoin-lndhub/blob/main/bitcoind/Dockerfile
lnd: https://github.com/pangyuteng/bitcoin-lndhub/blob/main/lnd/Dockerfile
LndHub: https://github.com/pangyuteng/bitcoin-lndhub/blob/main/hub/Dockerfile

I guess my next step is probably to add some print statements somewhere in the LndHub code. Will update this post after I do that.

LndHub logs:

https://github.com/pangyuteng/bitcoin-lndhub/blob/main/docker-compose.yml
bictoind: https://github.com/pangyuteng/bitcoin-lndhub/blob/main/bitcoind/Dockerfile
lnd: https://github.com/pangyuteng/bitcoin-lndhub/blob/main/lnd/Dockerfile
LndHub: https://github.com/pangyuteng/bitcoin-lndhub/blob/main/hub/Dockerfile

--- EDIT 2021-09-22 ---

I updated bitcoin-core to v22. now lnd seems to be somewhat working, and now I have to figure out how to get rpc to run for lnd, as below seems to indicate "rpc is not running"?

export LND_DIR=/mnt/hdd/lnd
export MACAROON_HEADER="Grpc-Metadata-macaroon: $(sudo xxd -ps -u -c 1000 $LND_DIR/data/chain/bitcoin/mainnet/admin.macaroon)"
curl -X GET --cacert $LND_DIR/tls.cert --header "$MACAROON_HEADER" https://localhost:8080/v1/balance/blockchain

{"error":"the RPC server is in the process of starting up, but not yet ready to accept calls","code":2,"message":"the RPC server is in the process of starting up, but not yet ready to accept calls","details":[]}