i2p guide added to rss
This commit is contained in:
parent
2967576c5d
commit
de2c6bde79
87
rss.xml
87
rss.xml
|
@ -15,6 +15,93 @@
|
|||
|
||||
<!-- LB -->
|
||||
|
||||
<item>
|
||||
<title>Mirror your site over I2P</title>
|
||||
<guid>https://landchad.net/i2p.html</guid>
|
||||
<link>https://landchad.net/i2p.html</link>
|
||||
<pubDate>Sun, 29 Aug 2021 15:32:44 -0400</pubDate>
|
||||
<description><![CDATA[
|
||||
<header><h1>Mirror Your Site Over I2P</h1></header>
|
||||
|
||||
<main>
|
||||
<img class=titleimg src="pix/i2p.svg" alt="I2P logo">
|
||||
<p>
|
||||
Now you have a website, why not offer it in a private alternative such as the Invisible Internet?
|
||||
</p>
|
||||
<h2>Setting up I2P</h2>
|
||||
<p>
|
||||
There are 2 main I2P implementations, I2P and i2pd, we are using i2pd in this
|
||||
guide because it's easier to use in servers.
|
||||
</p>
|
||||
<h3>Installing I2P</h3>
|
||||
<p>
|
||||
i2pd is in most repos, in debian/ubuntu you can install it simply
|
||||
with <pre><code>apt install i2pd</code></pre>
|
||||
</p>
|
||||
<h3>Enabling I2P</h3>
|
||||
<p>
|
||||
We are going to create a user for i2pd, because i2pd finds the configuration
|
||||
files in its home directory. And it's easier (and more tidy) to have it in a separate user:
|
||||
</p>
|
||||
<pre><code>useradd -m i2p -s /bin/bash
|
||||
su -l i2p
|
||||
mkdir ~/.i2pd
|
||||
cd ~/.i2pd</code></pre>
|
||||
<p>
|
||||
Now that you're in ~/.i2pd, you have to create a file named
|
||||
"tunnels.conf". Which is the config file for every hidden service you're
|
||||
offering over I2P, the content should be like this:
|
||||
</p>
|
||||
<pre><code>[<strong>example</strong>]
|
||||
type = http
|
||||
host = 127.0.0.1
|
||||
port = 8080
|
||||
keys = <strong>example.dat</strong></code></pre>
|
||||
<h3>Getting your I2P Hostname</h3>
|
||||
<p>
|
||||
Then, run <code>/usr/sbin/i2pd --daemon</code> to start i2pd and we can retreive our I2P hostname.
|
||||
</p>
|
||||
<p>
|
||||
This can be done in lynx or a command-line browser by going to <code>http://127.0.0.1:7070/?page=i2p_tunnels</code> to get your I2P hostname.
|
||||
</p>
|
||||
<p>
|
||||
You
|
||||
can also run these commands to find your hostname:
|
||||
</p>
|
||||
<pre><code>printf "%s.b32.i2p
|
||||
" $(head -c 391 /home/i2p/.i2pd/<strong>example.dat</strong> |sha256sum|xxd -r -p | base32 |sed s/=//g | tr A-Z a-z)</code></pre>
|
||||
<h2>Adding the Nginx Config</h2>
|
||||
<p>
|
||||
From here, the steps are almost identical to setting up a normal website configuration file.
|
||||
Follow the steps as if you were making a new website on the webserver
|
||||
<a href="nginx.html">tutorial</a> up until the server block of code. Instead, paste this:
|
||||
</p>
|
||||
<pre><code>server {
|
||||
listen 127.0.0.1:8080 ;
|
||||
root /var/www/<strong>example</strong> ;
|
||||
index index.html ;
|
||||
}</code></pre>
|
||||
<aside>
|
||||
<h4>Clarifications<h4>
|
||||
<p>
|
||||
Nginx will listen in port 8080, but i2pd will forward your port
|
||||
8080 to the i2p site port 80. This way you don't have to deal with server names or anything like that
|
||||
</p>
|
||||
</aside>
|
||||
<p>
|
||||
From here we are almost done, all we have to do is enable the site and reload nginx which is also covered in <a href="nginx.html#enable">the webserver tutorial</a>.
|
||||
</p>
|
||||
<h3>Update regularly!</h3>
|
||||
<p>Make sure to update I2P on a regular basis by running:</p>
|
||||
<pre><code>apt update && apt install i2pd</code></pre>
|
||||
<p><strong>Contributor</strong> - <a href="https://qorg11.net" target="_blank">qorg11</a></p>
|
||||
</main>
|
||||
|
||||
|
||||
]]></description>
|
||||
</item>
|
||||
|
||||
|
||||
<item>
|
||||
<title>Setting up a Calibre library server</title>
|
||||
<guid>https://landchad.net/calibre.html</guid>
|
||||
|
|
Loading…
Reference in New Issue