Tor is failing key retrieval?

Bitcoin
1

system/tor-logs:

2026-04-12T13:53:55-06:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2026-04-12T13:56:50-06:00 Received http status code 404 (“Not found”) from server 51.75.141.87:9000 while fetching “/tor/keys/fp/14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4”.
2026-04-12T13:59:13-06:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.

Went from hero to zero on BOTH servers. Anyone notice the same?

2

What application are you running that generates this log? Also, what operating system is that application running on?

3

Start9 OS - Pure Server and a Server One

They are the StartOS system/tor-logs

Also C-Lightning is showing the same kind of activity on Tor

4

What are the symptoms you see in conjuction with these logs? Is tor broken across the board (for example, can’t connect Sparrow wallet either)?

I think the lines Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query are normal. Or, to be more specific, I see that message repeated frequently in the logs on my server even when everything appears to be working working completely fine. If I am interpreting the message correctly, I think it is saying a service that it tried to connect with was temporarily unreachable-- which presumably happens frequently for Lightning peers which are not constantly up.

I’ve not seen the line Received http status code 404 (“Not found”) from server 51.75.141.87:9000 while fetching "/tor/keys/fp/14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4". Do you recognize that IP 51.75.141.87?

5

No I dont. The Pure log how a different IP

Received http status code 404 (“Not found”) from server 137.74.46.232:9001 while fetching “/tor/keys/fp/14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4”.

so the key is??? I notice they are the same…2 different servers.

Ill take a look at the peers

6

14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4 is an “v3ident” signature for a public Tor directory server. It is widely documented (for example, here are some slides that mention it in the context of “how tor works”)

7

This seems to have worked itself out. I figure it’s an external dependency again…especially with Core Lightning. Depressing