2

I'm starting tor using sudo service tor start. When checking sudo service tor status, it's saying:

$ sudo service tor status
● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
   Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled)
   Active: active (exited) since Fri 2019-02-22 15:43:14 UTC; 6min ago
  Process: 24491 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 24491 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/tor.service

Feb 22 15:43:14 raspberrypi systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)...
Feb 22 15:43:14 raspberrypi systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).

In my torrc, I only added this:

HiddenServiceDir /var/lib/tor/sshd/
HiddenServiceVersion 3
HiddenServicePort 1234 127.0.0.1:9735

I switched on debugging, but there doesn't seem to be any problem:

Feb 22 15:43:15.000 [notice] Tor 0.3.5.8 opening log file.
Feb 22 15:43:15.518 [notice] Tor 0.3.5.8 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0j, Zlib 1.2.8, Liblzma 5.2.2, and Libzstd 1.1.2.
Feb 22 15:43:15.519 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 22 15:43:15.519 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 22 15:43:15.519 [notice] Read configuration file "/etc/tor/torrc".
Feb 22 15:43:15.536 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 22 15:43:15.536 [notice] Opened Socks listener on 127.0.0.1:9050
Feb 22 15:43:15.000 [warn] Your log may contain sensitive information - you're logging more than "notice". Don't log unless it serves an important reason. Overwrite the log afterwards.
Feb 22 15:43:15.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 22 15:43:16.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 22 15:43:17.000 [notice] Bootstrapped 0%: Starting
Feb 22 15:43:21.000 [notice] Starting with guard context "default"
Feb 22 15:43:22.000 [notice] Signaled readiness to systemd
Feb 22 15:43:22.000 [notice] Opening Socks listener on /run/tor/socks
Feb 22 15:43:22.000 [notice] Opened Socks listener on /run/tor/socks
Feb 22 15:43:22.000 [notice] Opening Control listener on /run/tor/control
Feb 22 15:43:22.000 [notice] Opened Control listener on /run/tor/control
Feb 22 15:43:22.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Feb 22 15:43:22.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Feb 22 15:43:22.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Feb 22 15:43:22.000 [notice] Bootstrapped 100%: Done

How can I find out why my tor is not starting?

  • Have you tried checking if SOCKS5 tor proxy works on 127.0.0.1:9050? – NeverMine17 Feb 22 at 18:10
  • In case you mean whether anything is already running on that port, then no, lsof -i :9050 doesn't return anything – user1406177 Feb 22 at 18:27
  • What kind of OS are you running and how did you install tor? – NeverMine17 Feb 22 at 18:30
  • I'm using raspian and followed this guide for debian stretch: torproject.org/docs/debian.html.en – user1406177 Feb 22 at 18:38
  • 1
    Try stopping tor using sudo service tor stop and run it from console: tor – NeverMine17 Feb 23 at 9:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.