[tor-talk] random onion non-reachability
desnacked at riseup.net
Fri Jan 5 12:57:58 UTC 2018
Ben Tasker <ben at bentasker.co.uk> writes:
> [ text/plain ]
> On Fri, Jan 5, 2018 at 8:36 AM, Andreas Krey <a.krey at gmx.de> wrote:
>> Hi everyone,
>> I keep noticing a phenomenon regarding onion sites reachability.
>> Every now and then some onion site becomes unreachable from
>> a given tor browser instance while continuing to be reachable
>> from others. After a few days it becomes reachable again from
>> that instance as well. Happens with different onion services
>> and different browser instances (it's not always the same
>> service or instance involved).
>> Any idea what causes this? Random outage of rendevous points?
>> (The onion sites I observe this with are raspberries,
>> partially behind a NAT, under my control.)
> I've noticed similar with a group of services I've been experimenting with.
> Each of those services is configured in Single-Hop mode
> I initially assumed it related to this -
> https://trac.torproject.org/projects/tor/ticket/21969 - but haven't really
> had much chance to dig into it much further as I've been busy with other
> It's happened fairly frequently, but Tor's loglines aren't always the same.
> Because I use a dedicated routing system to decide which address to send
> you too, in the meantime I've just adjusted the routing status checks to
> always force a new circuit (to increase the chances of detecting the
> In all cases, restarting Tor on the Hidden Service helps.
> The various loglines I've seen are:
> Tor: I learned some more directory information, but not enough
> to build a circuit: We're missing descriptors for some of our primary
> entry guard
Yes, that's precisely #21969 and can be very bad for the reachability of
onion services. There has been lots of work on improving the #21969
situation on 0.3.2, so I'd recommend you try the latest tor-0.3.2
version and see whether things improve.
More information about the tor-talk