Open codeless03 opened 3 years ago
@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.
system ("tor -f .configs/$device{distribution}-torrc > /dev/null");
system ($startTor);
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: https://github.com/htrgouvea/nipe/issues/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.