jceaovh Pandora18 tornodeca
I was browsing a website that I hang out on all the time, and it came up with a Privoxy forwarding failure error. I tried another website and got the same error. I restarted Privoxy; didn't fix it. I brought up Vidalia and looked at the circuits. The one listed above was first; when I attempted to view the website, it added a line with the name of the website, labeled Closed, which quickly disappeared. I closed the circuit and refreshed the website and it came up.
cmeclax-sazri cmeclax-sazri@ixazon.dynip.com wrote:
I was browsing a website that I hang out on all the time, and it came up with a Privoxy forwarding failure error.
Posting the error message with the problem description would have helped.
I tried another website and gotthe same error. I restarted Privoxy; didn't fix it.
I'd be surprised if it did. Forwarding failures are unlikely to be solved (or even worked around) by restarting the HTTP proxy.
Restarting Tor is more likely to work around it, but of course it's not a real solution either.
I brought up Vidaliaand looked at the circuits. The one listed above was first; when I attempted to view the website, it added a line with the name of the website, labeled Closed, which quickly disappeared. I closed the circuit and refreshed the website and it came up.
With the information provided so far, I see no reason to blame the circuit or the exit.
Fabian
On Saturday 23 July 2011 14:14:47 Fabian Keil wrote:
With the information provided so far, I see no reason to blame the circuit or the exit.
I've seen it happen again with the same exit. There are two relays called "tornodeca"; the one in question is in the Netherlands. but the hostname is in an Indian domain. It has ports 80 and 443 open but apparently something's blocking port 80. I'll get in touch with the operator.
On Sunday 24 July 2011 12:39:58 cmeclax-sazri wrote:
On Saturday 23 July 2011 14:14:47 Fabian Keil wrote:
With the information provided so far, I see no reason to blame the circuit or the exit.
I've seen it happen again with the same exit. There are two relays called "tornodeca"; the one in question is in the Netherlands. but the hostname is in an Indian domain. It has ports 80 and 443 open but apparently something's blocking port 80. I'll get in touch with the operator.
http://torstatus.blutmagie.de/router_detail.php?FP=c20517b5cd15f21129f719ecc...
Could some other people try accessing sites through tornodeca and see if anyone other than me is having the problem?
The operator of tornodeca is unreachable. The bounce follows. Is this enough to call it a bad exit? --- This message was created automatically by the mail system (ecelerity).
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
my@mail.info (after RCPT TO): 550-The user my@mail.info does not exist
on our system. 550 Email postmaster@afilias.info if you have any questions.
cmeclax-sazri cmeclax-sazri@ixazon.dynip.com wrote:
On Sunday 24 July 2011 12:39:58 cmeclax-sazri wrote:
On Saturday 23 July 2011 14:14:47 Fabian Keil wrote:
With the information provided so far, I see no reason to blame the circuit or the exit.
I've seen it happen again with the same exit. There are two relays called "tornodeca"; the one in question is in the Netherlands. but the hostname is in an Indian domain. It has ports 80 and 443 open but apparently something's blocking port 80. I'll get in touch with the operator.
http://torstatus.blutmagie.de/router_detail.php?FP=c20517b5cd15f21129f719ecc...
Could some other people try accessing sites through tornodeca and see if anyone other than me is having the problem?
I can reproduce it. Trying to access www.example.org.c20517b5cd15f21129f719eccc54fbca05ae7ee5.exit:
Jul 24 23:08:35.065 [info] circuit_finish_handshake(): Finished building circuit hop: Jul 24 23:08:35.066 [info] exit circ (length 4, last hop tornodeca): [...](open) [...](open) [...](open) $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open) Jul 24 23:08:35.066 [info] circuit_send_next_onion_skin(): circuit built! Jul 24 23:08:35.066 [info] exit circ (length 4): [...](open) [...](open) [...](open) $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open) Jul 24 23:08:35.067 [info] connection_ap_handshake_send_begin(): Sending relay cell 0 to begin stream 4694. Jul 24 23:08:35.067 [info] connection_ap_handshake_send_begin(): Address/port sent, ap socket 4, n_circ_id 7997 Jul 24 23:08:35.716 [info] connection_ap_process_end_not_open(): Edge got end (connection refused) before we're connected. Marking for close. Jul 24 23:08:35.716 [info] exit circ (length 4): [...](open) [...](open) [...](open) $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open)
No problems accessing www.torproject.org.c20517b5cd15f21129f719eccc54fbca05ae7ee5.exit:443
Fabian
On Sunday 24 July 2011 17:39:07 Fabian Keil wrote:
I can reproduce it. Trying to access www.example.org.c20517b5cd15f21129f719eccc54fbca05ae7ee5.exit:
Jul 24 23:08:35.065 [info] circuit_finish_handshake(): Finished building circuit hop: Jul 24 23:08:35.066 [info] exit circ (length 4, last hop tornodeca): [...](open) [...](open) [...](open) $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open) Jul 24 23:08:35.066 [info] circuit_send_next_onion_skin(): circuit built! Jul 24 23:08:35.066 [info] exit circ (length 4): [...](open) [...](open) [...](open) $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open) Jul 24 23:08:35.067 [info] connection_ap_handshake_send_begin(): Sending relay cell 0 to begin stream 4694. Jul 24 23:08:35.067 [info] connection_ap_handshake_send_begin(): Address/port sent, ap socket 4, n_circ_id 7997 Jul 24 23:08:35.716 [info] connection_ap_process_end_not_open(): Edge got end (connection refused) before we're connected. Marking for close. Jul 24 23:08:35.716 [info] exit circ (length 4): [...](open) [...](open) [...](open) $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open)
No problems accessing www.torproject.org.c20517b5cd15f21129f719eccc54fbca05ae7ee5.exit:443
Okay, so it's not just me. I think that the other tornodeca should be flagged as BadExit too, even if it doesn't have the port blocked. Both have been up five days, both are named tornodeca, and both have the same invalid email address of the operator.
tor-relays@lists.torproject.org
-
cmeclax-sazri -
Fabian Keil