You should pay attention to close your Bitcoin Core GUI gracefully via File menu and Quit, wait until it actually all closes.


I don't run Bitcoin Core in Windows, I run my Core in Linux and not with the GUI. Unfortunately I can't tell you if the Windows version does or doesn't log the node's hidden service onion address. My Linux version does and I don't have a special debug log setting in my bitcoin.conf file, except for

Your setup only allows connections via tor (same as mine) and all your peers have indeed only onion addresses. So, that part is working properly. What did you install for Tor? Maybe you can find there some log entries indicating the onion address of your node?

I'm not sure if the reason could be that your Core can't properly communicate via the torcontrol. A log entry that torcontrol thread started is in your debul.log. Check if you have your Tor properly configured for Windows environment (can't help here much, but there are certainly thread on the topic Tor setup on Windows in this forum, too).


That's not what I wrote in my post:
You don't want to start another Core GUI as this can mess up your data directory. Not sure if your second GUI detected the presence of the first one and exited gracefully.

Anyway, running in Console window or command line should give same result and in yours "localaddresses" is empty for whatever reason.

In my /etc/tor/torrc I have the following settings:
All other stuff in my torrc is commented out and defaults apply accordingly.