Re: .onion sites fail to load with: (waiting for rendezvous desc)
On Sat, Feb 16, 2008 at 12:03:02PM -0800, [EMAIL PROTECTED] wrote: I'm seeing this message in terminal running Tor when trying to connect to any .onion sites: [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc), followed by a Privoxy 502 error. FWIW, it looks like Karsten maybe just fixed this issue with a patch that went into the Subversion repository as r13540. If anybody who's been seeing this problem is able to try running svn trunk, it would be great to see whether this fixes the problem. Thanks! Yrs, -- Nick
Re: .onion sites fail to load with: (waiting for rendezvous desc)
On Feb 17, 2008, at 6:03 PM, [EMAIL PROTECTED] wrote: On Sat, Feb 16, 2008 at 12:03:02PM -0800, [EMAIL PROTECTED] wrote: I'm seeing this message in terminal running Tor when trying to connect to any .onion sites: [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc), followed by a Privoxy 502 error. FWIW, it looks like Karsten maybe just fixed this issue with a patch that went into the Subversion repository as r13540. If anybody who's been seeing this problem is able to try running svn trunk, it would be great to see whether this fixes the problem. Thanks! Yrs, -- Nick Hi, I just compiled and testet the new version. Using this, I was able to contact core.onion, the v2 descriptor testpage and the example hidden service. On core.onion, I clicked a few random links. Most were not working, but in the logs, the error message is different - I get [Notice] Closing stream for '[scrubbed].onion': hidden service is unavailable (try again later). which I guess means that the service is down. Also, I got a few [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) and [Notice] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'. in my logs. I hope this can help you Best Sebastian PGP.sig Description: This is a digitally signed message part
.onion sites fail to load with: (waiting for rendezvous desc)
I'm seeing this message in terminal running Tor when trying to connect to any .onion sites: [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc), followed by a Privoxy 502 error. Where these pages once loaded for me, they now all fail after attempting to load with the reason given in Tor above. Others have verified the .onion sites I try to connect to as up and running, but I can almost never connect to them anymore. I'm running the latest Tor alpha. Every other use of Tor works fine, only this problem when trying .onion sites. Any clues on what may be wrong and how to fix plz? thx -- [EMAIL PROTECTED] -- http://www.fastmail.fm - Does exactly what it says on the tin
Re: .onion sites fail to load with: (waiting for rendezvous desc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, | [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. | Giving up. (waiting for rendezvous desc), followed by a Privoxy 502 | error. Some days ago there was a guy on #tor with a similar problem. You? :) After trying out some things which did not appear to have any direct effect, it suddenly worked again for him. I just tried to access two hidden services. Worked fine. But obviously, there is a bug that we should track down. Maybe you can help us with that? | Others have verified the .onion sites I try to connect to as up and | running, but I can almost never connect to them anymore. I'm running | the latest Tor alpha. Every other use of Tor works fine, only this | problem when trying .onion sites. What does almost never mean? How often does it work? What happens when you restart Tor and try again? What if you wait for some minutes after starting Tor before trying? With latest Tor alpha you mean 0.2.0.19-alpha? Did you try to compile and run current trunk? Unfortunately one bug fix for 0.2.0.19-alpha turned out to be erroneous and was reverted in current trunk. But I doubt that it's the one causing the problem you describe. What versions are the people running who say that it's working for them? Can you tell the .onion address in public or in private mail to me? Or another service that you can tell? If not, do you know by any chance who is running such a service and whether they are running version 0.2.0.10-alpha or higher? Can you reach the example hidden service http://duskgytldkxiuqc6.onion/ or my v2 test service http://uulvbbixcufpmmg4.onion/ ? Thanks for your help! - --Karsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHt0u+0M+WPffBEmURAlZiAKCyKH9YJcyy9PQx2j5n54Z1lvWhVACfcGaw K1GuMu9rxNeUpIACfMVYzLM= =XXuE -END PGP SIGNATURE-
Re: .onion sites fail to load with: (waiting for rendezvous desc)
On Sat, 16 Feb 2008 21:46:54 +0100, Karsten Loesing [EMAIL PROTECTED] said: Some days ago there was a guy on #tor with a similar problem. You? :) No. #tor on OFTC has a ban on tor users right now, why? This does not help bug reporters very well. Why not a moderation mode instead of ban? After trying out some things which did not appear to have any direct effect, it suddenly worked again for him. I've tried everything I can think of, nothing works. Should I revert to stable until this is fixed? I don't know if I can offer much help. I just tried to access two hidden services. Worked fine. But obviously, there is a bug that we should track down. Maybe you can help us with that? I can connect to http://duskgytldkxiuqc6.onion/ without a problem, but others including core.onion, hidden wiki, Freenode's hidden IRC server, and a few others don't work as they used to. I attempt only known verified as working .onion sites from others. Non-fuctional (down) .onion sites show a different message in terminal unrelated to this bug. What does almost never mean? How often does it work? One day I managed to connect to one when I reloaded the site the moment following the failure message (with 0.2.0.17-alpha (or) 18-alpha), but I have been unable to reproduce this with the current 19-alpha). What happens when you restart Tor and try again? What if you wait for some minutes after starting Tor before trying? All tries fail. With latest Tor alpha you mean 0.2.0.19-alpha? Yes Did you try to compile and run current trunk? Unfortunately one bug fix for 0.2.0.19-alpha turned out to be erroneous and was reverted in current trunk. But I doubt that it's the one causing the problem you describe. I download only from download page @ torproject.org, I don't apply patches myself or use svn. What versions are the people running who say that it's working for them? This information I have not verified from them. Can you tell the .onion address in public or in private mail to me? I mentioned a few of them above. I personally have little use for .onion sites as most of them don't have content interesting to me, but I test anyway because it is alpha. -- [EMAIL PROTECTED] -- http://www.fastmail.fm - A no graphics, no pop-ups email service
Re: .onion sites fail to load with: (waiting for rendezvous desc)
On Sat, Feb 16, 2008 at 02:02:23PM -0800, [EMAIL PROTECTED] wrote 2.3K bytes in 63 lines about: : No. #tor on OFTC has a ban on tor users right now, why? This does not : help bug reporters very well. Why not a moderation mode instead of ban? We were flooded with trolls. It was a temporary measure. -- Andrew
Re: .onion sites fail to load with: (waiting for rendezvous desc)
Hi, after reading this I went ahead and with the help of Phobos compiled an installed trunk. On Feb 16, 2008, at 11:02 PM, [EMAIL PROTECTED] wrote: On Sat, 16 Feb 2008 21:46:54 +0100, Karsten Loesing [EMAIL PROTECTED] said: Some days ago there was a guy on #tor with a similar problem. You? :) Nope, that was me :) I just tried to access two hidden services. Worked fine. But obviously, there is a bug that we should track down. Maybe you can help us with that? I'd like to help I can connect to http://duskgytldkxiuqc6.onion/ without a problem, but others including core.onion, hidden wiki, Freenode's hidden IRC server, and a few others don't work as they used to. I attempt only known verified as working .onion sites from others. Non-fuctional (down) .onion sites show a different message in terminal unrelated to this bug. I had a somewhat strange behaviour. I was able to connect to the example hidden service, but not the v2 test service. trying to access the v2 test service, I got the message [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) a bit later, I could access the v2 test page without a problem, but core.onion still throws the above error message. The strange thing is that a made-up onion address gives a different error message in the log: Trying to access http://duskgytldkxi2qc6.onion/ (almost the same as a above, but changed one letter) I get a [Notice] Closing stream for '[scrubbed].onion': hidden service is unavailable (try again later). in the logs :) What happens when you restart Tor and try again? What if you wait for some minutes after starting Tor before trying? All tries fail. Same here, it does not matter how long Tor has been running Did you try to compile and run current trunk? Unfortunately one bug fix for 0.2.0.19-alpha turned out to be erroneous and was reverted in current trunk. But I doubt that it's the one causing the problem you describe. unfortunately, this doesn't seem to be the problem :( Best Sebastian PGP.sig Description: This is a digitally signed message part
