On Thu, 26 Nov 2020, mike wrote:
> I have a server on the LAN that hosts a few minor Tor hidden services.
> I'd like it to also allow connections from the LAN to allow other
> computers on the LAN to use the SOCKSPORT rather than each one have to
> individually run their own tor proxy. In torrc if I set the following
> the tor daemon fails to bootstrap when I restart the machine.
> /var/log/tor/notices.log is empty upon boot and systemctl status tor
> shows as loaded, but the daemon doesn't allow connections from nyx or
> any other application.
> Changing to SOCKSPORT :9100 results in the same problem. On reboot tor
> fails to load without error, but when restarting tor via systemd tor
> works fine.
Does it work if you set SocksPort to 0.0.0.0:9100? What does syslog say
in either case?
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `- https://www.debian.org/
