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:

On 29 May 2018, at 03:51, Hamid Safe <hsafe@devopt.net> 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
https://gitweb.torproject.org/pluggable-transports/obfs4.git/tree/README.md#n89

T
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays