-
-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug #122
Comments
@htrgouvea I think teh issue mainly that you are trying to start 2 instances of tor and its being bind by default to the same port. ( because the configs files could not be found) OR as in the configs in arch config the Tranport was commented leading to tor using the default port.
I don't know instead of providing the config files to be used in first command I think cat'ing dirctly the settings into the /etc/tor/torrc would fix the issue there seems to be an issue in config files/iptable?. as even when everything is configured right no connection is been established. I installed tor-router on top of it and it works by using their setting. its not optimum. |
Hi @ajmandourah, In the pastNipet worked that way, but many people complained that Nipe overwritten their torrc files... I even added warning messages or permission requests about, but nothing resolved. But I think I can remove the current 2 lines and leave only one... I don't remember why I did it that way, I'll review |
Related to: #134 |
Error:
Job for tor.service failed because the control process exited with error code. See "systemctl status tor.service" and "journalctl -xe" for details.
The text was updated successfully, but these errors were encountered: