Relay not listed in topology.json

Hi Mattonecz,
If you check Adapools you can see the public IP = 78.102.209.253 and port is 6001 for your pool.
If you check that IP with Port checker, it is open. As you mentioned 192.168.0.101 as the internal address, i assume you are running from home. It could be likely the port forwarding thing Alex is mentioning. Make sure your modem settings are correct by pointing port 6001 to address 192.168.0.101. Make also sure this address is not obtained by DHCP, make it static.

he already replied me via DM (being a new member had limited posts)… it was an issue with the env file configuration and he fixed (wrong CNODE_port).

1 Like

hi, yes its already fixed. it was wrong configuration of gLiveView. I was connected but didnt see it

1 Like

We have https://explorer.mainnet.cardano.org/relays/topology.json as explorer for the main net.

Is there also a node explorer for the testnet ?

yes,

NOTE: Here you can find peers to connect to, and submit your own relay’s data: https://explorer.cardano-testnet.iohkdev.io/relays/topology.json

cheers,

1 Like

Perfect, thanks.

hi, having issues with a second relay not showing in the mainnet topology.json.

running cntools, the topologyUpdater.sh. output below;

{ “resultcode”: “204”, “datetime”:“2021-11-16 06:00:20”, “clientIp”: “203.51.0.29”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-11-16 07:00:24”, “clientIp”: “203.51.0.29”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-11-16 08:00:27”, “clientIp”: “203.51.0.29”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-11-16 09:00:30”, “clientIp”: “203.51.0.29”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-11-16 10:00:34”, “clientIp”: “203.51.0.29”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-11-16 11:00:37”, “clientIp”: “203.51.0.29”, “iptype”: 4, “msg”: “glad you’re staying with us” }

portchecker says port 3000 is open

Why u are saying this is an issue?
be patient… and check the pool on pool.vet

was expecting it to be up within say 12hours, i can be patient till the morning :slight_smile:

pool vet seems to be showing outdated data.

i mean, my ticker is rob, a while ago it used to be robot.

I suppose you registered a new certificate?

yes, got a “Transaction successfully submitted” with relays part like below, late here will check again and confirm in the morning. thanks.

–pool-relay-ipv4 52.63.243.155
–pool-relay-port 3000
–pool-relay-ipv4 203.51.0.29
–pool-relay-port 3000 \

Everything seems fine at pool.vet
Your new relay is there and it’ll take some time to sync the rest

Wait more days and u will see the Relay on main topology :wink:

morning, when checking my dbsync i can see my new relay in the pool_relay table, however not in the json file yet, waiting… waiting… no hurry :slight_smile:

image

hmmm, still not showing (9 days), any ideas?