- OS: Void Linux (amd64, glibc)
- Tor Browser version: 13.0.11 (tarball, installed for my user in my home folder)
- Tor Browser Security Level: Standard
My phone is enabling internet access for my desktop computer through USB tethering. I can connect successfully on the Android Tor Browser app, but the Linux version of Tor Browser is failing to do that.
I’ve requested (by email) and tried as many bridges as I could (and no bridge at all), but nothing gets through. I suppose there’s something going wrong with the Linux browser when you’re on USB tethering.
2024-04-30 20:39:36.004 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:40:21.330 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:40:21.330 [NOTICE] Switching to guard context "default" (was using "bridges")
2024-04-30 20:40:31.757 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2024-04-30 20:40:31.757 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2024-04-30 20:40:32.007 [NOTICE] Bootstrapped 5% (conn): Connecting to a relay
2024-04-30 20:45:06.016 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
2024-04-30 20:45:06.016 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:45:06.017 [WARN] Managed proxy "N/A" process terminated with status code 0
2024-04-30 20:45:06.326 [NOTICE] Delaying directory fetches: DisableNetwork is set.
2024-04-30 20:45:07.197 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2024-04-30 20:45:07.197 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2024-04-30 20:45:43.159 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
2024-04-30 20:45:43.159 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:45:43.170 [WARN] Managed proxy "N/A" process terminated with status code 0
2024-04-30 20:45:43.367 [NOTICE] Delaying directory fetches: DisableNetwork is set.
2024-04-30 20:45:46.221 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:45:46.221 [NOTICE] Switching to guard context "bridges" (was using "default")
2024-04-30 20:45:46.286 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2024-04-30 20:45:46.286 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2024-04-30 20:48:02.500 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 178.79.165.254:2024 ID=<none> RSA_ID=B1194DF9313427D1C7A6B7133DD8303B6F4EB6D9 ("general SOCKS server failure")
2024-04-30 20:49:41.830 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 178.79.165.254:2024 ID=<none> RSA_ID=B1194DF9313427D1C7A6B7133DD8303B6F4EB6D9 ("general SOCKS server failure")
2024-04-30 20:52:08.261 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 178.79.165.254:2024 ID=<none> RSA_ID=B1194DF9313427D1C7A6B7133DD8303B6F4EB6D9 ("general SOCKS server failure")
2024-04-30 20:55:04.022 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
2024-04-30 20:55:04.022 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:55:04.029 [WARN] Managed proxy "N/A" process terminated with status code 0
2024-04-30 20:55:25.064 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:55:25.064 [NOTICE] Switching to guard context "default" (was using "bridges")
2024-04-30 20:55:29.919 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2024-04-30 20:55:29.919 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2024-04-30 20:56:01.100 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
2024-04-30 20:56:01.100 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:56:01.112 [WARN] Managed proxy "N/A" process terminated with status code 0
2024-04-30 20:56:01.798 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2024-04-30 20:56:01.798 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2024-04-30 20:56:36.438 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
2024-04-30 20:56:36.438 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:56:36.443 [WARN] Managed proxy "N/A" process terminated with status code 0
2024-04-30 20:56:37.067 [NOTICE] Delaying directory fetches: DisableNetwork is set.
2024-04-30 20:56:39.318 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2024-04-30 20:56:39.318 [NOTICE] Switching to guard context "bridges" (was using "default")
2024-04-30 20:56:39.366 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2024-04-30 20:56:39.366 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2024-04-30 20:56:44.165 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 178.79.165.254:2024 ID=<none> RSA_ID=B1194DF9313427D1C7A6B7133DD8303B6F4EB6D9 ("general SOCKS server failure")
2024-04-30 20:57:53.349 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 178.79.165.254:2024 ID=<none> RSA_ID=B1194DF9313427D1C7A6B7133DD8303B6F4EB6D9 ("general SOCKS server failure")
2024-04-30 21:00:36.165 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 178.79.165.254:2024 ID=<none> RSA_ID=B1194DF9313427D1C7A6B7133DD8303B6F4EB6D9 ("general SOCKS server failure")
Is it ok to publish these logs like this?