add onion only usecase

This commit is contained in:
nihilist 2025-01-11 21:04:24 +01:00
parent 793fc88b0d
commit cf6545b0f2

View file

@ -232,6 +232,21 @@ HiddenServicePort 80 127.0.0.1:4445
<pre><code class="nim">
[ nowhere.moe ] [ /dev/pts/11 ] [~debian-tor/onions]
→ cat /etc/nginx/sites-available/nowhere.moe.conf
server {
######## TOR WEBSITE ########
listen 4443;
listen [::]:4443;
server_name daturab6drmkhyeia4ch5gvfc2f3wgo6bhjrv3pz6n7kxmvoznlkq4yd.onion;
root /srv/blog/;
index index.html;
}
</pre></code>
<p>That's how you do it for an onion-only website ^ but if you also have clearnet (meaning your website is reachable publicly via port 80 and 443) you can add onion support like so:</p>
<pre><code class="nim">
[ nowhere.moe ] [ /dev/pts/11 ] [~debian-tor/onions]
→ cat /etc/nginx/sites-available/nowhere.moe.conf
server {
listen 80;
listen [::]:80;
@ -398,6 +413,7 @@ nginx: configuration file /etc/nginx/nginx.conf test is successful
</code></pre>
<img src="3.png" class="imgRz">
<p>Now that we have our website up and running, it's better to configure some <strong>DoS countermeasures</strong> to avoid any unpleasant problems.</p>
<p>There are many countermeasures, one of the most effective is <strong>PoW</strong>. If you want to learn more about other DoS prevention methods check the <a href="https://community.torproject.org/onion-services/advanced/dos/">guidelines</a>. If you want to learn more about how PoW works, check out the <a href="https://onionservices.torproject.org/technology/pow/">FAQs</a>.</p>
<p>Without further ado, let's enable PoW for our onion service.