Unclear how to access the insight api about bitcore-node HOT 6 CLOSED

A port will be assigned for you by default. I explained all this in a previous comment:
#1 (comment)

Let me know.

from bitcore-node.

Thanks. I tried using:
docker run --rm -P -v /root/bitcoin-node --name testnet jeshan/bitcore-node
To run the image and open localhost:49153 in the browser but I keep getting ERR_EMPTY_RESPONSE (any other port number gets me a ERR_CONNECTION_REFUSED). I'n running docker in Win 10 with WSL2. But that should not make a difference I think.

Am I right that I should see a webpage, even if it is still syncing the blockchain? Starting web, Insight UI & API messages were without error. So I am expecting that the webserver should be up and running pretty fast after starting the container.

from bitcore-node.

did you open the urls as shown in my screenshots there? it shows that both insight and api are working.

from bitcore-node.

Yes,
http://localhost:49153/insight
and
http://localhost:49153/insight-api/tx/send

error message is "this page does not work, localhost did not send data"

also no strange things here:

from bitcore-node.

There are different ports at play here. Look closely at the example docker run just gave me:

9cee5f5154e9        jeshan/bitcore-node   "/usr/bin/dumb-init …"   9 seconds ago       Up 6 seconds (health: starting)   0.0.0.0:32772->3001/tcp, 0.0.0.0:32771->3232/tcp, 0.0.0.0:32770->6667/tcp, 0.0.0.0:32769->8333/tcp, 0.0.0.0:32768->18333/tcp   testnet

The one that is mapped to port 3001 (here 32772 on the host) is the correct one to access the insight UI:

This same port exposes the api:

I'll let you find out what the other ports are for. You'll have to manage now. I haven't worked on bitcore for years and can hardly remember these details.

from bitcore-node.

YES! It was 49157. Could see that one mapped to 3001.
Thanks a lot!

from bitcore-node.