I had the same issue and finally resolved it:
I am running my relays on network 192.168.1.XX just behind my modem with port forwarding.
My block-producing node is connected to the relays via ethernet on a private network 10.0.0.XX .
I had initially set up my cardano-node run command (as a startRelay1.sh) with HOSTADDR as 10.0.0.12 which was working fine with my setup, until I started using the topologyUpdater script. I realised that my Relays were connecting properly to the network but no longer open to connections for my Block-Producing node.
Finally figured out that with a setup that uses two network adaptors (Wifi on 192.168.1.XX and ethernet on 10.0.0.XX), I needed to use HOSTADDR= 0.0.0.0 in the cardano-run command, as below.
Now everything runs perfectly!
- #!/bin/bash
- DIRECTORY=/home/relay2/cnode
- PORT=3002
- HOSTADDR=0.0.0.0
- TOPOLOGY=${DIRECTORY}/config/mainnet-topology.json
- DB_PATH=${DIRECTORY}/db
- SOCKET_PATH=${DIRECTORY}/sockets/node.socket
- CONFIG=${DIRECTORY}/config/mainnet-config.json
- ~/.local/bin/cardano-node run --topology {TOPOLOGY} --database-path {DB_PATH} --socket-path {SOCKET_PATH} --host-addr {HOSTADDR} --port {PORT} --config {CONFIG}
1 Like
Hi Alex,
Does the Node Port listed on https://explorer.mainnet.cardano.org/relays/topology.json files have to be the same as the Port that the Relay is listening to internally?
my modem forwards outsider 5551 port to my relay 192.168.xx.xx address and port.
My relay looks fine on pool.vet, but i’m still getting the “glad you want to stay with us, but please check and enable your IP:port reachability” message in topologyupdater.json log
Thanks
Can u check here if the relay port is opened…
also check if u started the node with the port registered
yes, the beehi-relay1.ydns.eu:5551 checks as open.
But the node starts with an internal port that my modem forwards the 5551 to.
should I make them identical?
External port is 5551 and internal port is 1971
my modem blocks all traffic and fwd 5551 port to 1971
only 2. my BP and an IP that i asked about on the Telegram Stakepool247 Support Group. it’s unreachable and always on my In peers
the IP is 204.236.161.163
I’ve had days where there was more connected peers… but I upgraded my modem and relay recently…
Should I make both ports(external and internal to my network) identical and see if that works?
it’s up and running on 5551. BP is the only connected peer. that weird IP is gone!!
But Processed TX is not moving anymore.
I’ll wait for the topologyupdater refresh and check on the log
Node restarted.
BP is the only IN peer.
16 OUT peers
Proc TX and Mempool at 0 and not moving
Only 1 entry in the topology log. msg :“nice to meet you”
When it ran last time topology updater?
Check if the job was added in crontab
crontab -e
On adapools.org the relay is red
Also check the metadata
https://pool.vet/#BeeHive%20Pool
hmmm… It’s weird that the relay is red on adapools.
The pool.vet link you have isn’t my pool! here’s my pool’s link
https://pool.vet/#BEEHI
no crontab!
I just rebooted the relay
still no change
relay1.ydns.eu:5551 is onboarding on topologyUpdater
good sign
The relay could be red because u didn’t ran topology updater… should see glade u are staying with us
Now it shows “glad you’re with us”
But Processed Tx and Mempool still dead on 0
BP is the only IN peer
16 OUT peers
Now, the relay is green in adapools… soon other nodes will connect to ir relay…
yes, it’s back up and running.
thank you so much for all your help! you rock 
1 Like
Hi Alex,
How excited should I be when the BP node reads:
Blocks Since node start Leader 1 | Adopted 1 | Invalid 0
Does that mean it minted a block?!!?
Should I ask this in a different section of the forum?
Thanks
1 Like
wooohooooo!!! Amazing!! First block EVER!!!
Did anyone tell you today that you f**** ROOOOOOCK?!?!
thank you again a million times
1 Like
