#975939 tor: Tor fails to boot when SOCKSPORT set to anything but localhost

Package:
tor
Source:
tor
Description:
anonymizing overlay network for TCP
Submitter:
mike
Date:
2020-11-27 07:45:03 UTC
Severity:
normal
#975939#5
Date:
2020-11-27 01:59:20 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

0


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.
   * What exactly did you do (or not do) that was effective (or
     ineffective)? Commenting out the SOCKSPORT ip.of.my.server:9050 resolves the issue.
*** End of the template - remove these template lines ***
#975939#12
Date:
2020-11-27 07:37:09 UTC
From:
To:
Does it work if you set SocksPort to 0.0.0.0:9100?  What does syslog say
in either case?