Bitcoin node lost Tor peer connections

I've had my Bitcoin Core full node running on an Ubuntu server for quite a while. I use Tor to connect Bitcoind so my ISP can’t see my Bitcoin activity. But since mid-December, I haven’t been able to find any peers, and I'm not downloading new blocks anymore. Here’s a look at my bitcoin.conf: proxy=127.0.0.1:9050 listen=1 bind=127.0.0.1 When I commented out those lines, I started to find peers again and was able to download new blocks, but then I wasn’t using Tor any longer. Tor looks like it's working okay on my server. I can still access a hidden service I set up there, and when I run this command: "curl socks5 localhost:9050 socks5-hostname localhost:9050 -s https://check.torproject.org/ | cat | grep -m 1 Congratulations | xargs", it gives me 'Congratulations. This browser is configured to use Tor.' I'd like to get my node working again with Tor. Any suggestions would be great. Oh, and I'm on Bitcoin Core 0.21.1.

Have you updated Tor recently? You might get additional hints about the issue by adding --debug=tor arg when starting Bitcoin Core. Then check your latest debug.log entries for lines containing "[tor]" tag. For now, you can review section 2 or 3 of Bitcoin Core v0.21.1's Tor documentation: github.com/bitcoin/bitcoin/blob/v0.21.1/doc/tor.md

0.21.1 is pretty old at this point, and there have been changes to how Tor support works in newer versions. Might be worth upgrading if you can. Also check if your Tor service itself got updated recently. Sometimes Tor updates break the SOCKS interface or change default behaviors. Look at your Tor logs around mid-December when it stopped working. Here's one thing to try: add   onlynet=onion   to your config so it's explicitly only looking for onion peers. And make sure you have   listenonion=1   set. The debug.log with   -debug=tor   like nc50lc suggested should tell you what's actually failing.