I would guess that you have asymmetric NAT. Basically for incoming connection your IP is “xxx.132.94.135”(I put xxx to mask first octet), but for outgoing is something else, that why topology updater is confused.
Just run on your relays curl ifconfig.me and see what IP it shows, I’m pretty sure it is different from “xxx.132.94.135”
Did you configure your port with CNODE_PORT, in your topology?
port is set in env file, reflected in the gLiveView.sh correctly too
if you add me manually to your topology file, then it will connect okay so it indicates that the cnode is set up correctly
Is there any way to confirm with TopologyUpdater service if my correct port is being reflected upon notifying their service? Logs don’t reflect any port as far as I can see but it feels like I am not being added to the TopologyUpdater services correctly and thus no one is looking for me
Yea, I tried P2P a few months ago but I moved back but again I found I wasn’t getting many incoming either.
I just restarted the node I enabled P2P on and I currently only have my 3 nodes as incoming.
Will give it another go for a while and see if that goes up
This still the best config to be using on mainnet?
Apologies for reviving this thread, but did you ever find a solution for this? I’m having the same issue as the OP with my relay node’s incoming connections:
Relay has been running for weeks and transaction count is increasing
20+ outgoing connections, but only 1 incoming connection from a peer other than my BP
UFW port is open at the correct port (tcp allow in anywhere) and matches the port specified in startCardanoNode.sh and topologyUpdater.sh
Port forwarding properly set up in my router
topologyUpdater.sh log reports “glad you’re staying with us” every hour for weeks
Relay port is open at the relay’s public IP on yougetsignal
The fact that I’m getting 1 incoming connection from an outside peer is odd because it suggests my relay is indeed reachable. But only 1 peer has connected to me despite participating in the TopologyUpdater service for weeks.
I’ve tried all the recommendations in this thread, but none have increased my incoming connections. It seems like everything is set up correctly on my end, but only 1 outside peer is connecting to me. Is it possible that I’m not being added to the TopologyUpdater service correctly and thus no one is looking for me?
Thanks Mat. I’ll enabled P2P and now have 45 uni-dir connections and 9 bi-dir connections (0 duplex).
I haven’t yet read the documentation around what that means, but I’m assuming at least the bi-dir connections encompass the functionality of an incoming connection in the non-P2P topology. If so, then hopefully any blocks I produce can propagate out via the bi-dir connections.