DEBUG torsocks: Entry added with IP address 127.42.42.0 used as cookie (in onion_entry_create() at onion.c:207)

DEBUG torsocks: Entry added to the onion pool at index 0 (in insert_onion_entry() at onion.c:79) DEBUG torsocks: Creating onion entry for name SPGmA7pu1CsgVBNW.onion (in onion_entry_create() at onion.c:174) DEBUG torsocks: Finding onion entry for name SPGmA7pu1CsgVBNW.onion (in onion_entry_find_by_name() at onion.c:229) DEBUG torsocks: Resolving SPGmA7pu1CsgVBNW.onion on the Tor network (in tsocks_tor_resolve() at torsocks.c:527) From the torsocks(8) manpage, I learned I could get some more debug messages like this: TORSOCKS_LOG_LEVEL=5 TORSOCKS_LOG_FILE_PATH=/tmp/torsocks.log torsocks elinksĪfter reproducing the error, I dug into the log file and found this interesting excerpt (.onion address changed): DEBUG torsocks: Requesting SPGmA7pu1CsgVBNW.onion hostname (in tsocks_getaddrinfo() at getaddrinfo.c:44) The first order of business was to turn up the volume. My normal approach of searching for help didn’t turn up anything useful for that warning or queries like ‘torsocks elinks’ or ‘torify elinks’ or ‘elinks dns’, so I put on my hard-hat and went to work. Getting past that, I ran into the real issue: regular web traffic was going through tor, but attempting to resolve *.onion addresses resulted in failure and a few of these warnings: WARNING torsocks: Connection to a local address are denied since it might be a TCP DNS query to a local DNS server. I suppose that because of the use of shared libraries, solutions like this are a first-come-first-serve deal. That solution, stupidly enough, was to exit the other instance of elinks that I had running. onion addresses and a what-is-my-ip page check). The first issue I ran into was that elinks didn’t seem to be going through the proxy defined by LD_PRELOAD / torsocks config (verified by the inability to resolve.

(A wiser man than I likely would’ve just used the alternate method suggested there-privoxy-but for the next one of me who comes along, here’s what I found.) I found what seemed to be the easiest way to this: torify elinks, but that turned into a journey down the rabbit-hole. I recently tried to use the ELinks console-based web browser with Tor.

Elinks where does elinks.conf go