It’s still one, I’ll wait and see if it increases. Now I can see some Bi-Dir as well, was at 0 before. Thanks @os11k and @extramileit for your help and advice
it is prometheus. Sorry I’m using non-default ports 
If you have a relay node, which is the only node in communication with the BP node, I think it makes sense that you only see 1 incoming connection for the BP node
In my case, I’m running just a BP node, so it’s also serving as a relay node. Therefore, it has many incoming peer connections.
Does this sound correct?
No, not really.
Relay should have a lot of incoming and outgoing connections. BP config should not be changed(as it was before p2p) and it should have separate outgoing and incoming connections per each relay.
Previously I had a relay node, but after knowing I could just do with one BP node currently running just the BP node in testnet, so it must be an outside peer
Ok, that’s interesting. I’m looking at my mainnet BP node, and I see it has 15 incoming connections and 2 outgoing ones. In its topology file, it only includes the 2 relay nodes, so I’m confused where the 15 connections come from.
I can’t help in this case I’m assuming that everybody has at least 1 relay and BP in this case my configs will work. Not sure about a case, when only BP is running. Not sure why you even need this. I run testnet pool, to make sure that my mainnet pool works fine. But if I have completely different setups, then I will have different issues on different environments and there no point for such setup or I don’t understand the point.
@extramileit are you using the topologyUpdater in your mainnet BP? If so those incoming connections could be from other peers connecting to you, since they might get your BP node in their topology file after running the topologyUpdater
No, only on relays. For your mainnet BP node, do you only see incoming/outgoing connections count equal to the number of your relays?
Fair point about non-matching setup.
Even if the setup is different, it’s still useful for testing new node software on the BP testnet instance. Also, it’s good for supporting the Cardano testnet ecosystem by providing an additional pool.
In my case, I’m also trying to spare resources.
You have more then enough resources to run BP & relay on your VPS. 
Just my 50 cents.
I ran 4 cardano-nodes in similar HW server for testnet.
@extramileit I’m only running one BP and no relays in testnet. That’s all the setup I have now. I also didn’t include any relays in my topology with the P2P enabled setting. Following is what I see now.
Sorry, I interjected a question about my mainnet configuration into this thread on testnet setup, which is probably confusing. :(.
For my pool running on mainnet, I have 1 BP with 2 relays. The BP only includes the 2 relays in the topology.json file. But, when I look at connections on the BP node for my mainnet pool, I am confused why I see 15 incoming connections. Outgoing connections shows 2. I thought it only could use the relays for receiving/sending data to the rest of the network, so that it was insulated from attack. The large number of incoming connections is confusing to me now. I double checked that I’m not running the topology updater cron job on the BP node.
I need to dig on this question.
Have you double-checked your pool certificates?
In the “Do we need topology updater?” discussion a few days ago, they said, that at least the IOHK nodes pull from all relays registered there.
So, your relays were 207.180.224.185:6000 and 75.119.157.227:6000 for a few months and last month you deactivated the latter one and replaced it by 38.105.209.35:6000? Or is one of those your BP and the incoming connections come from those registrations?
You can check this with following command:
netstat -n -a | grep BP-port-number
It will show all your open connections, to that port. Keep in mind that if for relays you use same port number, then it will show connections to BP and connections from BP to relay. If ports are different, you should have on your BP 2 incoming connection, one per each relay.
Thanks @HeptaSean and @os11k.
I replaced one of my relays with a new relay about a month ago.
Running the netstat command on the BP server instance, it shows there are 12 connections to the new relay server on a non-6000 port. But, there is only connection to non-6000 port for the other relay.
So, that’s rather curious. I’m actually meant to mint a block later today, so I’m not going to muck with anything, but maybe there is something off in my setup of the new relay.
@extramileit how would you know that your node is to mint a block today? This is something I still haven’t found an answer anywhere yet. Would appreciate if you can share some light on this. Is it by looking at the Block Production section in gLiveView ?
Thanks
If you’re familiar with coincashew, it gives some info on installing an executable for a CLI tool called cncli and some scripts that will query the leaderlog data.
18. Operational and Maintenance Tips - CoinCashew.
Here’s the github project
I’ve seen the word cncli but never looked at it, thanks for pointing me in that direction. I will check on that. This discussion thread has been really helpful. I’ve learned quite a lot just from the past few days. Thanks to everyone generous enough to share the knowledge
Ditto… very helpful. Appreciate the discussion. Thanks all!