Can somebody please please help us out?
Identical config from one client to another fails, here is the
client side config:
# cat /etc/tor/torrc |egrep -v '^#|^$'
SocksPolicy accept 127.0.0.1/32
SocksPolicy accept 192.168.122.0/24
Log notice file /var/log/tor/notices.log
DataDirectory /var/lib/tor
UseBridges 1
Bridge obfs4 serverIP:Port Server signature cert=theServerCert
iat-mode=0
ClientTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy
Here is the obfs4proxy.log:
2018/06/03 20:20:57 [ERROR]: obfs4([scrubbed]:8080)
- outgoing connection failed: read: i/o timeout
2018/06/03 20:22:28 [ERROR]: obfs4([scrubbed]:8080) - outgoing
connection failed: read: i/o timeout
2018/06/03 20:23:48 [ERROR]: obfs4([scrubbed]:8080) - outgoing
connection failed: EOF
Here is the tor log at the client:
Jun 03 21:09:50.000 [notice] Bootstrapped 10%:
Finishing handshake with directory server
Jun 03 21:10:50.000 [warn] Proxy Client: unable to
connect to server ip:server port ("general SOCKS server failure")
In short, if the first client works fine and handshakes in
restarts;how come the second machine fails ????
On 05/31/2018 12:06 PM, Hamid Safe
wrote:
An update to the below is that I got 2x tor relay address from:
https://bridges.torproject.org/bridges?transport=obfs4
and configuring them also stock at the same step... :(
One thing though: living in Iran...could that be related?I thought
obfuscation+relay agents that are changing or private ones are
immune to the DPI censorship... and fact is my old laptop and
private relay remains active and resilient...
any thoughts?
May 31 11:55:51.487 [notice] Tor 0.3.3.6
(git-7dd0813e783ae16e) running on Linux with Libevent
2.1.8-stable, OpenSSL 1.1.0h, Zlib 1.2.11, Liblzma 5.2.4, and
Libzstd N/A.
May 31 11:55:51.487 [notice] Tor can't help you if you use it
wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 31 11:55:51.487 [notice] Read configuration file
"/etc/tor/torrc".
May 31 11:55:51.489 [notice] Scheduler type KIST has been
enabled.
May 31 11:55:51.489 [notice] Opening Socks listener on
127.0.0.1:9050
May 31 11:55:51.000 [notice] Parsing GEOIP IPv4 file
/usr/share/tor/geoip.
May 31 11:55:51.000 [notice] Parsing GEOIP IPv6 file
/usr/share/tor/geoip6.
May 31 11:55:51.000 [notice] Bootstrapped 0%: Starting
May 31 11:55:51.000 [notice] Starting with guard context
"bridges"
May 31 11:55:51.000 [notice] Delaying directory fetches: No
running bridges
May 31 11:55:53.000 [notice] Bootstrapped 5%: Connecting to
directory server
May 31 11:55:53.000 [notice] Bootstrapped 10%: Finishing
handshake with directory server
May 31 11:56:53.000 [warn] Proxy Client: unable to connect to
46.101.199.19:9443 ("general SOCKS server failure")
May 31 11:58:18.000 [warn] Proxy Client: unable to connect to
46.101.199.19:9443 ("general SOCKS server failure")
May 31 11:59:32.000 [warn] Proxy Client: unable to connect to
46.101.199.19:9443 ("general SOCKS server failure")
May 31 12:01:15.000 [warn] Proxy Client: unable to connect to
46.101.199.19:9443 ("general SOCKS server failure")
May 31 12:03:00.000 [warn] Proxy Client: unable to connect to
46.101.199.19:9443 ("general SOCKS server failure")
May 31 12:04:07.000 [warn] Proxy Client: unable to connect to
46.101.199.19:9443 ("general SOCKS server failure")
May 31 12:05:08.000 [warn] Proxy Client: unable to connect to
46.101.199.19:9443 ("general SOCKS server failure")
On 05/31/2018 11:07 AM, Hamid Safe
wrote:
Dear Teor,
I tried your suggestion ,but the result is the same no
misconfigs and all the data valid and identical. Did I emphasize
that I have another client and got the torrc config copied from
it? it does include the id key fingerprint too as it is stated
under the server sides's pt_state/obfs4_bridgeline.txt
line. Both machines are ArchLinux and packages are installed
and in path.
But in the new machine I see this on
/var/log/tor/notices.log:
May 31 10:17:49.000 [warn] Proxy Client:
unable to connect to <serverIP>:<obfs4proxy
port> ("general SOCKS server failure")
and
this log the /var/lib/tor/pt_state/obfs4proxy.log:
2018/05/31 10:53:05 [ERROR]:
obfs4([scrubbed]:8080) - outgoing connection failed: read:
i/o timeout
I am
pretty sure followed the steps like the first time...
Any advice?
On 05/30/2018 08:55 PM, teor wrote:
I currently do have a working private tor relay with
obfs4. The single client user is my laptop which is
working fine now,but I would like to add more clients to
that relay. I thought having the private signaure and
config in client's torrc is enough but it fails on the new
laptop at 10% with circuit error. Do I need to set up or
generate some more config on the new client? How can I fix
this issue.
Can you please help?
Try using the client bridge line from:
DataDir/pt_state/obfs4_bridgeline.txt
T
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
|