2

i've recently decided to support Tor throught a new relay, then i taked one of my server with debian 8 and follow the steps on torproject website after installing the most recently tor i've edited the torrc file uncommenting this:

ORPort 9001
DirPort 9030
Exitpolicy accept *:*
Nickname RELAYNAME
ContactInfo INFO@RELAYNAME
BandwidthRate 60 MBytes
BandwidthBurst 60 MBytes

after that i simply restarted the Tor service and checked the log:

Oct 18 19:24:12.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Oct 18 19:24:12.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Oct 18 19:24:13.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Oct 18 19:24:13.000 [notice] Bootstrapped 100%: Done
Oct 18 19:24:13.000 [notice] Now checking whether ORPort x.x.x.x:9001 and DirPort x.x.x.x:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Oct 18 19:24:14.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent.
Oct 18 19:24:15.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Publishing server descriptor.
Oct 18 19:24:15.000 [notice] Performing bandwidth self-test...done.

And after atleast 45mins my relay appeared on Atlas, now i've tried to connect throught my server to Tor simply addingEntryNodes RELAYNAME, but Tor cannot connect to Tor network and still remain in Loading relay informations..

Improve this question

1 Answer 1

Reset to default
0

It needs some more time and - if your relay is not having a Guard flag - it's role is not an EntryGuard, so try using UseEntryGuards 0 with EntyNodes {your relay} and StrictNodes 1 - and post a log if you will still have an error

Improve this answer
24
  • LoL during this time i've tried to stop the process and stopped tor@default too but now it cannot be started again....im in panic..
    – Danielix
    Commented Oct 18, 2016 at 21:48
  • this is what i obtain if i do service tor@default restart: Job for [email protected] failed. See 'systemctl status [email protected]' and 'journalctl -xn' for details.
    – Danielix
    Commented Oct 18, 2016 at 21:56
  • so post your 'systemctl status [email protected]' and 'journalctl -xn' output, please
    – Alexey Vesnin ♦
    Commented Oct 18, 2016 at 21:58
  • systemctl: ● [email protected] - Anonymizing overlay network for TCP (instance default-service) Loaded: loaded (/lib/systemd/system/[email protected]; disabled) Active: inactive (dead)
    – Danielix
    Commented Oct 18, 2016 at 22:02
  • and journalctl?
    – Alexey Vesnin ♦
    Commented Oct 18, 2016 at 22:08

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .