Open fsantiago07044 opened 6 years ago
Hi! The README explains in detail how you have to configure your Tor node and your Box to achieve this.
Honestly yet this is the most advanced setup you can operate with - and therefore a number of issues you could encounter.
My proposal: Begin with a local setup (box & node on the same system), then advance to a remote connection (box on your remote pc, ControlPort of the Tor node accessible from a remote system), continue to a (non authorized) hidden service to finally setup a hidden service with HiddenServiceAuthorizeClient
.
According to my experience, the first few connection attempts in that fully featured setup usually create a SocketTimeout
. It seems that creating the route through the network needs some time. I'm yet able to always establish a working connection finally.
February 4, 2018 10:53 AM, "ralphwetzel" notifications@github.com wrote:
Hi! The README explains in detail how you have to configure your Tor node and your Box to achieve this.
Honestly yet this is the most advanced setup you can operate with - and therefore a number of issues you could encounter.
My proposal: Begin with a local setup (box & node on the same system), then advance to a remote connection (box on your remote pc, ControlPort of the Tor node accessible from a remote system), continue to a (non authorized) hidden service to finally setup a hidden service with HiddenServiceAuthorizeClient.
According to my experience, the first few connection attempts in that fully featured setup usually create a SocketTimeout. It seems that creating the route through the network needs some time. I'm yet able to always establish a working connection finally.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
i haven't tried yet running it locally but i will.
in the meantime, i feel my issue is with my local tor proxy config and / or theonionbox's cfg. I've read your readme but it's not clear to me.
for hidden service config, is the only required config section for TOB:
[MyProxyNode] control=proxy host=7an5onionad2res2.onion port=9876 cookie=xa3NyourCookY6herexTOB
the [tor] section seems to be for monitoring a node locally. so not needed in my case ?
the next section [TorProxy] seems to pertain to my local tor proxy. i've tried configuring it and i can see in logs they're speaking to each other (my tor proxy and tob) but still the timeouts persist. I've also seen errors stating invalid port 'default'.
??
Thanks for your help.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
It does work remotely to the control port directly in the open. Hidden service no good yet.
If you provide some information, I could try to support:
From your local torrc:
ControlPort
SocksPort
From your The Onion Box configuration file (only those lines that you changed vs. the default settings):
From your remote Tor torrc
:
ControlPort
HiddenServicePort
Hello, I was having trouble and wanted to see if anyone here could help me determine what I'm doing wrong.
Trying to monitor my exit node from a remote PC. The remote is fedora 27 with python 2.7 and Tor running as a proxy by default. on the node I've setup a hidden service with cookie auth.
I keep getting socks timeout errors.
Does anyone have a sample config they can show me? Thanks.