"LND hidden service descriptor not publishing - No more HSDir available to query"

Start9 server, LND 0.20.1, StartOS 0.3.5-1

Tor bootstraps to 100% successfully but LND hidden service
descriptor never publishes to HSDir nodes.

Tried:

  • Reset Tor without wipe state
  • Reset Tor with wipe state
  • Full system restart
  • Turned off “Use Tor for all traffic” and “Stream Isolation” in LND config
  • Switched ethernet ports on TP-Link switch

Tor logs show “No more HSDir available to query” immediately
after bootstrap. Hidden service unreachable from Tor Browser
and curl via SOCKS5.

LND synced to chain and graph. Bitcoin Core satisfied.

There’s nothing you can do on StartOS to force various third parties in the TOR network to operate effectively, other than resetting Tor and hoping for a better circuit. Options are to wait or to reset.

Hmmm.. that’s not very hopeful Stu , hope a Start 9 tech can come up with a solution.

I’m not trying to be unhelpful… I can help with anything related with your server and with StartOS, not anything external or unrelated to your server. I have no personal control over the TOR network and can’t make it behave in any particular way.

Where do your logs say “LND hidden service descriptor not publishing“? That doesn’t sound right. Seems like that may be your language rather than someone from the logs.

Simple lines of “No more HSDir available to query” is all too common and normal, unfortunately.

Please reset Tor.

We have reset Tor multiple times (with and without wipe state) and the issue persists for over 24 hours. After each reset Tor bootstraps to 100% but the hidden service is never reachable — curl via SOCKS5 returns error 5, Tor Browser shows ‘Unable to connect’. The HSDir error appears within seconds of bootstrap every time. Is there anything specific we can check to confirm the hidden service descriptor is actually being uploaded?

After the latest reset, Tor bootstrapped to 100% but we’re now seeing: ‘Guard mycontribution is failing more circuits than usual. Tor network is overloaded. 144/206 success counts.’ Could this overloaded guard be preventing the hidden service descriptor from being published? Is there a way to force a new guard node selection?

Confirmed: curl via SOCKS5 can reach DuckDuckGo’s onion address successfully, but cannot reach my Start9 LND onion address. This confirms the hidden service descriptor is not being published to the Tor network. Tor bootstraps to 100% fine. What can I check to verify the descriptor is actually being uploaded?

Additional info: Start9 version 0.3.5-1, LND 0.20.1. Tor config in LND: ‘Use Tor for all traffic’ = OFF, ‘Stream Isolation’ = OFF. Previously had both ON which caused 33 simultaneous HSDir failures. After turning both OFF and doing a wipe state Tor reset, no more HSDir errors appear in logs, but hidden service still unreachable. DuckDuckGo onion reachable from same network confirming Tor works. Start9 heartbeat shows ‘onion services received INTRODUCE2 cells and attempted rendezvous circuits’ suggesting some activity but descriptor never found by clients.