Hello -
Hoping those who use TopologyUpdater can give me a hand… I believe I set everything up correctly yesterday, but I am not getting an updates. When I check the topologyupdater log I am seeing this error:
{ “resultcode”: “501”, “datetime”:“2021-02-13 14:20:23”, “clientIp”: “[My Relay IP]”, “msg”: “invalid hostname not pointing to client IP” }
Anyone know why?
Hello,
Did u changed this line?
CNODE_HOSTNAME="CHANGE ME"
Cheers?
I sure did. Do I need to add a port to the IP as well, or just my relay IP?
Nope, set it to default
Your name should be resolved by the IP in order to use it!
OK, yes it just lists my IP and has since yesterday, but still the error appears and no updates.
Change it to default and try again
The topology updater must be used only on relay and it should looks like that:
CNODE_HOSTNAME="CHANGE ME"
CNODE_VALENCY=1
MAX_PEERS=15
CUSTOM_PEERS="Ur_BP_ip:port"
To custom peers u can add more static connections if u have more trusted peers
CUSTOM_PEERS="Ur_BP_ip:port|other_node_IP:port"
Cheers,
Ah! I updated:
CNODE_HOSTNAME=“CHANGE ME”
And now got the respond “nice to meet you” so I assume that worked!
Thank you as always, Alex. It is very strange that the instruction says “CHANGE ME” but it does not want to be changed?!
Yes it can be used, but u didn’t read the instructions from the right… u can use the name only if ur IP solve it, like a dns record for ur IP…
You are welcome, anytime… after 4 runs (3 hours) u should see glade for staying with us…
Cheers,
@Alexd1985 I’m having a similar issue with this setup.
when changing: CNODE_HOSTNAME=“CHANGE ME”
to the public IP of my Block Producer do i leave the " " or remove completely? I’ve tried with, then changed it back to default, then without “” and get these messages
{ “resultcode”: “501”, “datetime”:“2021-09-22 06:27:00”, “clientIp”: “public IP removed for post”, “msg”: “invalid hostname not pointing to client IP” }
{ “resultcode”: “403”, “datetime”:“2021-09-22 08:27:00”, “clientIp”: “public IP removed for post”, “iptype”: 4, “msg”: “glad you want to stay with us, but please check and enable your IP:port reachability” }
{ “resultcode”: “501”, “datetime”:“2021-09-22 09:27:00”, “clientIp”: “public IP removed for post”, “msg”: “invalid hostname not pointing to client IP” }
CNODE_HOSTNAME=“CHANGE ME”
leave it default
4, “msg”: “glad you want to stay with us, but please check and enable your IP:port reachability” }
This is the right message but check if u opened the port to accept connections from any
as in check that the port is open on the servers firewall?
thanks for the quick reply btw 
Check here if the port is opened (the nide shoukd be 100% synced)
https://www.yougetsignal.com/tools/open-ports/
If not open the port in fw to accept connection from all (0.0.0.0/0) if u have a separate fw than ufw on server
Awesome, thankyou
@Alexd1985 hey sorry to ask again. This is open port 6000 only to the relay node. ports 3000 and 3001 dont need to be opened on the router/firewall to port forward, only 6000. ?
what i think im still confused about is the Block Producer only talks to the relay nodes on port 6000/6001 and shouldnt really see the outside internet. The relay nodes only see other relay nodes on ports 3000/3001, why does the relay node need port 6000 port forded to it and open on the external WAN firewall?
i.e., the node software only listens on port 6000 ?
This is open port 6000 only to the relay node. ports 3000 and 3001 dont need to be opened on the router/firewall to port forward, only 6000. ?
Right, only the port 6000 should be open (port 6000 is for IN connections) and on producer yes, u will need to open the port 6000 only for the relay, no other nodes should connect to the producer
what i think im still confused about is the Block Producer only talks to the relay nodes on port 6000/6001 and shouldnt really see the outside internet.
This is correct, the Producer should talk only with the relays
The relay nodes only see other relay nodes on ports 3000/3001, why does the relay node need port 6000 port forded to it and open on the external WAN firewall?
The relay must have have the port (the CNODE_port from env) opened for any, to accept connections from other public nodes
You will need a portforward only if your nodes are behind a private network… this way your local router will know to which server/IP should forward the incoming traffic (from other nodes)
ok cool, so on the Relay node, in the env file i should change:
CNODE_PORT=6000 # Set node port
to
CNODE_PORT=3000 # Set node port
and/or change on the Relay node, in the topologyUpdater.sh
CNODE_PORT=6000 # must match your relay node port as set in the startup command
to
CNODE_PORT=3000 # must match your relay node port as set in the startup command
Nope, wait… don’t change anything… 6000 it’s fine, forget about 3000,
What is your issue?
oh, i guess im still confused about what needs to talk to what.
Relay <–> BlockProducer ports 6000/6001
Relay <–> Other Relays ports 3000/3001
The issue is when i port forward 3000/3001 in my router to the Relay i get port closed. So it sounds to me like the node isnt listening on port 3000. However when i port forward 6000 its open, so the node software must be listening on port 6000.
and im still getting the same error once topologyUpdater runs:
“msg”: “glad you want to stay with us, but please check and enable your IP:port reachability”
ok, so, your nodes, producer and relay, are both behind the private network right?