[tor-bugs] #33219 [Circumvention/Censorship analysis]: Tor in China (Android) stops at 5%

[Tor Bug Tracker & Wiki]

#33219: Tor in China (Android) stops at 5%
-----------------------------------------------+---------------------------
 Reporter:  TiC                                |          Owner:  (none)
     Type:  defect                             |         Status:
                                               |  needs_information
 Priority:  Medium                             |      Milestone:
Component:  Circumvention/Censorship analysis  |        Version:
 Severity:  Normal                             |     Resolution:
 Keywords:  cn                                 |  Actual Points:
Parent ID:                                     |         Points:
 Reviewer:                                     |        Sponsor:
-----------------------------------------------+---------------------------
Changes (by dcf):

 * keywords:  Tor-Browser 9.0.4 => cn
 * status:  new => needs_information
 * component:  Circumvention => Circumvention/Censorship analysis
 * cc: dcf (added)


Old description:

> ==Description
> I am currently in China and since yesterday morning I cannot connect my
> tor browser on my phone unless I use another VPN service (which is very
> slow, so I would like to not use it). It is always stopping at 5%, I
> changed from mobile data to wifi, both does not work. I guess this is
> coincidence, but the problem occurred after I had tor opened while
> playing the Chinese PUBG (吃鸡). \\
>
> ==Protocols
>
> {{{- Einstellungen im Tor-Dienst werden aktualisiert /updating Tor
> applications
> - updating torrc custom configuration...
> - success.
> - checking binary version: 0.4.1.5-rc-openssl1.0.2p
> - Orbot startet …
> - Connecting to control port: 44003
> - SUCCESS connected to Tor control port.
> - SUCCESS - authenticated tor control port.
> - Took ownership of tor control port.
> - adding control port event handler
> - SUCCESS added control port event handler
> - NOTICE: Opening Socks listener on 127.0.0.1:9150
> - NOTICE: Opened Socks listener on 127.0.0.1:9150
> - NOTICE: Opening DNS listener on 127.0.0.1:5400
> - NOTICE: Opened DNS listener on 127.0.0.1:5400
> - NOTICE: Opening Transparent pf/netfilter listener on 127.0.0.1:9140
> - NOTICE: Opened Transparent pf/netfilter listener on 127.0.0.1:9140
> - NOTICE: Opening HTTP tunnel listener on 127.0.0.1:8218
> - NOTICE: Opened HTTP tunnel listener on 127.0.0.1:8218
> - Tor-Programm wird gestartet … abgeschlossen. /Tor program gets started
> - finished
> - NOTICE: Bootstrapped 5% (conn): Connecting to a relay
> - Netzwerkverbindung ist vorhanden. Tor wird aktiviert … /network
> connection available. Tor will be activated...
> - NOTICE: Your system clock just jumped 134 seconds forward; assuming
> established circuits no longer work.}}}

New description:

 == Description
 I am currently in China and since yesterday morning I cannot connect my
 tor browser on my phone unless I use another VPN service (which is very
 slow, so I would like to not use it). It is always stopping at 5%, I
 changed from mobile data to wifi, both does not work. I guess this is
 coincidence, but the problem occurred after I had tor opened while playing
 the Chinese PUBG (吃鸡). \\

 == Protocols

 {{{
 - Einstellungen im Tor-Dienst werden aktualisiert /updating Tor
 applications
 - updating torrc custom configuration...
 - success.
 - checking binary version: 0.4.1.5-rc-openssl1.0.2p
 - Orbot startet …
 - Connecting to control port: 44003
 - SUCCESS connected to Tor control port.
 - SUCCESS - authenticated tor control port.
 - Took ownership of tor control port.
 - adding control port event handler
 - SUCCESS added control port event handler
 - NOTICE: Opening Socks listener on 127.0.0.1:9150
 - NOTICE: Opened Socks listener on 127.0.0.1:9150
 - NOTICE: Opening DNS listener on 127.0.0.1:5400
 - NOTICE: Opened DNS listener on 127.0.0.1:5400
 - NOTICE: Opening Transparent pf/netfilter listener on 127.0.0.1:9140
 - NOTICE: Opened Transparent pf/netfilter listener on 127.0.0.1:9140
 - NOTICE: Opening HTTP tunnel listener on 127.0.0.1:8218
 - NOTICE: Opened HTTP tunnel listener on 127.0.0.1:8218
 - Tor-Programm wird gestartet … abgeschlossen. /Tor program gets started -
 finished
 - NOTICE: Bootstrapped 5% (conn): Connecting to a relay
 - Netzwerkverbindung ist vorhanden. Tor wird aktiviert … /network
 connection available. Tor will be activated...
 - NOTICE: Your system clock just jumped 134 seconds forward; assuming
 established circuits no longer work.
 }}}

--

Comment:

 Tor isn't expected to work in China without a [https://tb-
 manual.torproject.org/bridges/ bridge] because of GFW censorship. But if
 it was working for you recently and then stopped working, the cause might
 be something other than censorship. The main clue I see is `Your system
 clock just jumped 134 seconds forward`. The first thing you should do is
 make sure your system clock is set correctly. An incorrect system clock
 can cause Tor to fail early in the bootstrap process like that.
  * https://2019.www.torproject.org/docs/faq.html.en#DoesntWork

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