AWS Specific Question: Port 6000 or Port 3000 BP to Node not working

Staking & Delegation Setup a Stake Pool
1

Hi Folks,
I just can’t get my Block Producer to talk to my Relay. I really think everything is correct, but clearly it is not. The relay launches on Port 3001 and talks to IOHK. Data is flowing in, but the relay reports an erro with the correct IP on the correct port:

BP IP: 172.10.10.10
NODE IP: 172.11.11.11

RELAY ERROR
0.0.0.0:0 [172.10.10.10:6000] Restarting Subscription after 1.027140911s desired valency 1 current valency 0

RELAY CONFIG

  1. Start Node with with 0.0.0.0
  2. Security Groups Outgoing in AWS Port 6000 TCP 172.10.10.10/32
  3. Security Groups Incoming in AWS Port 6000 TCP 172.10.10.10/32

{
“Producers”: [
{
“addr”: “172.10.10.10”,
“port”: 6000,
“valency”: 1
},
{
“addr”: “relays-new.cardano-mainnet.iohk.io”,
“port”: 3001,
“valency”: 2
}
]
}

BLOCK PRODUCER
Error: Trying to connect to 172.11.11.11:6000 Waiting 0.025s before attempting a new connection

BP CONFIG

  1. Start Node with with 0.0.0.0
  2. Security Groups Outgoing in AWS Port 6000 TCP 172.11.11.11/32
  3. Security Groups Incoming in AWS Port 6000 TCP 172.11.11.11/32

{
“Producers”: [
{
“addr”: “172.11.11.11”,
“port”: 6000,
“valency”: 1
}
]
}

The to AWS instances have the same VPC ID and Subnet ID.

Any suggestions are appreciated.

Thank you,

TFPJ

2

Check the fw

Try to connect from each node to another

Producer:

telnet 172.11.11.11 6000

Relay

telnet 172.10.10.10 6000

u should see connected, if not please check the rules on fw

3

Have you done a public-facing port check? Take a look at a port-checker site like https://canyouseeme.org/ - I had similar problems with diagnosing connectivity and that helped determine the FW wasn’t setup correctly

4

AWS does not include TELNET by default … :frowning: I’m searchign for an install or a similar solution now …

Thank you,
TFPJ

5

Then check the aws firewall and servers firewall

The producer should accept connection from your relay only on port 6000 and the relay should accept connections from any on port 6000

But the nodes should be synced before to connect them

6

Hi, maybe I am not waiting long enough for the relay to sync. Ill give it more hours tomorrow.

Thank you

7

For connection tests you can use netcat aka nc and to display your firewall rules, provided you’re using some GNU/Linux distribution it’s sudo iptables -nvL. For instance

$ nc -v 172.11.11.11 6000

You may also use netcat to check connections to any IP and port, in case of a physical firewall or fw on another host. Telnet itself tends to disappear as it’s not secure, replaced by SSH. As for the node, you should be able to check the logs, no ? Or look for any network activity using tcpdump on the ports you defined.

8

The db directory was corrupted - it was not the ports … I misread the error messages …

Thank you guys for the help … I was determined to solve the issue instead of reinstalling … I erased the db folder and the relay is now working …

TFPJ