Me too. Beeline fix tor. How to modify my torrc to work
UseBridges 1
ClientTransportPlugin obfs4 exec /opt/sbin/obfs4proxy
Bridge obfs4 111.22.333.44:1234 FINGERPRINT cert=JS/66aasubHne96uyYmLklKSMkh/MYCamcbmu0c/aBhwbE
Bridge obfs4 111.22.333.44:1234 FINGERPRINT cert=zKC3y8ieK3lh28/nl/az6a2GeB1KSJUxKVTYG2X3K4G
Bridge obfs4 111.22.333.44:1234 FINGERPRINT cert=avfemQzJey18ZvPrTjpE86PbZR2gsf0nJsC/HabjtKo
This config is not work for me.
@unkn000wn what’s your operating system? Are you sure your obfs4proxy binary is installed in /opt/sbin?
Could you try emmapeel instructions?
I shared a bridge line in private with you (and @alex35).
Try do this to check the correct path for obfs4proxy:
which obfs4proxy
Tor Browser is good,
but I use tor package as a linux system-proxy.
I can’t find configuration torrc for work with obfs4proxy
BridgeRelay 1
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ORPort 443
ExtORPort auto
Log notice file /var/log/tor/log
What right format to ServerTransportListenAddr ?
LOG
Jan 03 11:14:53.000 [notice] Tor 0.3.5.16 opening new log file.
Jan 03 11:14:53.169 [notice] We compiled with OpenSSL 1010104f: OpenSSL 1.1.1d 10 Sep 2019 and we are running with OpenSSL 1010104f: 1.1.1d. These two versions should be binary compatible.
Jan 03 11:14:53.171 [notice] Tor 0.3.5.16 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
Jan 03 11:14:53.171 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jan 03 11:14:53.171 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jan 03 11:14:53.171 [notice] Read configuration file "/etc/tor/torrc".
Jan 03 11:14:53.177 [warn] Your ContactInfo config option is not set. Please strongly consider setting it, so we can contact you if your relay is misconfigured, end-of-life, or something else goes wrong. It is also possible that your relay might get rejected from the network due to a missing valid contact address.
Jan 03 11:14:53.177 [notice] Based on detected system memory, MaxMemInQueues is set to 2252 MB. You can override this by setting MaxMemInQueues by hand.
Jan 03 11:14:53.178 [notice] Opening Socks listener on 127.0.0.1:9050
Jan 03 11:14:53.178 [notice] Opened Socks listener on 127.0.0.1:9050
Jan 03 11:14:53.178 [notice] Opening OR listener on 0.0.0.0:443
Jan 03 11:14:53.178 [notice] Opened OR listener on 0.0.0.0:443
Jan 03 11:14:53.178 [notice] Opening Extended OR listener on 127.0.0.1:0
Jan 03 11:14:53.178 [notice] Extended OR listener listening on port 44839.
Jan 03 11:14:53.178 [notice] Opened Extended OR listener on 127.0.0.1:44839
Jan 03 11:14:53.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jan 03 11:14:53.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jan 03 11:14:53.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Jan 03 11:14:53.000 [notice] Your Tor server's identity key fingerprint is 'Unnamed ADA2FF4336675D6D746C490E09900D2B9C3CE0DF'
Jan 03 11:14:53.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'Unnamed D1E5DB0ABD22E858B72DBD80B8CA983523FE021B'
Jan 03 11:14:53.000 [notice] Bootstrapped 0%: Starting
Jan 03 11:14:55.000 [notice] Starting with guard context "default"
Jan 03 11:14:55.000 [notice] Signaled readiness to systemd
Jan 03 11:14:55.000 [warn] Server managed proxy encountered a method error. (obfs4 listen tcp 185.177.207.77:12346: bind: cannot assign requested address)
Jan 03 11:14:55.000 [warn] Managed proxy at '/usr/bin/obfs4proxy' failed the configuration protocol and will be destroyed.
Jan 03 11:14:55.000 [notice] Opening Socks listener on /run/tor/socks
Jan 03 11:14:55.000 [notice] Opened Socks listener on /run/tor/socks
Jan 03 11:14:55.000 [notice] Opening Control listener on /run/tor/control
Jan 03 11:14:55.000 [notice] Opened Control listener on /run/tor/control
Jan 03 11:14:55.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Jan 03 11:14:55.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jan 03 11:14:56.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jan 03 11:14:56.000 [notice] Guessed our IP address as 194.50.14.200 (source: 82.223.104.8).
Jan 03 11:14:56.000 [notice] Bootstrapped 100%: Done
Jan 03 11:14:56.000 [notice] Now checking whether ORPort 194.50.14.200:443 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jan 03 11:15:08.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Jan 03 11:15:08.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
There is an example on the Tor Project website at Community > Relay Operations > Technical Setup > Bridge > Debian / Ubuntu
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
# Replace "TODO2" with an obfs4 port of your choice.
# This port must be externally reachable and must be different from the one specified for ORPort.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ServerTransportListenAddr obfs4 0.0.0.0:TODO2
Just follow @emmapeel’s instructions: Tor blocked in Russia: how to circumvent censorship - #7 by emmapeel
Server managed proxy encountered a method error.
(obfs4 listen tcp 94.225.96.14:37075: bind: cannot assign requested address)
Managed proxy at ‘/usr/bin/obfs4proxy’ failed the configuration protocol and will be destroyed.
What can I do it ?
# torrc
RunAsDaemon 1
BridgeRelay 1
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ORPort 443
ExtORPort auto
Log notice file /var/log/tor/log
This works for tor_0.4.5.10-1 (LMDE 4, Debian 10) if the system is on Oracle VM.
The real PC needs IPv6… version 0.4.5 does not support IPv4.
I change tor version 0.3.5.16-1
result:
Jan 09 04:15:26.000 [notice] Tor 0.3.5.16 opening log file.
Jan 09 04:15:26.506 [notice] We compiled with OpenSSL 1010104f: OpenSSL 1.1.1d 10 Sep 2019 and we are running with OpenSSL 1010104f: 1.1.1d. These two versions should be binary compatible.
Jan 09 04:15:26.507 [notice] Tor 0.3.5.16 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
Jan 09 04:15:26.507 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jan 09 04:15:26.507 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jan 09 04:15:26.507 [notice] Read configuration file "/etc/tor/torrc".
Jan 09 04:15:26.513 [warn] Your ContactInfo config option is not set. Please strongly consider setting it, so we can contact you if your relay is misconfigured, end-of-life, or something else goes wrong. It is also possible that your relay might get rejected from the network due to a missing valid contact address.
Jan 09 04:15:26.513 [notice] Based on detected system memory, MaxMemInQueues is set to 4471 MB. You can override this by setting MaxMemInQueues by hand.
Jan 09 04:15:26.514 [notice] Opening OR listener on 0.0.0.0:443
Jan 09 04:15:26.514 [notice] Opened OR listener on 0.0.0.0:443
Jan 09 04:15:26.514 [notice] Opening Extended OR listener on 127.0.0.1:0
Jan 09 04:15:26.514 [notice] Extended OR listener listening on port 42859.
Jan 09 04:15:26.514 [notice] Opened Extended OR listener on 127.0.0.1:42859
Jan 09 04:15:26.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jan 09 04:15:26.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jan 09 04:15:27.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Jan 09 04:15:27.000 [notice] Your Tor server's identity key fingerprint is 'Unnamed ***** '
Jan 09 04:15:27.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'Unnamed *****'
Jan 09 04:15:27.000 [notice] Bootstrapped 0%: Starting
Jan 09 04:15:36.000 [notice] Starting with guard context "default"
Jan 09 04:15:36.000 [notice] Signaled readiness to systemd
Jan 09 04:15:36.000 [warn] Server managed proxy encountered a method error. (obfs4 listen tcp 11.22.33.44:37075: bind: cannot assign requested address)
Jan 09 04:15:36.000 [warn] Managed proxy at '/usr/bin/obfs4proxy' failed the configuration protocol and will be destroyed.
Jan 09 04:15:36.000 [notice] Opening Control listener on /run/tor/control
Jan 09 04:15:36.000 [notice] Opened Control listener on /run/tor/control
Jan 09 04:15:36.000 [notice] Bootstrapped 5%: Connecting to directory server
Jan 09 04:15:36.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Jan 09 04:15:36.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jan 09 04:15:36.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Jan 09 04:15:36.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jan 09 04:15:36.000 [notice] Guessed our IP address as 44.55.66.77 (source: 13.12.11.10).
Jan 09 04:15:36.000 [notice] Bootstrapped 100%: Done
Socks does not start,
string is missing : [notice] Opening Socks listener on 127.0.0.1:9050
The file “/usr/share/tor/tor-service-defaults-torrc” contains:
SocksPort unix:/run/tor/socks WorldWritable
SocksPort 9050
Proxy does not appear in the system.
What can I do 8?)
SOLVED
SocksPort 0 was be deleted from torrc
What are you trying to do? This torrc is for running a Tor bridge and not a client.
I am running tor on my client PC (lmde 4 - debian 10 buster).
I have linked the tor-package with privoxy, which I have made a system proxy.
All applications are running through tor