Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2011-05-10T02:04:20Zhttps://gitlab.torproject.org/legacy/trac/-/issues/2636Orbot doesn't redirect connections to tor2011-05-10T02:04:20ZNathan FreitasOrbot doesn't redirect connections to tororbot 1.0.4
kernel: 2.6.29
ROM: BladeVillain1.1.0
rooted: yes
Orbot seems to start ok (according to the log) after requesting Superuser permission, but doesn't seem to generate any iptables entries.
("iptables -L" doesn't show any active...orbot 1.0.4
kernel: 2.6.29
ROM: BladeVillain1.1.0
rooted: yes
Orbot seems to start ok (according to the log) after requesting Superuser permission, but doesn't seem to generate any iptables entries.
("iptables -L" doesn't show any active chains). I can't see any mention of iptables in the log, but I don't know if there should be anything.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2635Orbot continuously tries to kill Privoxy using the wrong PID2011-05-10T02:01:20ZNathan FreitasOrbot continuously tries to kill Privoxy using the wrong PIDorbot 1.0.4
kernel: 2.6.29
rooted: yes
On my Android BladeVillain ROM (based on Android 2.2) orbot logs hundreds of attempts to kill Privoxy, but using the User-ID of the privoxy process instead of the PID. This consumes almost all the C...orbot 1.0.4
kernel: 2.6.29
rooted: yes
On my Android BladeVillain ROM (based on Android 2.2) orbot logs hundreds of attempts to kill Privoxy, but using the User-ID of the privoxy process instead of the PID. This consumes almost all the CPU, making it look like the orbot app has crashed and preventing orbot from starting up correctly or shutting down correctly.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2493orbot is not working on Android (Froyo 2.2)2011-02-06T12:14:14ZTracorbot is not working on Android (Froyo 2.2)Hi,
I have a Samsung Galaxy S with Android Froyo 2.2 and installed the Orbot 1.04 .
I have followed your instructions from here http://www.torproject.org/docs/android.html.en
but after Orbot is activated (green window) and check if Tor...Hi,
I have a Samsung Galaxy S with Android Froyo 2.2 and installed the Orbot 1.04 .
I have followed your instructions from here http://www.torproject.org/docs/android.html.en
but after Orbot is activated (green window) and check if Tor is working with your web check page, it says " sorry but you are not using Tor"
It looks like I'm not the only one that I have this issue, others from xda-developers have the same issue.
Is it possible to fix this ?
Kind Regards,
Dinu
**Trac**:
**Username**: dinocNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2424Android purges firewall rules after network disable/airplane mode.2020-06-13T00:01:39ZcypherpunksAndroid purges firewall rules after network disable/airplane mode.Setting my phone to disable data access and/or enable airplane mode seems to cause the transproxy iptables rules created by OrBot to get silently flushed. After re-enabling, all apps access everything without tor, until I go into the orb...Setting my phone to disable data access and/or enable airplane mode seems to cause the transproxy iptables rules created by OrBot to get silently flushed. After re-enabling, all apps access everything without tor, until I go into the orbot config screen to cause it to reapply them.
OrBot should listen for these network disable/loss/disconnect events if possible, and reinstate the iptables rules after this happens.
Someone should also test if switching from cell data to+from wifi also triggers this iptables reset. I have not tested that yet.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2423OrBot transproxy silently fails open2011-05-10T01:57:25ZcypherpunksOrBot transproxy silently fails openOn rooted phones that lack proper modules or iptables commands, OrBot seems to fail silently without informing the user that their selected apps are not torified. Minimally, it should verify the iptables rules it attempts to create are s...On rooted phones that lack proper modules or iptables commands, OrBot seems to fail silently without informing the user that their selected apps are not torified. Minimally, it should verify the iptables rules it attempts to create are still present after it creates them.
Ideally, it should also ping check.torproject.org, which provides a minimal, easy to parse XHTML response at https://check.torproject.org/?TorButton=trueNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2168Privoxy file missing from Orbot2012-04-06T01:04:03ZTracPrivoxy file missing from OrbotOn Google Android Devphone 1 with firmware 1.6 and using Orweb version 1 with Orbot Version 11 (Which is the first release in the Android market): When Privoxy encounters Error 500 I get the message
500 Internal Privoxy Error
Privoxy ...On Google Android Devphone 1 with firmware 1.6 and using Orweb version 1 with Orbot Version 11 (Which is the first release in the Android market): When Privoxy encounters Error 500 I get the message
500 Internal Privoxy Error
Privoxy encountered an error while processing your request:
Could not load template file forwarding - failed or one of its included components.
Please contact your proxy administrator.
If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It's typically the Privoxy Install directory, or /etc/privoxy/).
As a user rather than a technogeek, I have no idea how to fix this, but I think it should be in the Orbot installation package.
**Trac**:
**Username**: 4u2guessNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2069Orbot fails to start if configured as a relay2020-06-12T23:54:18ZTracOrbot fails to start if configured as a relayOrbot version: 1.0.4
Phone: Nexus One, 2.2.1 FRG83
Repo steps:
In Settings, select "Relaying", set "Relay Port" to 9001 set "Relay nickname". Press back. Press to start. Orbot turns yellow:
"set_options(): Bug: Acting on config option...Orbot version: 1.0.4
Phone: Nexus One, 2.2.1 FRG83
Repo steps:
In Settings, select "Relaying", set "Relay Port" to 9001 set "Relay nickname". Press back. Press to start. Orbot turns yellow:
"set_options(): Bug: Acting on config options left us in a broken state. Dying."
Selected lines from the log:
Orbit is starting....
got tor proc id: 18938
Tor process id=18938
Starting Tor...
Setting up control...
SUCCESS connected to control port
SUCCESS authenticated to control port
Setting up control...complete.
adding control port event handle
SUCCESS added control port event handle
You ContactInfo config option is not set .Please ...
Opening OR listener on 0.0.0.0:9001
You Tor server's identify key fingerprint is 'Skevek 73DD7A435...'
Unable to stat resolver configuration in '/etc/resolv.conf': No such file or directory
set_options(): Bug: Acting on config options left us in a broken state. Dying.
**Trac**:
**Username**: aglNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1969Full i18n in preference2018-12-12T07:56:11ZTracFull i18n in preferenceStrings in preference view is not i18ned.
I've updated
M res/values/strings.xml
M res/xml/preferences.xml
for full i18n in preference.
**Trac**:
**Username**: pen9u1nStrings in preference view is not i18ned.
I've updated
M res/values/strings.xml
M res/xml/preferences.xml
for full i18n in preference.
**Trac**:
**Username**: pen9u1nhttps://gitlab.torproject.org/legacy/trac/-/issues/1966Need to handle non-ISO-639-1 language codes2018-12-12T08:01:26ZNick MathewsonNeed to handle non-ISO-639-1 language codesI hear from Runa that orbot can't handle language codes of multiple characters. This is (obviously) a problem for the billion people who read zh_CN, but it's also a problem for all the people who speak languages that have codes in ISO 6...I hear from Runa that orbot can't handle language codes of multiple characters. This is (obviously) a problem for the billion people who read zh_CN, but it's also a problem for all the people who speak languages that have codes in ISO 639-2 but not ISO 639-1, like Hmong or Berber or Madurese.https://gitlab.torproject.org/legacy/trac/-/issues/1960Orbot website points to wrong svn location2011-02-15T23:08:58ZRoger DingledineOrbot website points to wrong svn locationhttps://guardianproject.info/apps/orbot/
is sending people to
https://svn.torproject.org/cgi-bin/viewvc.cgi/projects/android/trunk/Orbot/
which isn't going to work. You can't svn co from a cgi script.
The correct url is
https://svn.torp...https://guardianproject.info/apps/orbot/
is sending people to
https://svn.torproject.org/cgi-bin/viewvc.cgi/projects/android/trunk/Orbot/
which isn't going to work. You can't svn co from a cgi script.
The correct url is
https://svn.torproject.org/svn/projects/android/trunk/Orbot/Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1958Orbot stopped after I press Home/Back button2011-05-03T07:00:49ZTracOrbot stopped after I press Home/Back buttonDevice: Nexus one
Orbot 1.0.4-RC4-2010920
1. Start Orbot and connect to Tor successfully.
2. Press Home/Back button on device, return to home screen.
wait a moment, Orbot notfy that it has been stopped.
not always, but both in 1.0.3, ...Device: Nexus one
Orbot 1.0.4-RC4-2010920
1. Start Orbot and connect to Tor successfully.
2. Press Home/Back button on device, return to home screen.
wait a moment, Orbot notfy that it has been stopped.
not always, but both in 1.0.3, 1.0.4
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1957Do not start/stop tor when touch on log view2011-02-15T22:59:33ZTracDo not start/stop tor when touch on log viewDevice: Nexus one
Orbot 1.0.4-RC4-2010920
1. Switch to Log View
2. Touch on the screen
Unexpcepted: Tor stop/started after I touch screen.
I guess it's caused by the log view is not full fill the whole view, I can see it expanding whe...Device: Nexus one
Orbot 1.0.4-RC4-2010920
1. Switch to Log View
2. Touch on the screen
Unexpcepted: Tor stop/started after I touch screen.
I guess it's caused by the log view is not full fill the whole view, I can see it expanding when more log added into view.
BTW: the font size is too small in log view.
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1935Orbot UI hang in log view activity2011-05-03T07:11:12ZTracOrbot UI hang in log view activityDevice: Nexus one
Orbot: Orbot-1.0.3-Alpha-Experimental-100909c.apk
Steps to reproducer:
1. Start Orbot, and connect to Tor
2. After successfully connected to Tor, (May wait some time)
3. Press "Log" in the Menu
Expected: I can see th...Device: Nexus one
Orbot: Orbot-1.0.3-Alpha-Experimental-100909c.apk
Steps to reproducer:
1. Start Orbot, and connect to Tor
2. After successfully connected to Tor, (May wait some time)
3. Press "Log" in the Menu
Expected: I can see the log
Actually: I got a empty view
Then I press "return" button on my device, I got the main windows or Orbot.
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1934Updated Chinese Translation2011-11-04T17:21:56ZTracUpdated Chinese TranslationI've updated chinese translation for Orbot (svn trunk).
Patch will be attached.
**Trac**:
**Username**: pen9u1nI've updated chinese translation for Orbot (svn trunk).
Patch will be attached.
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1927orbot release 1.0.1 is missing changelog2011-02-17T17:33:30ZAndrew Lewmanorbot release 1.0.1 is missing changelogThe last changelog entry is for 1.0.The last changelog entry is for 1.0.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1875Automate Orbot builds2013-10-16T18:54:20ZErinn ClarkAutomate Orbot buildsOrbot builds are currently done by hand. The process is pretty simple, so it ought to be easy to automate. Nathan might have some ideas of things he wants added to this, so I'm adding him to the cc.Orbot builds are currently done by hand. The process is pretty simple, so it ought to be easy to automate. Nathan might have some ideas of things he wants added to this, so I'm adding him to the cc.Deliverable-Mar2011Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1814Need to setup an Android Market account2010-08-21T12:49:53ZNathan FreitasNeed to setup an Android Market accounthttp://market.android.com/publish
Requires a Google Account, and a $25 one-time payment.
This will be the official Tor Project account for releasing the Orbot application into the market.http://market.android.com/publish
Requires a Google Account, and a $25 one-time payment.
This will be the official Tor Project account for releasing the Orbot application into the market.Android (Orbot): 1.0Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1716Per-app traffic routing prefs not persisted2010-07-23T01:55:17ZTracPer-app traffic routing prefs not persistedversion: Orbot-0.0.8-Beta-071910a.apk
the new per app torification preferences screen within Settings doesn't persist settings.
**Trac**:
**Username**: djhallidayversion: Orbot-0.0.8-Beta-071910a.apk
the new per app torification preferences screen within Settings doesn't persist settings.
**Trac**:
**Username**: djhallidayNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1659Tor datum with proxy (MTN NIGERIA)2010-07-05T14:53:45ZTracTor datum with proxy (MTN NIGERIA)Jul 03 07:54:29.467 [Info] circuit_expire_building(): Abandoning circ 0 (state 2:connecting to server, purpose 5)
Jul 03 07:54:29.468 [Info] exit circ (length 1, exit 0000000000000000000000000000000000000000): $00000000000000000000000000...Jul 03 07:54:29.467 [Info] circuit_expire_building(): Abandoning circ 0 (state 2:connecting to server, purpose 5)
Jul 03 07:54:29.468 [Info] exit circ (length 1, exit 0000000000000000000000000000000000000000): $0000000000000000000000000000000000000000(closed)
Jul 03 07:54:29.468 [Info] connection_ap_fail_onehop(): Closing one-hop stream to '$0000000000000000000000000000000000000000/84.177.181.66' because the OR conn just failed.
Jul 03 07:54:29.468 [Info] _connection_free(): Freeing linked Socks connection [waiting for circuit] with 64 bytes on inbuf, 0 on outbuf.
Jul 03 07:54:29.468 [Info] _connection_free(): Freeing linked Socks connection [waiting for circuit] with 66 bytes on inbuf, 0 on outbuf.
Jul 03 07:54:29.471 [Info] _connection_free(): Freeing linked Socks connection [waiting for circuit] with 65 bytes on inbuf, 0 on outbuf.
Jul 03 07:54:29.516 [Info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.
Jul 03 07:54:29.516 [Info] connection_dir_request_failed(): Giving up on directory server at '78.55.109.29'; retrying
Jul 03 07:54:29.517 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
Jul 03 07:54:29.517 [Info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.
Jul 03 07:54:29.517 [Info] connection_dir_request_failed(): Giving up on directory server at '84.177.181.66'; retrying
Jul 03 07:54:29.517 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
Jul 03 07:54:29.517 [Info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.
Jul 03 07:54:29.517 [Info] connection_dir_request_failed(): Giving up on directory server at '86.170.194.39'; retrying
Jul 03 07:54:29.517 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
Jul 03 07:55:15.469 [Info] update_consensus_networkstatus_downloads(): Launching networkstatus consensus download.
Jul 03 07:55:15.469 [Info] router_pick_directory_server(): No reachable router entries for dirservers. Trying them all again.
Jul 03 07:55:15.469 [Info] directory_get_from_dirserver(): No router found for consensus network-status fetch; falling back to dirserver list.
Jul 03 07:55:15.470 [Info] connection_ap_make_link(): Making internal direct tunnel to [scrubbed]:8080 ...
Jul 03 07:55:15.470 [Info] onion_pick_cpath_exit(): Using requested exit node 'F2044413DAC2E02E3D6BCF4735A19BCA1DE97281'
Jul 03 07:55:15.471 [Info] circuit_handle_first_hop(): Next router is [scrubbed]: Not connected. Connecting.
Jul 03 07:55:15.471 [Info] connection_ap_make_link(): ... application connection created and linked.
Jul 03 07:55:15.471 [Info] directory_send_command(): Downloading consensus from 80.190.246.100:8080 using /tor/status-vote/current/consensus.z
Jul 03 07:55:15.471 [Info] connection_edge_process_inbuf(): data from edge while in 'waiting for circuit' state. Leaving it on buffer.
Jul 03 07:55:15.471 [Info] connection_edge_process_inbuf(): data from edge while in 'waiting for circuit' state. Leaving it on buffer.
Jul 03 07:55:16.470 [Info] run_connection_housekeeping(): Expiring non-open OR connection to fd 428 (84.177.181.66:9003).
Jul 03 07:55:16.471 [Info] run_connection_housekeeping(): Expiring non-open OR connection to fd 528 (86.170.194.39:443).
Jul 03 07:55:16.471 [Info] run_connection_housekeeping(): Expiring non-open OR connection to fd 536 (78.55.109.29:443).
Jul 03 07:55:30.474 [Info] circuit_expire_building(): Abandoning circ 0 (state 2:connecting to server, purpose 5)
Jul 03 07:55:30.475 [Info] exit circ (length 1, exit F2044413DAC2E02E3D6BCF4735A19BCA1DE97281): $F2044413DAC2E02E3D6BCF4735A19BCA1DE97281(closed)
Jul 03 07:55:30.475 [Info] connection_ap_fail_onehop(): Closing one-hop stream to '$F2044413DAC2E02E3D6BCF4735A19BCA1DE97281/80.190.246.100' because the OR conn just failed.
Jul 03 07:55:30.477 [Info] _connection_free(): Freeing linked Socks connection [waiting for circuit] with 80 bytes on inbuf, 0 on outbuf.
Jul 03 07:55:30.477 [Info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.
Jul 03 07:55:30.477 [Info] update_consensus_networkstatus_downloads(): Launching networkstatus consensus download.
Jul 03 07:55:30.477 [Info] router_pick_directory_server(): No reachable router entries for dirservers. Trying them all again.
Jul 03 07:55:30.477 [Info] directory_get_from_dirserver(): No router found for consensus network-status fetch; falling back to dirserver list.
Jul 03 07:55:30.477 [Info] connection_ap_make_link(): Making internal direct tunnel to [scrubbed]:80 ...
Jul 03 07:55:30.477 [Info] onion_pick_cpath_exit(): Using requested exit node '0AD3FA884D18F89EEA2D89C019379E0E7FD94417'
Jul 03 07:55:30.478 [Info] circuit_handle_first_hop(): Next router is [scrubbed]: Not connected. Connecting.
Jul 03 07:55:30.478 [Info] connection_ap_make_link(): ... application connection created and linked.
Jul 03 07:55:30.478 [Info] directory_send_command(): Downloading consensus from 208.83.223.34 using /tor/status-vote/current/consensus.z
Jul 03 07:55:30.479 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
Jul 03 07:55:30.479 [Info] connection_edge_process_inbuf(): data from edge while in 'waiting for circuit' state. Leaving it on buffer.
Jul 03 07:55:30.479 [Info] connection_edge_process_inbuf(): data from edge while in 'waiting for circuit' state. Leaving it on buffer.
Jul 03 07:55:45.484 [Info] circuit_expire_building(): Abandoning circ 0 (state 2:connecting to server, purpose 5)
Jul 03 07:55:45.486 [Info] exit circ (length 1, exit 0AD3FA884D18F89EEA2D89C019379E0E7FD94417): $0AD3FA884D18F89EEA2D89C019379E0E7FD94417(closed)
Jul 03 07:55:45.487 [Info] connection_ap_fail_onehop(): Closing one-hop stream to '$0AD3FA884D18F89EEA2D89C019379E0E7FD94417/208.83.223.34' because the OR conn just failed.
Jul 03 07:55:45.488 [Info] _connection_free(): Freeing linked Socks connection [waiting for circuit] with 74 bytes on inbuf, 0 on outbuf.
Jul 03 07:55:45.488 [Info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.
Jul 03 07:55:45.488 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
**Trac**:
**Username**: sejawhttps://gitlab.torproject.org/legacy/trac/-/issues/1658Tor datum with bridges (MTN NIGERIA)2010-07-05T14:53:16ZTracTor datum with bridges (MTN NIGERIA)Jul 03 07:48:45.164 [Info] connection_dir_request_failed(): Giving up on directory server at '84.177.181.66'; retrying
Jul 03 07:48:45.164 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on in...Jul 03 07:48:45.164 [Info] connection_dir_request_failed(): Giving up on directory server at '84.177.181.66'; retrying
Jul 03 07:48:45.164 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
Jul 03 07:48:45.164 [Info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.
Jul 03 07:48:45.164 [Info] connection_dir_request_failed(): Giving up on directory server at '86.170.194.39'; retrying
Jul 03 07:48:45.165 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
Jul 03 07:48:46.357 [Info] TLS error: <syscall error while handshaking> (errno=10053: Software caused connection abort [WSAECONNABORTED ])
Jul 03 07:48:46.359 [Info] connection_tls_continue_handshake(): tls error [misc error]. breaking connection.
Jul 03 07:48:46.360 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 1; recommendation warn)
Jul 03 07:48:48.498 [Info] TLS error: <syscall error while handshaking> (errno=10053: Software caused connection abort [WSAECONNABORTED ])
Jul 03 07:48:48.501 [Info] connection_tls_continue_handshake(): tls error [misc error]. breaking connection.
Jul 03 07:48:48.502 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)
Jul 03 07:48:52.158 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:48:52.778 [Info] TLS error: <syscall error while handshaking> (errno=10053: Software caused connection abort [WSAECONNABORTED ])
Jul 03 07:48:52.780 [Info] connection_tls_continue_handshake(): tls error [misc error]. breaking connection.
Jul 03 07:48:52.781 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 3; recommendation warn)
Jul 03 07:48:58.162 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:49:03.162 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:49:11.960 [Info] TLS error: <syscall error while handshaking> (errno=10053: Software caused connection abort [WSAECONNABORTED ])
Jul 03 07:49:11.963 [Info] connection_tls_continue_handshake(): tls error [misc error]. breaking connection.
Jul 03 07:49:11.963 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 4; recommendation warn)
Jul 03 07:49:11.966 [Info] TLS error: <syscall error while handshaking> (errno=10053: Software caused connection abort [WSAECONNABORTED ])
Jul 03 07:49:11.966 [Info] connection_tls_continue_handshake(): tls error [misc error]. breaking connection.
Jul 03 07:49:11.966 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 5; recommendation warn)
Jul 03 07:49:14.164 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:49:15.756 [Info] TLS error: <syscall error while handshaking> (errno=10053: Software caused connection abort [WSAECONNABORTED ])
Jul 03 07:49:15.759 [Info] connection_tls_continue_handshake(): tls error [misc error]. breaking connection.
Jul 03 07:49:15.759 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 6; recommendation warn)
Jul 03 07:49:25.167 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:49:36.170 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:49:47.169 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:49:58.170 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:49:59.170 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:50:09.171 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:50:20.171 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:50:31.172 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:50:42.173 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:50:53.174 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:51:00.175 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:51:04.176 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:51:15.176 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:51:26.177 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:51:37.179 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:51:48.180 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:51:59.182 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:52:01.182 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:52:10.183 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:52:21.183 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:52:32.184 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:52:43.184 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 03 07:52:54.185 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
**Trac**:
**Username**: sejaw