Tor: 0.4.8.10-dev-20240401T153401Z-1~d13.trixie+1
tor mode: obfs4
error:
2024-04-02 06:24:38.024 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-02 06:24:38.052 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2024-04-02 06:24:38.052 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2024-04-02 06:24:40.014 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
2024-04-02 06:24:40.016 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
2024-04-02 06:24:43.080 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ID=<none> RSA_ID=EC9EB3CA101B068172ACC3BB06B691F6C2EF5AB2 ("general SOCKS server failure")
2024-04-02
4 04 09:37:13 localhost.localdomain Tor[135420]: Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out; TIMEOUT; >
4 04 09:37:13 localhost.localdomain Tor[135420]: 1477 connections have failed:
4 04 09:37:13 localhost.localdomain Tor[135420]: 1477 connections died in state connect()ing with SSL state (No SSL object)
4 04 09:39:11 localhost.localdomain Tor[135420]: Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out; TIMEOUT; >
4 04 09:39:11 localhost.localdomain Tor[135420]: 1478 connections have failed:
4 04 09:39:11 localhost.localdomain Tor[135420]: 1478 connections died in state connect()ing with SSL state (No SSL object)
4 04 09:46:50 localhost.localdomain Tor[135420]: Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out; TIMEOUT; >
4 04 09:46:50 localhost.localdomain Tor[135420]: 1479 connections have failed:
4 04 09:46:50 localhost.localdomain Tor[135420]: 1479 connections died in state connect()ing with SSL state (No SSL object)
If you’re connecting from mainland China, you should use webtunnel (https://bridges.torproject.org/options/ > select Webtunnel ) or a private obfs4 bridge from Tor frontdesk.
Bridges distributed by some BridgeDB’s distributors are enumerated and blocked by the GFW.
os:
Debian Gnu/Linux 13
kernel:
linux-image-6.7.12-amd64 6.7.12-1 amd64 Linux 6.7 for 64-bit PCs (signed)
cli tor:
0.4.9.0-alpha-dev-20240528T020417Z-1~d13.trixie+1
error:
09:29:53 [ERR] Bug: /usr/bin/tor(_start+0x21) [0x56312a5fdf71] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /lib/x86_64-linux-gnu/libc.so.6(libc_start_main+0x85) [0x7f95f5145d45] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /lib/x86_64-linux-gnu/libc.so.6(+0x27c8a) [0x7f95f5145c8a] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(main+0x1d) [0x56312a5fdf1d] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(tor_main+0x5d) [0x56312a5fe38d] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(tor_run_main+0x1e5) [0x56312a601ff5] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(do_main_loop+0xf5) [0x56312a6067b5] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(event_base_loop+0x49f) [0x7f95f5b9804f] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(+0x21822) [0x7f95f5b97822] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(notify_pending_waitpid_callbacks+0xf7) [0x56312a699fb7] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(process_notify_event_exit+0x4d) [0x56312a6985cd] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(+0xca48b) [0x56312a65f48b] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(+0xc88d2) [0x56312a65d8d2] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tortor_assertion_failed+0x14b) [0x56312a68c79bd] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: /usr/bin/tor(log_backtrace_impl+0x5b) [0x56312a68156b] (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] Bug: Tor 0.4.9.0-alpha-dev: Assertion mp->conf_state == PT_PROTO_COMPLETED failed in proxy_prepare_for_restart at …/src/feature/client/transports.c:519: . Stack trace: (on Tor
│ 0.4.9.0-alpha-dev )
│ 09:29:53 [ERR] tor_assertion_failed(): Bug: …/src/feature/client/transports.c:519: proxy_prepare_for_restart: Assertion mp->conf_state == PT_PROTO_COMPLETED failed; aborting. (on Tor 0.4.9.0-alpha-dev )
│ 09:29:53 [WARN] Managed proxy “/usr/bin/lyerbird” process terminated with status code 256
│ 09:29:53 [WARN] Managed proxy “N/A” process terminated with status code 256 [1 duplicate hidden]
─┘ 09:29:53 [WARN] 18 connections died in state connect()ing with SSL state (No SSL object)
that stack trace looks like the one from tor#40895. This happens if the pluggable transport crashes in some cases. While tor shouldn’t crash when a PT crash, the underlying issue is that the PT crashes.
Does your apparmor profile allows for executing /usr/bin/lyerbird? Last i checked the defaultprovile only allows /usr/bin/obfs4proxy.
Remove the webtunnel in the first line (ClientTransportPlugin meek_lite,....) as you have already set where the webtunnel client is in the next line, and obfs4proxy does not support webtunnel.
I won’t explain more (because I’m too lazy to type more lol), just copy/paste the fixed config to /etc/torrc and you should maybe be good
11 15:38:22 localhost Tor[102810]: Server managed proxy encountered a method error. (webtunnel unimplemented)
11 15:38:22 localhost Tor[102810]: Managed proxy ‘/usr/bin/lyrebird’ was spawned successfully, but it didn’t launch any pluggable transport listeners!
11 15:38:22 localhost Tor[102810]: Managed proxy ‘/usr/bin/lyrebird’ did not configure the specified outgoing proxy and will be terminated.
11 15:38:22 localhost Tor[102810]: Managed proxy ‘/usr/bin/obfs4proxy’ did not configure the specified outgoing proxy and will be terminated.
11 15:38:22 localhost Tor[102810]: Managed proxy “N/A” process terminated with status code 256
11 15:38:22 localhost Tor[102810]: Managed proxy “N/A” process terminated with status code 256
11 15:38:22 localhost Tor[102810]: Managed proxy “N/A” process terminated with status code 256
11 15:38:22 localhost Tor[102810]: Managed proxy “N/A” process terminated with status code 65280
11 15:38:22 localhost Tor[102810]: Managed proxy “N/A” process terminated with status code 0
How can TLS traffic pass through the firewall safely and effectively? Is this a problem? ? ? Otherwise it cannot be connected
6月 11 15:18:26 localhost Tor[100849]: Could not add transport webtunnel. Skipping.
6月 11 15:18:26 localhost Tor[100849]: You tried to add transport ‘snowflake’ at ‘127.0.0.1:17456’ but the same transport already>
6月 11 15:18:26 localhost Tor[100849]: Could not add transport snowflake. Skipping.
6月 11 15:18:26 localhost Tor[100849]: Server managed proxy encountered a method error. (webtunnel no such transport is supported)
6月 11 15:18:26 localhost Tor[100849]: Registered server transport ‘obfs4’ at ‘[::]:12998’
6月 11 15:18:27 localhost Tor[100849]: Opening Socks listener on /run/tor/socks
6月 11 15:18:27 localhost Tor[100849]: Opened Socks listener connection (ready) on /run/tor/socks
6月 11 15:18:27 localhost Tor[100849]: Opening Control listener on /run/tor/control
6月 11 15:18:27 localhost Tor[100849]: Opened Control listener connection (ready) on /run/tor/control
