Awesome thank you kindly.  Was reaching my tolerance limit on this issue.  Yes- my router is a higher end (enterprise) that get very granular with security options so i think that was the issue.  Or- my conf file didnt include my internal ip address (explicitly) as opposed to just the loopback.  Against my better judgement, i changed both (router and binding my internal ip in conf file).  Likely it was the explicit ip vs loopback.  Anyway- ill try the -cli to look for the the .onion address but somehow its working.  Is there a way that i can check external connectivity via .onion address vs ip?

Confirmed that tor: Got service ID XXXXXXXXXXX, advertising service XXXXXXXXXXX.onion:8333 is showing in debug.log file.  Address does not show on getnetworkinfo output.  onion_private_key is present in default data folder.  I may have discovered an (if not the) issue.  My router was blocking Tor traffic (security setting).  I set that to allow and now i have 17 incoming (IPv4) and showing up as "reachable" on test site.  Maybe that was the issue?  Should the getinfo output show my address?  Do i need to add my onion address to the .conf file? If yes- what is the format?  Thanks by the way the debug tip is useful, would not have found that otherwise.

No real reason for [onlynet=onion] other than trying to increase anonymity.  ill try removing it.  Unfortunately i could not get port 8333 open with this node (windows); np with the former Redhat node.  I can try again.  It forwarded properly on my router but wont show as open on the btc node url test. Its been up and sync'd for about 3 weeks now so i would assume i should have some incoming.
With regards to output of addresses- no- did not show xxxxxxx.onion address; is blank so i believe without that, the node is unreachable to incoming peers.

I'm aware of the issue between v2 and v3 of Tor but its been quite a while since that change.  I would assume I would get at least 1 Peer.  I was just looking to support the btc network but not looking so likely at this point based on the # of replies.

I have a bitcoin node (v23) running on windows 10 Pro; fully synced and a wallet on Spectre (working).  I have 10 outgoing nodes connected (Onion) but no incoming.
I have the Tor service installed, its running and some config settings in bitcoin.conf.
listenonion=1
onlynet=onion
proxy=127.0.0.1:9050
listenonion=1
onlynet=onion
proxyrandomize=1
server=1
listen=1
disablewallet=0
bind=127.0.0.1
blockfilterindex=1
[test]
bind=127.0.0.1
[regtest]
bind=127.0.0.1
[signet]
bind=127.0.0.1

I would like to get incoming connections going on tor but if i run [getnetworkinfo] i show no local addresses and no incoming peers.  Anyone help me with that?

I appreciate the response.  The OS RHEL is Redhat Enterprise Linux.  the Rpi or Debian/ Obuntu installs wont work directly without changing commands etc.  Im not that skilled at those OS to be able to do that so was hoping someone did and i could follow.  Otherwise im coming up short searching for something useable- unless of course im missing something.

I'm running currently Bitcoin Core v23 on RHEL 8 (has a few hours left before fully sync'd).

I would like to install Electrum Personal Server (or S or X?) on that same server (RHEL) then link to Sparrow Wallet (on windows 10 but same network) using Ledger Nano S (already set up). 

I cant seem to find install instructions for Electrum for RHEL.  All of the docs i found were for Ubuntu, Rpi, Debian, etc.  I'm hopeful that someone has done this here and can point me in the right direction.  Thanks!