topologyUpdater.sh Error resultcode 403

Perfect, open the port in firewall like u did for first relay

It is open

6000/tcp ALLOW Anywhere

Ok, check from internet , I gave u earlier a site… check the port

it says its open on my public ips, but closed on my private ips

Then wait for the next message
Do u have any IN peers?

Block : 5385756 Tip (ref) : 22636920 │
│ Slot : 0 Tip (node) : 22636800 │
│ Density : 4.918 Tip (diff) : 120 :expressionless:
│--------------------------------------------------------------│
│ Processed TX : 0 Out / In │
│ Mempool TX/Bytes : 0 / 0 Peers : 4 0

4 out peers

Shoulld I do this on my block producer?
sudo ufw allow proto tcp from any to any port 6000

Nope, block producer should accept connections only from ur relays not from anyone

How it looks ur Producer? Has IN/OUT PEERS?

Cardano Node - (Core - Mainnet) : 1.25.1 [9a7331cc] <
┌────────────────────────┬────────────┬────────────────────────┐
│ Uptime: 02:30:19 │ Port: 6000 │ Guild LiveView v1.19.4 │
│------------------------└────────────┴────────────────────────┤
│ Epoch 250 [0.1%] (node) │
│ 4d 23:53:23 until epoch boundary (chain) │
│ ▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖ │
│ │
│ Block : 5385761 Tip (ref) : 22637197 │
│ Slot : 330 Tip (node) : 22637130 │
│ Density : 4.888 Tip (diff) : 67 :expressionless:
│--------------------------------------------------------------│
│ Processed TX : 0 Out / In │
│ Mempool TX/Bytes : 0 / 0 Peers : 4 0 │
├──────────────────────────────────────────────────────────────┤
│ KES current/remaining : 174 / 61 │
│ KES expiration date : 2021-05-26 09:44:51 UTC │
│--------------------------------------------------------------│
│ BLOCKS Leader | Adopted | Invalid │
│Since node start (EKG metrics) 0 | 0 | 0 │
└──────────────────────────────────────────────────────────────┘
TG Announcement/Support channel: Telegram: Contact @guild_operators_official

[esc/q] Quit | [i] Info | [p] Peer Analysis

Relay 1

Processed TX : 0 Out / In │
│ Mempool TX/Bytes : 0 / 0 Peers : 2 2

Relay 2
Processed TX : 0 Out / In │
│ Mempool TX/Bytes : 0 / 0 Peers : 2 2

So u connected ur relay each other right?

Why do u have 4 OUT peers ON Producer?

No idea what information do you need?

mainnet-topology.json

{
“Producers”: [
{
“addr”: “xx”, Relay 1
“port”: x,
“valency”: 1
},
{
“addr”: “xxx”, Relay 2
“port”: xx,
“valency”: 1
},
{
“addr”: “relays-new.cardano-mainnet.iohk.io”,
“port”: 3001,
“valency”: 2
}
]
}

Aa ok, u can delete IOHK relays from ur producer

Now, show ufw status (your nodes are on different servers same network right?

all the nodes are on different servers, in AWS

Block

--------------------------------------------------------------│
│ Processed TX : 0 Out / In │
│ Mempool TX/Bytes : 0 / 0 Peers : 2 0

Block

To Action From


x/tcp ALLOW x ssh
x/tcp ALLOW x relay 1
x/tcp ALLOW x relay 2

Then on producer type

sudo ufw allow proto tcp from relay1_ip to any port 6000
sudo ufw allow proto tcp from relay2_ip to any port 6000

But the nodes are on the same private network? They can comunicate via private ips, or via public ips?

Private network ips like 192.168…

No its not a private network , its just a private IP im using from amazon you get 1 public ip, 2 private ip, 3 public dns, 4 private dns That command didnt work:

sudo ufw allow proto tcp from xxx x to any port 6000
Skipping adding existing rule

Skipping… already is? Or why skipping

sudo ufw status:

To Action From


6000/tcp ALLOW x.x.x.x (Relay 1)
xxxx/tcp ALLOW SSH
6000/tcp ALLOW x.x.x.x (Relay 2)

Ok, let me try something…

Go to ur relays and type

telnet Producer_IP 6000

Should say connected