May 1, 2017 at 15:23How to raise your i2p site (eepsite) to VDS (VPS) under Ubuntu (LAMP). Brief briefing for beginners
- Tutorial
- Recovery mode
Background: the other day a book was written about the new state system ( State-Domain ), which is waiting for us in the near future. And since Roskomnadzor reacts inadequately to such things, it decided to create a site on its i2p private network under its scribble. In the course of the creation, I had to solve some technical issues, which I will discuss below, trying to save your time, at the same time I will be cheated.
So , there is a remote VPS under Ubuntu, and you need to place the site on it. For, you can, of course, make it on your laptop, but when the laptop is turned off, the site is inaccessible (personally, it invariably annoys me in .i2p and .onion).
Further, I assume that your LAMP is already configured, and normally sends content to the regular Internet. Those. you already have a couple of ordinary (non-i2p) sites spinning on it.
First we put i2p on Ubuntu:
We configure the i2p router as a constantly working daemon:
In the course of configuration (through the graphical interface) you will need to answer a few simple questions, put autorun, I left the default 128 MB, in general, I think you will have no problems with this.
Upon completion of the configuration, the i2p daemon will start on its own.
Now we need the panel with the web interface of the i2p router to be accessible remotely. To do this, open the file
And change it
on the
Where instead
Set the external IP of your VPS. There is another option (from i2p developers) where you can replace with:
but I have not tried it.
Now you have access to the web interface for managing your remote i2p router.
FIRST CASE go to:
(substitute the IP of your VPS instead of 80.80.80.80) and set the login password (so that no one is fired). Now you have access to the web console only (well, I hope so).
The guide recommends: “Go to localhost : 7657 / index.jsp and click on“ Soft Restart ”, this will restart the JVM and all applications . ” Do it. Do not forget to substitute the localhost IP of your VPS.
Now here is the jamb with i2p under Ubuntu 16.04: in the left pane of the web console you will see the inscription:
This is due to the fact that Ubuntu 16.04 uses ... in general, you need to install another Java, stable. I chose an option from Oracle.
and further:
Now all you have to do is create a new HTTP tunnel to your site. You can do it here:
(Change IP only)
Select "New open service" - HTTP (default) and click "Create". In field
Indicate the IP of your VPS. Indicate the port on which the server is running (say, apache2, usually 80 or 8080), and in the field:
Write something like:
Put a daw on startup. Change the Name (N) and Description (e) if desired .
Do not touch the rest. Click on "Save."
Voila! Now your site is visible by a 32-bit key-address (like this: pqajparec44p74uvpxvxhpd5u3neuqs2t4awwd6bcieku3juhwwa.b32.i2p ) on the i2p network. And if you add your site to the address books of various services, for example, here: stats.i2p , then over time your domain name moysite.i2p , which you specified earlier, will fall into the address books of other services. And your site will be able to find directly by this name, or through jump-services.
A good question. In general, I also tested the installation on a production server with virthosts and solved the problem like this: assigned a different port to the site for i2p (which we prescribed earlier when creating the tunnel). Let's do it together. Open:
And write there:
For example, let us have this port number 8088.
In another config:
Write something like:
(by all means close the VirtualHost tag - on Habr there is a glitch with the display of this piece of code)
DocumentRoot, of course, change the path to the real one, to the one where you actually have the DocumentRoot folder for your i2p site. If not, create one. Save everything. Restart Apache:
If you do not want your i2p site to be visible from the normal Internet, put the .htaccess in the DocumentRoot directory as follows:
80.80.80.80 - change to the IP of your VDS.
Go to stats.i2p and add your site to the service there.
After adding your site becomes accessible, for example, like this:
stats.i2p / cgi-bin / jump.cgi? A = r.i2p
(this is the address of the site, which I did)
And yes, in general, it’s more logical, not host an i2p site on a working VPS. It is better to take something separate under i2p. Well, I see it that way.
If there is an extra. installation questions - well in kamenty.
Links to used docks:
→ geti2p.net/en/faq
→ help.ubuntu.ru/wiki/i2p
→ help.ubuntu.ru/wiki/java
So , there is a remote VPS under Ubuntu, and you need to place the site on it. For, you can, of course, make it on your laptop, but when the laptop is turned off, the site is inaccessible (personally, it invariably annoys me in .i2p and .onion).
Further, I assume that your LAMP is already configured, and normally sends content to the regular Internet. Those. you already have a couple of ordinary (non-i2p) sites spinning on it.
First we put i2p on Ubuntu:
sudo apt-add-repository ppa:i2p-maintainers/i2p
sudo apt-get update
sudo apt-get install i2pWe configure the i2p router as a constantly working daemon:
sudo dpkg-reconfigure -plow i2pIn the course of configuration (through the graphical interface) you will need to answer a few simple questions, put autorun, I left the default 128 MB, in general, I think you will have no problems with this.
Upon completion of the configuration, the i2p daemon will start on its own.
Now we need the panel with the web interface of the i2p router to be accessible remotely. To do this, open the file
/var/lib/i2p/i2p-config/clients.configAnd change it
clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/on the
clientApp.0.args=7657 80.80.80.80 ./webapps/Where instead
80.80.80.80Set the external IP of your VPS. There is another option (from i2p developers) where you can replace with:
clientApp.0.args=7657 0.0.0.0 ./webapps/but I have not tried it.
Now you have access to the web interface for managing your remote i2p router.
FIRST CASE go to:
http://80.80.80.80:7657/configui(substitute the IP of your VPS instead of 80.80.80.80) and set the login password (so that no one is fired). Now you have access to the web console only (well, I hope so).
The guide recommends: “Go to localhost : 7657 / index.jsp and click on“ Soft Restart ”, this will restart the JVM and all applications . ” Do it. Do not forget to substitute the localhost IP of your VPS.
Now here is the jamb with i2p under Ubuntu 16.04: in the left pane of the web console you will see the inscription:
Caution: ECDSA is not available. Update Java or OS.
This is due to the fact that Ubuntu 16.04 uses ... in general, you need to install another Java, stable. I chose an option from Oracle.
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installerand further:
sudo update-java-alternatives -s java-8-oracleNow all you have to do is create a new HTTP tunnel to your site. You can do it here:
http://80.80.80.80:7657/i2ptunnelmgr(Change IP only)
Select "New open service" - HTTP (default) and click "Create". In field
Access Point: Address (H):
Indicate the IP of your VPS. Indicate the port on which the server is running (say, apache2, usually 80 or 8080), and in the field:
Website Name (W):
Write something like:
moysite.i2pPut a daw on startup. Change the Name (N) and Description (e) if desired .
Do not touch the rest. Click on "Save."
Voila! Now your site is visible by a 32-bit key-address (like this: pqajparec44p74uvpxvxhpd5u3neuqs2t4awwd6bcieku3juhwwa.b32.i2p ) on the i2p network. And if you add your site to the address books of various services, for example, here: stats.i2p , then over time your domain name moysite.i2p , which you specified earlier, will fall into the address books of other services. And your site will be able to find directly by this name, or through jump-services.
But if my server gives several virthosts on one socket, how do I know which domain will be visible on the i2p network?
A good question. In general, I also tested the installation on a production server with virthosts and solved the problem like this: assigned a different port to the site for i2p (which we prescribed earlier when creating the tunnel). Let's do it together. Open:
/etc/apache2/ports.confAnd write there:
Listen 8088For example, let us have this port number 8088.
In another config:
/etc/apache2/sites-enabled/000-default.confWrite something like:
ServerAdmin webmaster@localhost
DocumentRoot /var/www/moysite
ErrorLog ${APACHE_LOG_DIR}/error8088.log
CustomLog ${APACHE_LOG_DIR}/access8088.log combined
(by all means close the VirtualHost tag - on Habr there is a glitch with the display of this piece of code)
DocumentRoot, of course, change the path to the real one, to the one where you actually have the DocumentRoot folder for your i2p site. If not, create one. Save everything. Restart Apache:
sudo service apache2 restartIf you do not want your i2p site to be visible from the normal Internet, put the .htaccess in the DocumentRoot directory as follows:
Order deny,allow
Deny from all
Allow from 80.80.80.8080.80.80.80 - change to the IP of your VDS.
Go to stats.i2p and add your site to the service there.
After adding your site becomes accessible, for example, like this:
stats.i2p / cgi-bin / jump.cgi? A = r.i2p
(this is the address of the site, which I did)
And yes, in general, it’s more logical, not host an i2p site on a working VPS. It is better to take something separate under i2p. Well, I see it that way.
If there is an extra. installation questions - well in kamenty.
Links to used docks:
→ geti2p.net/en/faq
→ help.ubuntu.ru/wiki/i2p
→ help.ubuntu.ru/wiki/java
