-
Notifications
You must be signed in to change notification settings - Fork 641
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
Run the daemon and insight API on two distinct servers #549
Comments
I am sure the Bitcore v5.0 can support it. In the previous versions of Bitcore, it connects to a custom bitcoind. You can find the doc here: |
Yes, I know> So I tried to start with this :
And it don't work : [2018-02-22T01:10:43.637Z] info: ::ffff:172.17.0.1 "GET /insight-api/blocks" 200 - 1.130 "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36" [2018-02-22T01:10:43.637Z] info: ::ffff:172.17.0.1 "GET /insight-api/blocks" 200 - 1.130 "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36" |
I think, Insight API is connected to the daemon : But, When I look for get block or transaction, insigh api dont found this. |
Hello,
I'd like to run the bitcoin daemon and insight api on two servers :
Do you know if it's possible ? I tried a lot of different configuration, but it don't work...
{ "network": "livenet", "port": 3001, "services": [ "header", "insight-api", "insight-ui", "web", "p2p", "db", "block", "timestamp", "mempool", "transaction", "address", "fee" ], "servicesConfig": { "bitcoind": { "connect": [ { "rpchost": "DAEMON_URI", "rpcport": 8332, "rpcuser": "toto", "rpcpassword": "toto", "zmqpubhashtx": "tcp://DAEMON_URI:28332", "zmqpubhashblock": "tcp://DAEMON_URI:28332", "zmqpubrawblock": "tcp://DAEMON_URI:28332", "zmqpubrawtx": "tcp://DAEMON_URI:28332" } ] }, "insight-api": { "disableRateLimiter": true, "translateAddresses": process.env.translate, "cwdRequirePath": "node_modules/insight-api" }, "insight-ui": { "cwdRequirePath": "node_modules/insight-ui" } } }
The text was updated successfully, but these errors were encountered: