Unable to Establish Connection between relay and BP

Hello everyone,

I have a problem with my Cardano nodes and i don’t know hot to solve it.
I have three nodes all running on version 1.35.7.

Node 1 is my block producer with port 6000,
Node 2 is my relay with port 6001,
Node 3 is another relay with port 6005.

Currently, Node 2 is set up as the P2P.

My BP is connected to Node 2, and I have both peer-in and peer-out and transactions processed. However, with Node 3, I can only establish peer-out connections

Node 2 is connected to both BP and Node 3, with peer-in and peer-out connections, and transactions processed.

Node 3 is connected to Node 2 with both peer-in and peer-out connections, but it cannot connect to BP.

My BP and Node 2 are on the local network, whereas Node 3 is on a VPS on Contabo. Both nodes on the local network are under DNS.

Here is the topology for my BP:

{
"Producers": [
{
"addr": "node 2 ip",
"port": xxxx,
"valency": 1
},
{
"addr": "node 3 ip",
"port": xxxx,
"valency": 1
}
]
}

Here is the topology for my Node 2:

{
"localRoots": [
{ "accessPoints": [
{ "address": "BP ip", "port":xxxx },
{ "address": "node 3 ip", "port": xxxx }
]
, "advertise": false
, "valency": 1
}
]
, "publicRoots" : [
{ "accessPoints": [
{ "address": "relays-new.cardano-mainnet.iohk.io", "port": 3001 }
]
, "advertise": true
, "valency": 1
}
]
, "useLedgerAfterSlot": 0
}

And here is the topology updater for Node 3:

CNODE_HOSTNAME="IP"
CNODE_VALENCY=1
MAX_PEERS=15
CUSTOM_PEERS=" DNS,xxxx|DNS,xxxx|relays-new.cardano-mainnet.iohk.io,3001,1"

I have opened the port in the UFW of my BP to accept incoming connections only from my relays, but Node 3 still cannot connect.

Ufw on bp


163/tcp                    ALLOW       Anywhere
6000/tcp                   ALLOW       node 2 ip
6000/tcp                   ALLOW       node 3 ip
163/tcp (v6)               ALLOW       Anywhere (v6)

I have also noticed an error in the log file in the Cardano node folder, which reads as follows:

{"app":[],"at":"2023-04-23T13:36:14.29Z","data":{"domain":""DNS"","event":"Failed to start all required subscriptions","kind":"SubscriptionTrace"},"env":"1.35.7:f0b4a","host":"vmi11779","loc":null,"msg":"","ns":["cardano.node.DnsSubscription"],"pid":"1876762","sev":"Warning","thread":"600"}

Could this be related to my issue?
Any help or suggestions would be much appreciated.

i have another question, How many IN peers should I have with a p2p node on mainnet?
currntly i have only 7 peer… on preprod testnet i reach over 200, is ok?
image

thanks in advance guys

Try to replace BP DNS with BP IP

for 2nd question… I can’t answer because I don’t know how many people set P2P on nodes… so it will depend about this… but for preprod can you help @Betterloop with topology updater configuration? I mean whici magin number did u use?

2 Likes

thanks for reply
Done but nothing changed my node 3 can’t connect to the bp anyway i can’t use the IP because it is not static

for relay on p2p no problem i’m on mainnet, probably i need to wait that other people going on p2p

Hello NotMick3,

When you Created the topologyUpdater.sh script which publishes your node information to a topology fetch list. Did you alter the command on Pre-prod testnet ? I did just copy paste the command without changes.
I just get 1 incoming connection, and i have waited a few days.

Best regards,

1 Like

Hi, I’m not sure if I understood your question correctly, but currently I’m on the mainnet and I’ve modified the topologyUpdater.sh script with the DNS and port of other nodes.
I didn’t create the script myself.
At this point, I’m not sure if 7 incoming peers are okay or not
and i’m using cntools

1 Like

Try from relay

telnet dns xxxx
dns of BP
xxxx is the BP port
U should see connected

PS: u said the IP its not static but on BP under FW rules u added/permited the IP of Relay… perhaps the IP changed?

good morning, sorry for my late reply
wait my BP and my node 2 are under dns and they communicate with each other through the local network at my home
my node 3 is on other network.
and if i try telnet from my node 3
image

Solved… my fault i made a mistake with the ip on my modem