Log Error With Topology Updated

Staking & Delegation Setup a Stake Pool
#1

I am having an error in the logs when topology updater runs.

{ “resultcode”: “403”, “datetime”:“2021-01-31 15:22:04”, “clientIp”: “65.52.18.195”, “iptype”: 4, “msg”: “glad you want to stay with us, but please check and enable your IP:port reachability” }

I found a post referring to the firewall, which I fixed and restarted the node. Still no luck. Also port forwarding is setup on both block producer and relay.

Additionally my relay does not show up on https://explorer.mainnet.cardano.org/relays/topology.json

#2

Check the port, it seems to be closed (perhaps u have aditional fw in cloud);
this log is from relay right? Both are running on the same server?
What port do u set for relay?

Cheers,

1 Like
#3

Ports 6000 and 3001 are open in cloud and firewall is off to test if that is the problem. Yes this log is on the relay. They’re cloud servers running on the same network. BP and Relay are communicating fine though relay only has 1 peer in.

#4

Both ports are closed in fw

image image

Check your cloud fw, u should add a rule 0.0.0.0/0 to allow all trafic to specific port

Cheers,

#5

Got it, I was able to open port 6000 on the cloud fw, for some reason 3001 was opened but isnt showing it was opened, Im using microsoft azure. Any ideas

#6

What port are u using for relay 6000 or 3001?

#8

Both 3001 to talk to relay node network and 6000 between my BP node

#9

I don’t get it… what port did u seted in env file for relay… or what port are u using when u start the relay (in case u don’t have the env file)?

I see port 6000 open and 3001 still closed… please check again the port 3001.

What is your pool ticker?

#10

my CNODE port in env file is 6000BP1 Relay1
Also here is the 2 live views of my nodes incase that helps

#11

Ok, so for relay u are using 6000, great now it shows open, wait for the next topology run and check the logs again… should be fine now

What is ur pool ticker?

#12

Got it thank you! Pool ticker is TAPIA

#13

Ok, let me know the status

#14

Sorry for the late response, pool shows up on adapools and yoroi though it isn’t showing on daedulus or pooltools

#15

Hey,

We are experiencing the same issue here but our ports appear to be open. Out topology updater gives the following result:
{ “resultcode”: “403”, “datetime”:“2021-03-15 10:53:00”, “clientIp”: “3.16.55.22”, “iptype”: 4, “msg”: “glad you want to stay with us, but please check and enable your IP:port reachability” }

But when we check for port availability we get:

Captura de ecrã 2021-03-15, às 11.03.52
Captura de ecrã 2021-03-15, às 11.03.521148×664 111 KB

We’re reaching out to other relays but we don’t have any inbound records other than our BP.

Any ideas on how to solve it?

Many thanks in advance.

#16

sudo ufw status… did u opened the port 3001 for all incoming connections right?

#17

Hey @Alexd1985 !

Yes, it is open. This is running in the cloud so I don’t have root privilege to run “ufw” but I’ve opened 3001 to all incoming connections, but it is still not receiving any.

#18

I’ve just launched a new instance to check if it reaches the first one

#19

Hi,
my relay is getting the same message as well.
The port checks open. It’s a ‘green check-mark’ on Adapools.org relay.
Processes TX is moving, as well as Mempool

Any recommendation?
thanks

#20

Maybe you could check your pool is this site–> https://pool.vet
If you have a bad configuration you will see the problem in the website.

Good luck!

#21

Thank you! this is a great tool