How can I connect localhost:3000 using symbol-bootstrap in mainnet

Tech Support
#1

Hello, everyone.

I’m trying to run peer node for harvesting in mainnet with symbol-bootstrap.
I’ve confirmed the node is listed in “Symbol node list”(https://symbolnodes.org/nodes/), so that the node seems to me to running and syncronizing in network now.

however, I can’t access the node info by localhost: 3000. I don’t know why, but port 3000 doesn’t opened in docker network anyway, and I’ve struggling this problem for 2 days. how can I open the port 3000 in docker. or in the first place, Is my understanding about peer node is incorrect ?

According to the document of symbol-bootstrap, port 3000 is utilized for REST Gateway, it’s function provided by API node. so it seems that port 3000 opening doesn’t need if I build only peer node ( in host OS layer, I opened port 3000, though).

Of course, in this state, I got an error for getting AccountKeyLink and VrfKeyLink transactions, too: FetchError: request to http://localhost:3000/node/info failed, reason: connect ECONNREFUSED 127.0.0.1:3000 Code: ECONNREFUSED.

What can I do to fix this problem?

#symbol-bootstrap healthCheck result.

Container node is running
Container node port 7900 → 7900 is open
Network is running!

#my peer node information from “symbol node list”.
IP / DNS: 160.16.147.26
Port: 7900
Supernode:
Harv :
Network: MAIN_NET
Ver: 16777216
Role: peer
Name: DF8E387
Location: Japan
Height:
Final:
E:
P:
latest update : v1.0.0.0
Last check:

#my environment.
Host: VPS in Japan
OS: Ubuntu 20.04.1 LTS
npm version: 7.6.3
node.js version: v14.16.0
docker version: 20.10.5
docker-compose version: 1.27.4
symbol-bootstrap version: 1.0.1

#my hostOS(Ubuntu) ufw status
Status: active
To Action From
55522 ALLOW Anywhere
3000 ALLOW Anywhere
7900 ALLOW Anywhere
22/tcp ALLOW Anywhere

#2

You used option “-a peer” when configuring your node, you should have used “-a dual” if you want api running on your node too: Running a Symbol node — Symbol Documentation

As an alternative, you can have a peer only node and add “–useKnownRestGateways” option when registering links: Enrolling to the Supernode program — Symbol Documentation

#3

Thank you,rigel.

Yes, I’ve used -a option when starting the node up because I wanted to build only peer node.

So, I also add —useKnownRestGateways option when entering symbol-bootstrap link command, but I got an error, for due to access to localhost:3000 failured.

The error message is :

There has been an error talking to node http://localhost:3000. Error: request to http://localhost:3000/node/info failed, reason: connect ECONNREFUSED 127.0.0.1:3000}

Connecting to node http://ngl-dual-001.symbolblockchain.io:3000
Node’s minFeeMultiplier is 35
Node signing account ND7POZLEPLWMRY7VADNVMMBTZ2IGZIAR7TWUUFY is not valid.

This is the reason why I want to connect localhost:3000, even if I build peer node only.

but is this messages indicate that if I have 35 XYM in the account ND7POZLEPLWMRY7VADNVMMBTZ2IGZIAR7TWUUFY, doesn’t need to open port 3000? ( I don’t have it.)

#4

I’m sorry rigel, I’ve built new dual node to test.
Now, I can connect localhost:3000, and network is running well.

Thank you!