Ok

[xmrhopium]

Ok

[BlackHatCoiner]

Bitcoin Core thinks the Tor SOCKS proxy is at 127.0.0.1:9050. Check if Tor is actually listening on that port:

Code:

Test-NetConnection 127.0.0.1 -Port 9050

If it does not return true, then you might be listening on another port (e.g., 9150). Test the same command under 9150. If that does not work, the debug.log might be helpful.

[nc50lc]

Hi, I recently updated to Bitcoin Core v29.1 on my new windows 11, but I’m now having a problem setting it up with Tor.

The problem is that my node isn’t connected to any Tor peers even though I set onlynet=onion, correctly?

Please clarify; was your previous setup isn't configured with Tor onion service?
If so, you should tell the related config that you've added to your bitcoin.conf file.

And, is Tor service already setup and running in your Windows 11 PC? (you can check if it's running in your services named "Tor Win32 Service")
Because with the correct proxy and Tor-related settings in Bitcoin Core, it will already show as "limited": false, "reachable": true, even if it can't find a running Tor service.
It'll just result with zero peers with onlynet=onion if Tor isn't available.

[nc50lc]

Yes, actually my previous setup was not properly configured with the TOS which I had set the Tor proxy to port 9050 but it wasn't connecting (that was the only problem), then switching to 9150 right after @BlackHatCoiner's suggestions, I updated the bitcoin.conf, it's now working perfectly.

Okay, so you're using "Tor Browser Bundle" instead of a stand-alone background process "Tor service" since their default SOCKS Port are different.
No wonder that the previous proxy settings didn't work.

Since you didn't mentioned that, others who have the same issue and found this thread should take note of it.