Hi Ben
Am 19.09.2018 um 13:56 schrieb Ben Riley:
So I type 'tor' and get
Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running on
Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma
5.2.2, and Libzstd 1.3.3.
Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning
Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc".
Sep 19 21:34:24.823 [notice] Based on detected system memory,
MaxMemInQueues is set to 2862 MB. You can override this by setting
MaxMemInQueues by hand.
Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled.
Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050
First listener to port 9050 for localhost
Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051
Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001
Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050
Second listener to port 9050 for all ips
Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address already
in use. Is Tor already running?--
Your torrc wants tor to expect both socks AND directory requests at port
9050. Only one can.
Check the torrc file and move the Dirport to 9030. Restart tor and check
the log again if it works better. Somewhere should be the entry
"Self-testing indicates your DirPort is reachable from the outside.
Excellent." Same for Orport. If you dont't need socks you can change it
to <SocksPort 0>.
I hope I got you right. Good luck!
[] https://www.torproject.org/docs/tor-manual.html.en