Feb 24 10:45:08.668 [notice] Tor 0.3.2.9 (git-64a719dd25a21acb) running on
Linux with Libevent 2.0.19-stable, OpenSSL 1.0.1t,
Zlib 1.2.7, Liblzma N/A, and Libzstd N/A.
Feb 24 10:45:08.668 [notice] Tor can't help you if you use it wrong! Learn how
to be safe at https://www.torproject.org/downl
oad/download#warning
Feb 24 10:45:08.668 [notice] Read configuration file "/etc/tor/torrc".
Feb 24 10:45:08.671 [notice] Based on detected system memory, MaxMemInQueues is
set to 2891 MB. You can override this by sett
ing MaxMemInQueues by hand.
Feb 24 10:45:08.671 [notice] Scheduler type KIST has been enabled.
Feb 24 10:45:08.671 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 24 10:45:08.671 [notice] Opening Control listener on 127.0.0.1:9051
Feb 24 10:45:08.671 [notice] Opening OR listener on 0.0.0.0:9001
Feb 24 10:45:08.671 [notice] Opening Directory listener on 0.0.0.0:80
Feb 24 10:45:08.000 [notice] Not disabling debugger attaching for unprivileged
users.
Feb 24 10:45:08.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 24 10:45:08.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 24 10:45:08.000 [notice] Configured to measure statistics. Look for the
*-stats files that will first be written to the d
ata directory in 24 hours from now.
Feb 24 10:45:08.000 [warn] You are running Tor as root. You don't need to, and
you probably shouldn't.
Feb 24 10:45:08.000 [notice] Your Tor server's identity key fingerprint is '123'
Feb 24 10:45:08.000 [notice] Bootstrapped 0%: Starting
Feb 24 10:45:09.000 [notice] Starting with guard context "default"
Feb 24 10:45:09.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Feb 24 10:45:10.000 [notice] Bootstrapped 85%: Finishing handshake with first
hop
Feb 24 10:45:11.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Feb 24 10:45:12.000 [notice] Tor has successfully opened a circuit. Looks like
client functionality is working.
Feb 24 10:45:12.000 [notice] Bootstrapped 100%: Done
Feb 24 10:45:12.000 [notice] Now checking whether ORPort ***:9001 and DirPort
***:80 are reachable... (th is
may take up to 20 minutes -- look for log messages indicating success)
Feb 24 10:45:13.000 [notice] Self-testing indicates your DirPort is reachable
from the outside. Excellent.
Feb 24 10:45:13.000 [notice] Self-testing indicates your ORPort is reachable
from the outside. Excellent. Publishing server d
escriptor.
Feb 24 10:45:14.000 [notice] Performing bandwidth self-test...done.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 24 February 2018 5:40 PM, teor <teor2...@gmail.com> wrote:
> > On 25 Feb 2018, at 04:23, Gabe D. ga...@protonmail.com wrote:
> >
> > Hey Guys,
> >
> > Ive an issue... I wanted to aid the network and setup a tor exit node,
> > however its failing to do so, everything looks perfect config wise and it
> > says "publishing server descriptor" no errors but the node never shows up
> > in tor atlas, is there something i may be doing wrong?
> >
> > This is my config:
> >
> > ORPort 9001
> >
> > ExitRelay 1
> >
> > Nickname **
> >
> > ContactInfo **
> >
> > DirPort 80
> >
> > DisableDebuggerAttachment 0
> >
> > ControlPort 9051
> >
> > CookieAuthentication 1
>
> What does Tor say in its logs when it starts up?
>
> We need to see the all the lines up to "publishing descriptor".
>
> Is your relay on a public IP address?
>
> T
>
> tor-relays mailing list
>
> tor-relays@lists.torproject.org
>
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
