Adding relays but denied toplogy?

Staking & Delegation Operate a Stake Pool
1

Hi all;

Recently I added a few relays. The new relays are running topology updater, every hour on the hour. I’m getting good responses back, e.g. ‘glad you are staying with us’. However, when I look at the toplogy, there is nothing in it except:

{ "resultcode": "402", "datetime":"2021-02-19 03:22:30", "clientIp": "165.22.209.166", "iptype": 4, "msg": "IP is not (yet) allowed to fetch this list", "Producers": [ { "addr": "174.138.40.202", "port": 6000, "valency": 2 }

This is after approximately 24 hours.

The thing is, these nodes do have in/out peers. One has 9 in and 5 out. The other has 7 in and 0 out. All of my relays show up as in peers for my producer. Yet neither node appears in the topology.

What to make of this? Is this a cause for concern? Any suggestions?

2

hello,

did you checked in your Producer fw if you allow incoming connections from your new relay?
also check the topology file from your Producer, did you added the new Relay?

Cheers,

3

I have, yes. They are in there.

4

Did you find any solution? Same problem here.

5

topology.json is nothing to do with topology updater, it gets data from ledger, basically when you send pool registration certificate with relays, then your relays will end up there.

Here is great answer about same problem by @rdlrt