That's actually a very interesting clue.

If LND is running Tor 0.4.9.11 while Bitcoin is still reporting Tor 0.4.7.8, then your Bitcoin app is almost certainly still attached to an old Tor container/image.

That shouldn't happen after upgrading to 1.7.4.

A few things I'd try:

1. Verify the image IDs:



docker ps -a
docker images | grep tor

See whether bitcoin_tor and lightning_tor are actually using different images.

2. Force a recreation of the Bitcoin app containers.



From the Umbrel App Store:

Stop Bitcoin Node.

Uninstall without deleting blockchain data (keep your data).

Install it again.


This recreates the containers while preserving the chainstate and blocks.

3. If you're comfortable with SSH, remove only the Bitcoin Tor container and let Docker recreate it:



docker rm -f bitcoin_tor_1
docker compose up -d

(or whatever compose command Umbrel uses for your version).

4. Also check whether the old container is mounting stale Tor data:



docker inspect bitcoin_tor_1

and compare it with the LND Tor container.

At this point I don't think this is a Bitcoin Core issue anymore—it looks like your Bitcoin app never picked up the new Tor image even though the OS update succeeded.

Could you also post the output of:

docker images
docker ps --format "table {{.Names}}\t{{.Image}}"

That should tell us immediately whether Bitcoin is still using an old cached image.