[tor-bugs] #5661 [- Select a component]: Tor Not Working Anymore

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Sun Apr 22 05:18:35 UTC 2012


#5661: Tor Not Working Anymore
---------------------------------------+------------------------------------
 Reporter:  ktx2skd                    |          Owner:                     
     Type:  defect                     |         Status:  new                
 Priority:  normal                     |      Milestone:                     
Component:  - Select a component       |        Version:  Tor: 0.2.2.17-alpha
 Keywords:  tor vidalia 403 forbidden  |         Parent:                     
   Points:                             |   Actualpoints:                     
---------------------------------------+------------------------------------
 Hello, I understand that I can get help here on running Tor/Vidalia,
 correct? If so then I would like assistance since Tor/Vidalia stopped
 working for me since a week.

 My connection passes through a proxy that at least supports HTTP (since it
 allows my web browsers to work), but in Tor Settings I used to put
 HTTP/HTTPS mode. It also requires user/password authentication which I
 also supplied.

 This set was working for me for a year or so, but last week it just
 stopped working. I tried different sets with the same proxy and a SOCKS4
 proxy I have, but nothing worked. I tried bridges, but it seems to not
 make a difference.

 I got basic understanding in programming & networking, but I do not rule
 the possibility that I've done something wrong. Here's two samples of a
 failing multi-hour log with the settings that "used" to work:

 ** NOTE#1: I don't know what is this SOCKS5 problem showing below, but it
 used to show up even at the times when Tor succeeded in connecting **
 ** NOTE#2: The 1st sample shows only the first 30 minutes of my attempt,
 the 2nd sample shows all the log BUT with excluding the repetition of the
 SOCKS5 issue **
 ** NOTE#3: The original log is attached **

 ========== FIRST SAMPLE STARTING ==========

 April 21 15:23:59.106 [Notice] Tor v0.2.2.17-alpha (git-dadd9608d2720368).
 This is experimental software. Do not rely on it for strong anonymity.
 (Running on Windows 7  [workstation])
 April 21 15:23:59.218 [Notice] Initialized libevent version 1.4.13-stable
 using method win32. Good.
 April 21 15:23:59.218 [Notice] Opening Socks listener on 127.0.0.1:9050
 April 21 15:23:59.218 [Notice] Opening Control listener on 127.0.0.1:9051
 April 21 15:23:59.434 [Notice] Circuit build measurement period of 60000ms
 is more than twice the maximum build time we have ever observed. Capping
 it to 6350ms.
 April 21 15:23:59.434 [Notice] Based on 1000 circuit times, it looks like
 we don't need to wait so long for circuits to finish. We will now assume a
 circuit is too slow to use after waiting 3 seconds.
 April 21 15:23:59.434 [Notice] Parsing GEOIP file.
 April 21 15:24:02.991 [Notice] Bootstrapped 5%: Connecting to directory
 server.
 April 21 15:24:03.021 [Notice] Bootstrapped 10%: Finishing handshake with
 directory server.
 April 21 15:24:03.029 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 15:24:03.029 [Warning] Proxy Client: unable to connect to
 193.23.244.244:443
 April 21 15:24:03.032 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 15:24:03.033 [Warning] Proxy Client: unable to connect to
 208.83.223.34:80
 April 21 15:24:05.001 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:05.001 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:08.000 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:08.001 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:10.991 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:10.991 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:13.994 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:13.994 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:16.996 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:16.996 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:19.995 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:19.996 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:22.978 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:22.979 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:25.988 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:25.995 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:28.988 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:28.990 [Warning] Fetching socks handshake failed. Closing.
 April 21 15:24:31.989 [Warning] socks5: command 3 not recognized.
 Rejecting.
 April 21 15:24:31.991 [Warning] Fetching socks handshake failed. Closing.

 ========== FIRST SAMPLE ENDING ==========

 ========== SECOND SAMPLE STARTING ==========

 April 21 15:23:59.106 [Notice] Tor v0.2.2.17-alpha (git-dadd9608d2720368).
 This is experimental software. Do not rely on it for strong anonymity.
 (Running on Windows 7  [workstation])
 April 21 15:23:59.218 [Notice] Initialized libevent version 1.4.13-stable
 using method win32. Good.
 April 21 15:23:59.218 [Notice] Opening Socks listener on 127.0.0.1:9050
 April 21 15:23:59.218 [Notice] Opening Control listener on 127.0.0.1:9051
 April 21 15:23:59.434 [Notice] Circuit build measurement period of 60000ms
 is more than twice the maximum build time we have ever observed. Capping
 it to 6350ms.
 April 21 15:23:59.434 [Notice] Based on 1000 circuit times, it looks like
 we don't need to wait so long for circuits to finish. We will now assume a
 circuit is too slow to use after waiting 3 seconds.
 April 21 15:23:59.434 [Notice] Parsing GEOIP file.
 April 21 15:24:02.991 [Notice] Bootstrapped 5%: Connecting to directory
 server.
 April 21 15:24:03.021 [Notice] Bootstrapped 10%: Finishing handshake with
 directory server.
 April 21 15:24:03.029 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 15:24:03.029 [Warning] Proxy Client: unable to connect to
 193.23.244.244:443
 April 21 15:24:03.032 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 15:24:03.033 [Warning] Proxy Client: unable to connect to
 208.83.223.34:80
 April 21 15:25:03.004 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 15:25:03.006 [Warning] Proxy Client: unable to connect to
 193.23.244.244:443fdsfsad
 April 21 15:30:08.223 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 15:30:08.225 [Warning] Proxy Client: unable to connect to
 208.83.223.34:80
 April 21 16:25:03.096 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 16:25:03.102 [Warning] Proxy Client: unable to connect to
 80.190.246.100:8080
 April 21 16:27:04.280 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 16:27:04.283 [Warning] Proxy Client: unable to connect to
 208.83.223.34:80
 April 21 16:32:09.761 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 16:32:09.766 [Warning] Proxy Client: unable to connect to
 80.190.246.100:8080
 April 21 16:42:19.862 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 16:42:19.871 [Warning] Proxy Client: unable to connect to
 80.190.246.100:8080
 April 21 17:25:03.371 [Notice] Bootstrapped 15%: Establishing an encrypted
 directory connection.
 April 21 17:27:03.329 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 17:27:03.334 [Warning] Proxy Client: unable to connect to
 193.23.244.244:443
 April 21 18:25:00.324 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 18:25:00.332 [Warning] Proxy Client: unable to connect to
 80.190.246.100:8080
 April 21 18:32:07.812 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 18:32:07.819 [Warning] Proxy Client: unable to connect to
 213.115.239.118:80
 April 21 18:42:17.236 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 18:42:17.245 [Warning] Proxy Client: unable to connect to
 193.23.244.244:443
 April 21 19:24:59.452 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 19:24:59.462 [Warning] Proxy Client: unable to connect to
 208.83.223.34:80
 April 21 19:32:06.887 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 19:32:06.897 [Warning] Proxy Client: unable to connect to
 208.83.223.34:80
 April 21 19:42:16.630 [Warning] The https proxy sent back an unexpected
 status code 403 ("Forbidden"). Closing.
 April 21 19:42:16.641 [Warning] Proxy Client: unable to connect to
 208.83.223.34:80

 ========== SECOND SAMPLE ENDING ==========

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


More information about the tor-bugs mailing list