@Alexd1985
please what does this output mean?
It means u don’t have luck for epoch 261 to create a block 
Seriousely??
Unfortunately yes
Many thanks @Alexd1985
Hello,
That’s because u don’t have IN peers in Producer
Check the topology updater from ur relays… did u ran deploy-as-systemd and chose Y for topology updater (on both Relays only)?
If yes, did u added ur Producer IP and port in topology updater script to custom peers?
relays were installed deploy as systemd the BP didn’t… about your second question I don’t know what you mean but my relay can see the BP.
Go on ur relay to scripts folder
and type
nano topologyUpdater.sh
u should see a line custom peer — there u should add ur Producer IP + port amd delete the # from the begining
yeah, thank you very much. I forgotten to open port 6000 on BP, now my producer is working thank you
you are welcome, keep the port 6000 opened in the PRoducer only for your relay
Nope, is not, your BP has no IN peers (your relay)
you need to open the port in the Producer FW to allow incoming connection only from your relay
example sudo ufw allow proto tcp from Relay_IP to any port 6000
or check in relay side, topologyupdater script… if u added the producer IP + port to custom peers.
Cheers,
I just did option2:
“check in relay side, topologyupdater script… if u added the producer IP + port to custom peers.”
still no in from the producer. do i have to restart any service?.
any need for option1?.
thanks @Alexd1985 Tell me i am now ready for blocks 
@adgo123 & @Alexd1985 - I don’t see BLOCKS following stat " Ideal, Luck, Confirmed" in gLive display for my core-mainnet, am I missing something?
check your configuration with this topic from @Alexd1985
Thanks for your response. Figured it. Wasn’t running the CNCLI services. All good now.
U are, it looks fine
always u can check the status of the pool on pool.vet
I you want to check if you pool you can use: https://pool.vet/