<p> Before we start, make sure you either rent a VPS anonymously (tor+XMR + ssh via tor) click <ahref="https://kycnot.me/search?q=hosting&type=service">here</a> for the list of anonymity-friendly hosting providers or rent a VPS on a cloud provider that <ahref="https://community.torproject.org/relay/community-resources/good-bad-isps/">explicitly</a> allows for tor exit nodes to be hosted on their platform.</p>
<p>As a disclaimer, you need to know who allows these tor exit nodes, if you're going to pick a random host provider to host an exit node for you,
you really don't know how the host may respond to that. Therefore it is best to pre-emptively see who actually accepts those exit nodes by looking at their TOS or
by contacting them for additional information. </p>
<imgsrc="1.png"class="imgRz">
<p> ⚠️ Beware that authorities aren't always aware of tor exit node and what to do from a legal stand point. Before hosting an exit node, please take time to do sufficient legal research.
People have been arrested all around the world and had a lot of trouble with authorities because they hosted exit nodes.
If you are still motivated to get your own exit node, keep the phone number of a lawyer specialised in this field just in case anything goes wrong. ⚠️ </p>
<p>Now you can get a domain name to resolve to your exit node, or just use the one provided by njal.la :</p>
<p>Now regarding the choice of location for the server, in order to make sure that Tor remains decentralised, make sure that you are picking a country that doesn't have many tor nodes (see the <ahref="https://metrics.torproject.org/bubbles.html#country">bubbles graph</a>):</p>
<imgsrc="../relay/country.png"class="imgRz">
<p><u>Disclaimer:</u><b>Do not host your Tor node in Germany, Netherlands or in the US, as there are already too many nodes in those countries.</b> Try to run your own Tor nodes in countries that have the least nodes preferably, as this will help keeping the Tor network decentralized.</p>
<p>Next we make sure it's an exit like so: (be aware that this is where it gets dangerous if you're not doing this on a non-KYC VPS, or on a cloud provider that doesnt accept tor exit nodes.</p>
Jan 29 10:43:03 exit Tor[3855]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Jan 29 10:43:04 exit Tor[3855]: Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Jan 29 10:43:04 exit Tor[3855]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Jan 29 10:43:04 exit Tor[3855]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Jan 29 10:43:05 exit Tor[3855]: Bootstrapped 100% (done): Done
Jan 29 10:43:05 exit Tor[3855]: Now checking whether IPv4 ORPort 80.78.22.215:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jan 29 10:43:05 exit Tor[3855]: Now checking whether IPv6 ORPort [2a0a:3840:8078:22:0:504e:16d7:1337]:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jan 29 10:43:06 exit Tor[3855]: Self-testing indicates your ORPort [2a0a:3840:8078:22:0:504e:16d7:1337]:9001 is reachable from the outside. Excellent.
Jan 29 10:43:06 exit Tor[3855]: Self-testing indicates your ORPort 80.78.22.215:9001 is reachable from the outside. Excellent. Publishing server descriptor.
Jan 29 10:43:06 exit Tor[3855]: Performing bandwidth self-test...done.
root@exit:~# nyx
</code></pre>
<p>Then wait a few hours for the exit node to appear on tor metrics, then you can take the node fingerprint (example 916EDD8E5D61613BBC7B6CCEFB2778AE706786B9) and check it's status on torproject.org <ahref="https://metrics.torproject.org/rs.html#search/flag:exit">here</a>.</p>
<p>After that, you need to wait 2 weeks for the exit node to be fully operational as explained <ahref="https://blog.torproject.org/lifecycle-of-a-new-relay/">here</a>.</p>
<pre><codeclass="nim">
"A new relay, assuming it is reliable and has plenty of bandwidth, goes through four phases: the unmeasured phase (days 0-3) where it gets roughly no use, the remote-measurement phase (days 3-8) where load starts to increase, the ramp-up guard phase (days 8-68) where load counterintuitively drops and then rises higher, and the steady-state guard phase (days 68+). "
Until there is Nothing left.</p></br></br><p>Creative Commons Zero: <ahref="../../../../opsec/runtheblog/index.html">No Rights Reserved</a></br><imgsrc="\CC0.png">
