But it’s on testnet right? 
Also I see 0/0 peers and no TX processes
Yeah it’s on testnet. I believe that the tools to show/allow P2P connections was a piece that was optional. Is that right or do I need it on the relay node?
I think the P2P is not released… so u will need to run topology updater script
This way u will announce the IP of the relay to other nodes
Okay cool. I already have that set up with a crontab. That’s what I set up to have my own topology list updated regularly. I had to change its path and customize that piece a bit but I think we got it movin’. So if I’ve minted a block already, does that mean it’ll wait until the next epoch to show that “produced block”?
Added a screenshot because I figure my question was confusing.
Nope, u should see the block already… but I see that the Producer has 0/0 peers… it should show 1/1 (your relay)
Also the relay needs to have IN peers
Would that be another issue with the configuration of the env file, or a firewall/port setting you think?
For Producer:
I see u started the Producer with port 3001… did u opened the port to accept connections from relay?
Also, did u added the relay inside the topology file?
For Relay:
U must have a script (if u followed the coincashew guide)… something with push…
There u should add the Producer IP + Producer port
run the script and restart the node
For relay u must opened the port to accept connections from any
For Producer:
did u opened the port to accept connections from relay? Also, did u added the relay inside the topology file?
Yes and yes. I just altered the env file to ensure that it’s pulling data from the right topology file for my custom setup
For Relay:
U must have a script (if u followed the coincashew guide)… something with push…
There u should add the Producer IP + Producer port
I think that you’re talking about this section for the topology pull, and yes I have that as well as opened the firewall to allow traffic to my port on the relay node.
But I don’t see the Producer IP + u have the 6000 port instead of 3001… is this yours or the default from guide?
try from
-
Producer
telnet relay_IP relay_port -
relay
telnet BP_IP BP_port
Do u see connected?
So my BP is supposed to communicate with my relay? I only set the relay to communicate with the BP
Yes, both should communicate
Okay. So what’s weird is that my BP is able to talk to my relay, but not vice versa. I used the telnet commands you suggested and found that for the BP to the relay, there is a connection successful message displayed. However, the relay trying the the BP gets a message that just says “Trying…” and never ends
In order for the BP to talk to the relay, I opened a port in the GCP firewall and updated the UFW rules. I did the same for the relay and still can’t seem to get the connection message. Any suggestions?
for BP, to allow connections from relay you must open the port shown in gLive (by default is 6000).
try also sudo ufw status, perhaps you have the firewall activated on server
if not, and you are using a LAN network, then check the PF configuration
to test if there is an issue wiht the GCP firewall configuration, disable it then try again the telnet command from relay
That helped substantially. Now both machines are connecting but the connect is “closed by foreign host”. I don’t know what else to check for at this point.
It’s fine if u see connected then closed message…
Now, the nodes should be able to connect to each other;
for relay run pull topology script then restart the node
With those steps performed, I still don’t see the block I minted yesterday listed for the stake pool. Did I just drop the block, or is there another step that I need to complete first?
nope, you will not see it… .I think it wasn’t propagated… but you have few millions staked so you should make more blocks per epoch… that’s why I tell u to check with CNCLI leaderlog…
anyway… .be sure that both nodes are connected to each other and the relay has another IN peers (other than the BP)
and both should have TX processed (if TraceMempool is set to false will not be visible on glive, you will net to set to true inside the config.json file)
Cheers

