Can't connect to insight-api


#1

I’m using bitcore-node to build an explorer on my customised bitcoin node.

Followed this instruction https://github.com/bitpay/bitcore-node/blob/master/docs/development.md

I’m able to run my mode using INSIGHT_FORCE_RPC_SYNC=1 bitcore-node start
but the inisight-api is not working. When I try to get my block info using http://localhost:3001/insight/blocks it keep giving me Waiting for blocks... all the time.

I believe the insight-api is not connected which cause this problem because when I try on http://localhost:3001/insight-api/block-index/0 I’ll get Method not found. Code:-32601

In addition, the command line keep popping up warning as following:
[2017-07-13T07:39:21.427Z] info: Starting bitcoin process
[2017-07-13T07:39:26.471Z] info: Bitcoin Height: 3122 Percentage: 47.59
[2017-07-13T07:39:26.474Z] info: Bitcoin Daemon Ready
[2017-07-13T07:39:26.474Z] info: Starting web
[2017-07-13T07:39:26.495Z] info: Starting insight-api
[2017-07-13T07:39:26.496Z] info: Starting insight-ui
[2017-07-13T07:39:26.496Z] info: Bitcore Node ready
[2017-07-13T07:39:26.963Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:26.964Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:26.964Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:26.964Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:27.464Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:27.464Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:27.464Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:27.964Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:27.964Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332
[2017-07-13T07:39:27.965Z] warn: ZMQ connection delay: tcp://127.0.0.1:8332

I’ve searched a lot but could not find a solution for this. Anyone have a suggestion how to get it work?


(Kiran Devkar) #2

Yes, I am also facing same problem.
Does anyone has solution ?


(Mehdi) #3

I also have same problem. Is there a solution for these kind of errors?