tor@.service / tor@service failing
See original GitHub issueThere is a failed service:
₿ systemctl --type=service | grep tor@
  tor@default.service                                                                               loaded active     running      Anonymizing overlay network for TCP
● tor@service.service                                                                               loaded failed     failed       Anonymizing overlay network for TCP (instance service)
fixed by:
sudo systemctl disable tor@service
sudo systemctl reset-failed tor@service
I wonder it should not be enabled in https://github.com/rootzoll/raspiblitz/blob/2bb53ceb9626c3d4c43c4cf7f76574db9dc7f6e9/home.admin/config.scripts/tor.install.sh#L221 what do you think @nyxnor ?
Issue Analytics
- State:
 - Created 2 years ago
 - Comments:9 (5 by maintainers)
 
Top Results From Across the Web
Tor service failing to start in Linux
The relevant error is Failed to bind one of the listener ports . You already have something running which is bound to one...
Read more >Ok so I put "tor service status" and I get an error message.
This should be simple to fix. "Unit tor.service could not be found." is all I get. I'm in root so I know I...
Read more >1290444 – Tor service fails to start - Red Hat Bugzilla
service failed because the control process exited with error code. See "systemctl status tor.service" and "journalctl -xe" for details. # systemctl status tor ......
Read more >Tor failed because the service did not take the steps required ...
Failed to start Anonymizing overlay network for TCP (multi-instance-master). tor.service: Scheduled restart job ... tor --version. Tor version ...
Read more >Failed to start tor.service: Unit tor.service is masked. - Reddit
Normally I use TOR as a proxy by running this on startup: USR@USR:~$ sudo service tor start Failed to start tor.service: Unit tor.service...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@rootzoll this is a litd error just appears with torsocks because the binary is run with tor because of the Lightning Terminal Connect would leak the IP otherwise.
Looks like the config does not have the PasswordB placed as the password for the GUI.
Likely fixed with 5970f03d