Translating VPN advantage page on yunohost doc



Salut à tous !

J’ai remarqué que la page Avantage d'un VPN pour l'auto-hébergement | Yunohost Documentation n’était pas traduite en anglais ce que je trouve dommage étant donné que la thématique de l’utilisation d’un VPN est récurrente sur le forum.

Voici une proposition de traduction (qui mérite surement relecture par un natif et, à mon sens, quelques adaptation concernant les spécificités des FAI français qui n’intéresse pas forcement les anglais).

Comment faire pour l’ajouter sur github ? Je suis un peu perdu pour savoir si je suis en train de modifier la version française ou anglaise…

Hi !

I noticed that the Avantage d'un VPN pour l'auto-hébergement | Yunohost Documentation page was not translated in English which I find a pity since the theme of the use of a VPN is recurrent on the forum.

Here is a proposal of translation (which deserves surely a proofreading by a native and, in my opinion, some adaptation concerning the specificities of the French ISP which does not necessarily interest the English).

How to add it on github ? I’m a bit lost to know if I’m modifying the french or english version…

Advantage of a VPN for self-hosting

Since setting up a server at home is an uncommon practice, most Internet connections provided to individuals are unsuitable for this purpose. A VPN respecting net neutrality and providing a fixed IPv4 address and IPv6 addresses can help to circumvent some limitations or difficulties.

Be careful: not all existing VPN providers meet these conditions, make sure the one you choose meets them.
Plug & Play

By configuring a VPN on your server, you will be able to make it accessible to the rest of the Internet without having to change the configuration of the router you connect it to. This can be really handy if you are going on vacation, moving or have an Internet outage, as you will be able to easily connect it to someone you trust without having to configure the router of the person helping you.

Likewise, you save yourself the trouble of opening your router’s ports and bypassing hairpinning.
No micro DNS outages

If your Internet connection does not have a fixed public IP, you will be forced to set up a dynamic domain name (Dynamic DNS). This solution may be acceptable, but the DNS will only be updated at regular intervals (every two minutes if it is a or domain name). So there is a chance that this will cause display errors in the browser from time to time, or even that another site will be displayed (the risks are however reduced because the practice of self-hosting is not widespread).

With a neutral VPN, this problem is circumvented because the VPN can be compared to a Virtual Internet connection, which has its own fixed IPv4 address, so there is no need to update the domain name.
The case of email

Email is one of the most complex protocols to self-host, usually it is the last thing a user self-hosts. Indeed, it is very easy to find yourself in a situation where emails sent by the server are refused by the recipient SMTP servers.

To avoid this you need to :

  • configure the reverse DNS of the server’s Internet connection (or VPN)
  • a fixed IPv4
  • that this IPv4 is removable from all blacklists (notably the IP must not be on the DUL)
  • to be able to open port 25 (as well as the other SMTP ports)

Unfortunately, none of the most common French ISPs respect all these points.

To overcome this, the use of a VPN respecting these points can be an alternative.

Finally, if you do not want the content of your server’s communications to be spied on by equipment present on your ISP’s network, you can use a VPN to encrypt your communications and deport your trust to a VPN provider. As a reminder, since 2015, the government officially deploys black boxes at the large network operators whose objective is to tap all French digital communications in order to preserve the scientific, economic and industrial interests of France.

A neutral VPN has a cost since the operator who provides it must run a server and use bandwidth. The prices of the FFDN’s associative VPN are around 6 € per month.
Packet path

When you set up a VPN on your server, if you don’t set up any particular configuration, the transfer of a file from a computer on the local network to the server using the VPN, will go through the end of the VPN i.e. through the server of the VPN provider.

To solve this problem, there are two solutions:

  • transform the server into a router and connect the home equipments to it, these equipments will then benefit from the VPN confidentiality too.
  • use the YunoHost server as a DNS resolver when you are at home, in order to redirect the server’s domain names to the local IP rather than the public IP. This operation can be done either on each equipment or on the router (if the latter allows it).


If you have an account on github, you can do like this:

  1. Go on GitHub - YunoHost/doc: YunoHost documentation
  2. Fork the project fork
  3. On your forked project, go on pages/01.administrate/07.specific_use_cases/10.vpn
  4. Upload your new into this dir thanks to the button Add file addfile
  5. Save the change in a new branch with a commit message that explain what you did:
  6. You should get a screen that suggest you to create a pull request of your branch onto the master branch of the official project, create this pull request:

And next, your Pull request will be reviewed and merge :slight_smile:

Alternatively, i can do it for you, however the commit won’t be at your name…

it should be good but I didn’t find how to change the name of the branch that github created for me automatically “patch-5”.

I’ll take the opportunity to propose a german translation, which also needs to be proofread.

1 Like