Re: is this a bandwidth problem? my IP is a TOR exit, the client works and the server doesn't
On 7/23/07, Fabian Keil [EMAIL PROTECTED] wrote: I think you messed up your Privoxy configuration file while debugging this issue. The configuration file of the official Privoxy release should contain the same (valid) lines as: http://www.privoxy.org/faq/misc.html#TOR Fabian I was shocked, and a little embarrassed, to see that http://config.privoxy.org/show-status initially reported that I had errors because I had taken out the dots. I had not bothered to check it again after taking out the dots in the config. I must have gotten it working briefly by initially leaving the .s in, then I messed it up soon after that by taking them out. I put the dots back in to the config file and suddenly the http://config.privoxy.org/show-status page stopped showing the errors. Thanks to everyone for helping with this.
Re: is this a bandwidth problem? my IP is a TOR exit, the client works and the server doesn't
Rip Rock [EMAIL PROTECTED] wrote: So http://torcheck.xenobite.eu/ verifies that my TOR setup really is working, and it shows IPs and machine names that have nothing to do with my real IP and machine name. That much is great. However, when I try surfing to .onion URLs, I get 503 or 404 errors, along with the not-very-encouraging message that my request could not be fulfilled, because the domain name *... *could not be resolvedThis is often a temporary failure, so you might just try again. Remote Tor checks usually only confirm that your request is coming from a known Tor exit node, they don't confirm whether or not your using socks4 or socks4a. Are you sure you're using the latter? I'm using Vidalia/Privoxy/Firefox/Torbutton and I usually don't run a server. And it's great for going to normal webpages but telling them some other IP. I tried running a server to see if that would improve matters, but possibly my bandwidth is too low (I'm just on a home ADSL account). Jul 22 11:29:12:003 [Warning] Your server (...:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Jul 22 11:29:12:080 [Warning] Your server (...:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. I don't think this is related to your hidden service problems. I think the problem might be a lack of bandwidth. I don't believe I have a firewall problem. While it could also be a NAT problem, I wouldn't rule out a firewall issue. I imagine the worst-case scenario is that I'll be unable to resolve any .onion URLs until I buy a huge amount of bandwidth, set up a dedicated TOR server, and thus get enough traffic to be thoroughly connected. In other words, I fear that I might have to set up a miniature ISP in order to get any .onion connections. Is there any way to troubleshoot this, short of setting up a miniature ISP? Check your Tor logs. A failed request for a hidden service should result in something like: Jul 22 14:28:10.086 [notice] Tried for 120 seconds to get a connection to hy2644uxnz6zwt6c:80. Giving up. (waiting for circuit) or: Jul 22 15:07:26.829 [notice] Rend stream is 120 seconds late. Giving up on address 'hy2644uxnz6zwt6c.onion'. If there are no such messages you may not be using socks4a. With a socks4 (no a) connection between Privoxy and Tor you would still pass remote Tor checks, while your DNS requests could be done through a standard name server which wouldn't resolve onion domains and might explain the error messages. You could also try opening example.noconnect. If it leads to the same error message you're not using socks4a. Additionally you could build Privoxy 3.0.7 from CVS to get a less useless error message in case of forwarding failures. It wouldn't solve the problem, but might make diagnosing it easier. Fabian signature.asc Description: PGP signature
Re: is this a bandwidth problem? my IP is a TOR exit, the client works and the server doesn't
Rip Rock [EMAIL PROTECTED] wrote: On 7/22/07, Roger Dingledine [EMAIL PROTECTED] wrote: I think the problem might be a lack of bandwidth. No, the problem is that your ports aren't reachable. Okay, the problem is my ports. And because my logs had lacked the error messages described by Fabian, I guess I have socks4 where I ought to have socks4a, although I had thought that I had socks4a because my Privoxy config file has the line: # forward-socks4a / localhost:9050 . But of course the little dot prevents the forwarding from being used. There's nothing wrong with the dot. It indicates that there's no HTTP proxy after the socks proxy. So I tried taking out the . and LittleSnitch reported that Privoxy was now trying to access the net when I tried to find the hidden service. That's because invalid configuration directives are ignored (and valid forward-socks4a directives end either with a dot or with a HTTP proxy address). Have a look at: http://config.privoxy.org/show-status to see which of your configuration directives are ignored. I now see that there is an error: Jul 22 23:53:09:137 [Notice] Rend stream is 120 seconds late. Giving up on addre ss '[scrubbed].onion'. Now, the fact that I have that would lead me to think I have socks4a, At least you had it at Jul 22 23:53:09:137 ... but example.noconnect leads to an identical error page, so maybe I don't have socks4a, or maybe some other thing is going wrong with the 9050 mentioned in the file and the 8118 mentioned on the error page. I think you messed up your Privoxy configuration file while debugging this issue. I imagine the worst-case scenario is that I'll be unable to resolve any .onion URLs until Does http://6sxoyfb3h2nvok2d.onion/ load for you? You may have to try it several times. That address opens immediately with the message: [quote] The hidden wiki is gone. If you set up a new one and post the link to the or-talk list I'll link it from here. 06/07/07. Some Hans Zaagman suggested in a post to or-talkhttp://archives.seul.org/or/talk/Jun-2007/msg00215.htmlto use http://hy2644uxnz6zwt6c.onion/hidden/ as a replacement. 07/07/07. [/quote] So this hidden service appears to be working. The problem comes when I try to open http://hy2644uxnz6zwt6c.onion/hidden/ which always takes at least 30 seconds, usually much longer, and results in a 404 error. This hidden service doesn't work for me either, maybe it's just not running. So anyway I went into the config file of Privoxy and added the following below the forward socks4a: forward-socks4a / localhost:9050 forward-socks4a / localhost:8118 forward 192.168.*.*/ forward 10.*.*.*/ forward 127.*.*.*/ This was inspired by reading the faq/configuration file. However, neither the new hidden wiki, nor example.noconnect, show any new behaviors -- they both show the same error page, except for the URL. That's probably because none of these lines use correct syntax (and the second one is probably wrong anyway as it would overrule the first one and it's unlikely that Tor is listening at port 8118). The configuration file of the official Privoxy release should contain the same (valid) lines as: http://www.privoxy.org/faq/misc.html#TOR Fabian signature.asc Description: PGP signature
