Tor consensus failures

Hi Guys,

I am getting to 45% and no further with the Bootstrapping… ( Getting killed on Tor failures over the last month or so… :frowning: )

50% of the time Logs show ( after the 45% bootstrap stage ):
Received http status code 404 (“Not found”) from server …

Trying to diagnose this online its saying that"
“Tor selects this server from its hardcoded fallback directory list. In your version (0.4.8.9, released ~2023), this list is outdated. By 2025, many fallbacks have changed configurations, retired, or stopped serving certain resources, leading to 404s”

The other 50% of the time the logs show:
“I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/8915, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)”

FYI I have done dozens of Tor resets and/or Wipes as well as full server cold restarts and no joy - this happened before and I was Tor was done for days on end,

Couple of Questions:

  1. How up to date is the Tor Directory list if the version of Tor is from ~2023 with the current latest StartOS?
  2. Is there a set of Steps that I should be running via SSH into the Env to update default timeouts; or view the logs that Tor’s logs suggest such as:
    2a. [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
    2b. [notice] Read configuration file “/etc/tor/torrc”.
    Aside: Bootstrapping timeout is set to 30seconds which doesn’t appear to be enough time to complete the Bootstrapping the majority of the time; is there a reason its so tight?

Yes, the fallback directory list is probably pretty stale. This hasn’t been a main focus for us since 99.99% of users are happily using Tor on their servers and the old reports we ever get of it not working are from users in countries where Tor is banned. As you probably know, our focus currently is on releasing StartOS v040 as soon as possible.

As for modifying Tor or anything really on the server to suit your needs, you’re free to do so, but you’d be relying on community support. Again, the only people around here who’ve ever needed to modify anything are a couple people who couldn’t connect at all.

In your case I’d probably just go to System → Experimental Features → Reset Tor + Wipe State a couple of times until you get a working circuit.

Yes, looking forward to the upgrade. Q1 2026?

Reluctant to alter defaults.

Yes I have done the Reset Tor + Wipe State many many times over the last week or two but it didn’t fix things until tonight :slight_smile:

The Logs really don’t show what is causing the many Tor failures ( significant downtime ) I am not touching Router Settings and there is no VPN on my wired node, bandwidth is not an issue Download 960Mbps; Upload 100Mbps. Government not gone fully Totalitarian yet so Tor isn’t blocked I believe.

Thanks

StartOS v040 is just about to enter Beta.