⚡ highsignal™ 🌪 movefast asked 22 days ago
LN+ App — Tor Hidden Service Descriptor Upload Failing (0 Inbound .onion Connections)
Environment:
Umbrel node (home server)
App: Lightning Network+ (LN+)
Tor version in LN+ container: 0.4.7.8
Issue:
The LN+ app's dedicated tor_server-1 container has been running continuously for 6+ days but reports 0 v3 INTRODUCE2 cells at every 6-hour heartbeat. The app's .onion address is not reachable remotely.
Root Cause (from container logs):
Repeated circuit timeout failures specifically on hidden service descriptor upload circuits:
No circuits are opened. Relaxed timeout for circuit X
(a Hidden service: Uploading HS descriptor 4-hop circuit
in state doing handshakes with channel state open)
No circuits are opened. Relaxed timeout for circuit X(a Hidden service: Uploading HS descriptor 4-hop circuitin state doing handshakes with channel state open)
The .onion descriptor is never successfully published to the Tor directory.
What is NOT affected:
-System-level Tor (Bitcoin node, LND) is fully functional
-Channel forwards are working normally
-LN+ app is accessible locally on the LAN
-Additional observations:
Worth noting:
-LN+ API authentication not working with Thunderhub generation
Recurring HTTP 404 errors fetching authority key certificates from 109.70.100.246:9040 — same three relay fingerprints — persisting across 6 days
Tor 0.4.7.8 in the LN+ container is outdated (current stable: 0.4.8.x)
App restarted May 19 ~09:00 UTC — bootstrapped to 100% in 15 seconds — awaiting confirmation of descriptor upload success
Request:
Update Tor in the LN+ Docker container to current stable
Confirm torrc has correct HiddenServiceDir and port mapping
Advise on the recurring 404s against those three authority fingerprints
Umbrel node (home server)
App: Lightning Network+ (LN+)
Tor version in LN+ container: 0.4.7.8
Issue:
The LN+ app's dedicated tor_server-1 container has been running continuously for 6+ days but reports 0 v3 INTRODUCE2 cells at every 6-hour heartbeat. The app's .onion address is not reachable remotely.
Root Cause (from container logs):
Repeated circuit timeout failures specifically on hidden service descriptor upload circuits:
No circuits are opened. Relaxed timeout for circuit X
(a Hidden service: Uploading HS descriptor 4-hop circuit
in state doing handshakes with channel state open)
No circuits are opened. Relaxed timeout for circuit X(a Hidden service: Uploading HS descriptor 4-hop circuitin state doing handshakes with channel state open)
The .onion descriptor is never successfully published to the Tor directory.
What is NOT affected:
-System-level Tor (Bitcoin node, LND) is fully functional
-Channel forwards are working normally
-LN+ app is accessible locally on the LAN
-Additional observations:
Worth noting:
-LN+ API authentication not working with Thunderhub generation
Recurring HTTP 404 errors fetching authority key certificates from 109.70.100.246:9040 — same three relay fingerprints — persisting across 6 days
Tor 0.4.7.8 in the LN+ container is outdated (current stable: 0.4.8.x)
App restarted May 19 ~09:00 UTC — bootstrapped to 100% in 15 seconds — awaiting confirmation of descriptor upload success
Request:
Update Tor in the LN+ Docker container to current stable
Confirm torrc has correct HiddenServiceDir and port mapping
Advise on the recurring 404s against those three authority fingerprints
4 Comments
LN+ Admin wrote 21 days ago
Thank you for the report! I'll get on this and fix it.
⚡ highsignal™ 🌪 movefast wrote 19 days ago
Github issue report submitted with the Tor keys causing the 404 errors
https://github.com/getumbrel/umbrel/issues/2151
https://github.com/getumbrel/umbrel/issues/2151
⚡ highsignal™ 🌪 movefast wrote 12 days ago
LN+ Admin wrote 10 days ago
I temporarily removed LN+ App from the Umbrel Store until fixed. I need to do a lot of updates on it anyway. I plan to re-do it with a new approach to make it better because the web version is way ahead in many ways. I think the Umbrel version should be simpler in some ways, but support some essential things that are currently missing.
I completely removed the ranks, because the API I was relying on is retired. I will need to evaluate alternative ways to reproduce similar functionality.
I completely removed the ranks, because the API I was relying on is retired. I will need to evaluate alternative ways to reproduce similar functionality.
Please login to post comments.