If your Umbrel Bitcoin node still has no Tor peers after updating to umbrelOS 1.7.4, while clearnet and I2P work, the problem is most likely with the Tor service itself or its connection to Bitcoin Co...
If I check docker ps, it shows me there's Tor 0.4.9.11 now,
LND log confirms it's using 0.4.9.11
>> lightning_tor_1 | Jul 15 10:23:24.931 [notice] Tor 0.4.9.11 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.5.6, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Glibc 2.41 as libc.
but the bitcoin log says it's seeing (and using) Tor 0.4.7.8.
>> bitcoin_tor_1 | Jul 15 10:23:24.655 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.
WTF?
So, it seems LND is back and working as expected (still some more channels offline than usual, but that might be on them, not me),
but Bitcoin still isn't for some reason.
LND log confirms it's using 0.4.9.11
>> lightning_tor_1 | Jul 15 10:23:24.931 [notice] Tor 0.4.9.11 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.5.6, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Glibc 2.41 as libc.
but the bitcoin log says it's seeing (and using) Tor 0.4.7.8.
>> bitcoin_tor_1 | Jul 15 10:23:24.655 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.
WTF?
So, it seems LND is back and working as expected (still some more channels offline than usual, but that might be on them, not me),
but Bitcoin still isn't for some reason.
❤️1