CoinCashew Guide: Step 8 issue. Cannot get Block Producing Node to Communicate

[babylon]

I am following the CoinCashew guide and I am stuck at step 8. I am unable to get my block producing node to communicate.

I am attempting to create a block producing node and one relay node. Both are AWS Ubuntu Server 20.4 LTS, t3.large, 2 cores, 8Gb RAM and 20GB of storage. My block producing node has been assigned a static IP address (34.248.243.132), and the relay node also has a static IP address (52.210.145.85).

My Relay node appears to be up and running but my block producing node not so.

Block producing node (gLiveView)

The block producing node, journalctl --unit=cardano-node --follow readout:

Relay node (gLiveView):

Block producing Node (mainnet-topology.json):

Relay Node (mainnet-topology.json):

Please can someone advise?

[laplasz]

Hi!

Check the port connectivity between the two nodes…
so now both nodes listening on port 6000.
but the question is that whether the ports can be reached from the other node.
So to check the connection, use command netcat -vnz 52.210.145.85 6000 from BP node; and netcat -vnz 34.248.243.132 6000

[babylon]

@laplasz , so i tried:
netcat -vnz 52.210.145.85 6000 from BP node &
netcat -vnz 34.248.243.132 6000 from the relay node.

Both came back with the following:
netcat: connect to 34.248.243.132 port 6000 (tcp) failed: Connection timed out

Please can you advise me?

[laplasz]

have you opened the ports on the firewall/cloud settings?

[babylon]

@laplasz I’m not sure how to so that at this stage. I am using AWS. I don’t suppose you might be able guide me? I was thinking at this stage looking into the security groups of each Ubuntu instance?

[laplasz]

inbound rules! I am not using AWS but here is a topic where they have issues with connectivity:

Issue connecting to AWS relay nodes

Good morning all, I would like to state upfront that I am VERY new to this and my background is in evolutionary biology I have set up 2 relays as AWS ec2 instances, they are running very well and are in sync with the blockchain. Now I would like my local machine to talk exclusively to them, but I am having trouble. So: I have modified the mainnet-topology.json file in both relays to look like this: { “Producers”: [ { “addr”: “relays-new.cardano-mainnet.iohk.io”, “port”: 30…

user guide to setup inbound rules:
https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html

if you have questions may someone else will guide you here, or just open a new topic with a specific question regarding to how to open port in AWS

[babylon]

@laplasz thank you so much. both nodes are now communicating after setting the inbound and outbound rules for the security groups of both nodes. BP node can only communicate to with the relay node, and the relay node should be allowed to communicate with the BP node and everyone else.

[laplasz]

good - also check http://pool.vet if you registered your pool.

[babylon]

i aint got that far yet:) But I hope to get there!

[Denereum]

Hey there i just saw this, i posted a post this morning about me using coincashew to setup a cardano node, on your block producer node it should say core -mainnet and not relay, so i believe there is an issue there. I just noticed the pictures. and thought i’d let you know as well

[babylon]

@Denereum Thanks for that. I did notice that. was wondering why it was saying “relay - Mainnet”…

[Denereum]

Hey there i found a better link for an install tutorial: Installing the node from source