Wanted to contact directory mirror XXX ... but but it's in our ExcludedNodes list and StrictNodes is set.
When I try to use tor hidden service, most often than not I get the following message:
"[warn] {DIR} Wanted to contact directory mirror XXX at xx.xx.xx.xx for hidden-service v2 descriptor fetch, but it's in our ExcludedNodes list and StrictNodes is set. Skipping. This choice might make your Tor not work."
There is so much wrong in this, I don't know where to start!
- Provided I have both EntryNodes, ExcludedNodes and StrictNodes all set, why is tor attempting to connect to a directory mirror it knows is in the ExcludedNodes list and then starts moaning?
This is like banging your head against the wall and then start complaining that it hurts!
The appropriate course of action should have been for tor to try and connect to a directory mirror which is NOT in my ExcludedNodes list.
- This whole issue stems from the fact that tor seems to ignore any of my [Alternate]DirAuthority settings as well and does what he wants - please refer to #10461 (moved) for details where I provided a detailed bug report, but nobody from the tor devs seems to care.
I also posted about this problem on the tor-talk ML but had nothing but a wall of silence there as well.
As it stands, I can't effectively use ANY tor hidden services as tor tries (and often fails) to get its v2 descriptors and everything goes pair shaped.
Trac:
Username: mr-4