I think I've figured out underlying problem that caused me to get confused about whether tor was able to access the sockets.
Dec 21 13:50:16.000 [debug] rend_client_refetch_v2_renddesc(): Fetching v2 rendezvous descriptor for service [scrubbed] Dec 21 13:50:16.000 [info] pick_hsdir(): Could not pick one of the responsible hidden service directories, because we requested them all recently without success. Dec 21 13:50:16.000 [info] pick_hsdir(): Could not pick one of the responsible hidden service directories, because we requested them all recently without success. Dec 21 13:50:16.000 [info] fetch_v2_desc_by_addr(): Could not pick one of the responsible hidden service directories to fetch descriptors, because we already tried them all unsuccessfully. https://trac.torproject.org/projects/tor/ticket/16501 https://trac.torproject.org/projects/tor/ticket/15937 While testing my peer-to-peer use of tor hidden services, I was running multiple hidden services on one development machine. Each peer would try to contact the other's hidden service. As seen in the bug reports above, multiple SOCKS connections to a hidden service could cause some of the requests to fail. Those bugs reports seem to have been dealt with, but I am still experiencing what seems to be a similar problem. I've filed a new bug report on tor about that: https://trac.torproject.org/projects/tor/ticket/21056 -- see shy jo
signature.asc
Description: PGP signature
