No IN Peers

You are right env port was 6000 not 6001. Alex thanks a lot :slight_smile:

I have another guestion do You know what can be wrong if my Peers in IN connection is unreachable?

unreachable

Press info [I] and read the details :slight_smile: you are welcome!

I read it but i am not sure if i understand. It means that this is ok?

Yes, it’s because the peers doesn’t respond to ping (icmp filtered)

But as long the peers are present, is fine

Thanks :slight_smile: Have a nice day :slight_smile:

3peers

Is this ok if i have 1 Out and 3 In on BP?

Depends on how many relays you are connected to. I would assume you are fine here.

i have one relay

if you have 1 single Relay, why on Producer u have 3 peers IN? should be only your relay there;
do u run the topology updater scirpt on Producer?

Cheers.

No i run topology updater just on relay and in topology file on BP node i have just one producer and is address of relay

Ok, how many peers do u see to IN on the Producer?

3peers-2

Ok; understand…

On ur producer type

sudo ufw allow proto tcp from Relay_Ip to any port 6001

sudo ufw reload

Restart the node

This way u will allow connections only from ur relay

i cannot start BP i have:

COULD NOT CONNECT TO A RUNNING INSTANCE, 3 FAILED ATTEMPTS IN A ROW!

It didnt restart for 9 days, maybe is something with Mary era?
Relay is working, i restarted.

journalctl -e -f -u cnode.service

Or

journalctl -e -f -u cardano-node.service

Thank you it showed me that i do not have permissions so i did that and is ok:
chmod 400 vrf.skey

And at the moment i have 1 IN.
Have a nice day and thxt! :slight_smile:

1 Like

HI, would you tell me please where you modify that 'env port ? thanks a lot

In env file

nano env and replace cnode port which by default it’s 6000 with ur desire port