[tor-bugs] #5602 [Tor Bridge]: When managed proxy dies, we get "Tried to connect through proxy, but proxy address could not be found."

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Fri May 18 00:46:28 UTC 2012


#5602: When managed proxy dies, we get "Tried to connect through proxy, but proxy
address could not be found."
------------------------+---------------------------------------------------
 Reporter:  asn         |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  normal      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Bridge  |        Version:                    
 Keywords:  pt          |         Parent:  #5070             
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by asn):

 Please see branch `bug5602` in
 `https://git.gitorious.org/mytor/mytor.git`.

 It makes the log message more informative, but it also makes it similar to
 the one that `validate_pluggable_transports_config()` is giving out:
 {{{
 May 18 22:03:26.000 [warn] We were supposed to connect to bridge
 '222.222.222.222:1151' using pluggable transport 'obfs2', but it seems
 that we can't find a pluggable transport proxy supporting 'obfs2'. Please
 make sure that your configuration file is valid.
 May 18 22:03:26.000 [warn] We can't find a pluggable transport proxy that
 supports 'obfs2' for bridge '222.222.222.222:1151'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped working.
 }}}

 I'm wondering if `connection_or_connect()` is a good place to give out
 this warning, and if it can replace
 `validate_pluggable_transports_config()` (which is also the subject of
 silly bugs like #5589). Specifically, I'm thinking whether there are any
 cases where `connection_or_connect()` is not called, even though the
 user's configuration is wrong.

 If `connection_or_connect()` is a good place to warn about non-existent
 ClientTransportPlugin lines, maybe we can simply remove
 `validate_pluggable_transports_config()`.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5602#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list