doc/pages/01.administrate/05.install/install.md

title	template	taxonomy	never_cache_twig	twig_first	process	page-toc	routes
Install YunoHost	docs	category docs	true	true	markdown twig true true	active depth true 2	default aliases /install /docker /install_iso /install_on_vps /install_manually /install_on_raspberry /install_on_arm_board /install_on_debian /install_on_virtualbox /plug_and_boot /burn_or_copy_iso /boot_and_graphical_install /postinstall

{% set arm, at_home, regular, rpi2plus, rpi1, rpi0, arm_sup, arm_unsup, vps, vps_debian, vps_ynh, virtualbox, internetcube, docker = false, false, false, false, false, false, false, false, false, false, false, false, false, false %} {% set hardware = uri.param('hardware') %} {% if hardware == '' %} {% set hardware = 'vps_debian' %} {% endif %}

{% if hardware == 'regular' %} {% set regular = true %} {% elseif hardware == 'internetcube' %} {% set arm, arm_sup, internetcube = true, true, true %} {% elseif hardware == 'rpi2plus' %} {% set arm, rpi2plus = true, true %} {% elseif hardware == 'rpi1' %} {% set arm, rpi1 = true, true %} {% elseif hardware == 'rpi0' %} {% set arm, rpi0 = true, true %} {% elseif hardware == 'arm_sup' %} {% set arm, arm_sup = true, true %} {% elseif hardware == 'arm_unsup' %} {% set arm, arm_unsup = true, true %} {% elseif hardware == 'vps_debian' %} {% set vps, vps_debian = true, true %} {% elseif hardware == 'vps_ynh' %} {% set vps, vps_ynh = true, true %} {% elseif hardware == 'virtualbox' %} {% set at_home, virtualbox = true, true %} {% elseif hardware == 'docker' %} {% set docker = true %} {% endif %}

{% if arm or regular %} {% set at_home = true %} {% endif %}

Select the hardware on which you want install YunoHost : [div class="flex-container"]

[div class="flex-child hardware{%if virtualbox %} active{% endif %}"] [figure caption="VirtualBox"][/figure] [/div]

[div class="flex-child hardware{%if rpi2plus or rpi1 or rpi0 %} active{% endif %}"] [figure caption="Raspberry Pi"][/figure] [/div]

[div class="flex-child hardware{%if arm_sup or arm_unsup or internetcube %} active{% endif %}"] [figure caption="ARM board"][/figure] [/div]

[div class="flex-child hardware{%if regular %} active{% endif %}"] [figure caption="Regular computer"][/figure] [/div]

[div class="flex-child hardware{%if vps_debian or vps_ynh %} active{% endif %}"] [figure caption="Remote server"][/figure] [/div]

[/div] [div class="flex-container pt-2"]

{% if rpi2plus or rpi1 or rpi0 %} [div class="flex-child hardware{%if rpi2plus %} active{% endif %}"] [figure caption="Raspberry Pi 2, 3 or 4"][/figure] [/div]

[div class="flex-child hardware{%if rpi1 %} active{% endif %}"] [figure caption="Raspberry Pi 1"][/figure] [/div]

[div class="flex-child hardware{%if rpi0 %} active{% endif %}"] [figure caption="Raspberry Pi zero"][/figure] [/div] {% elseif arm_sup or arm_unsup or internetcube %}

[div class="flex-child hardware{%if internetcube %} active{% endif %}"] [figure caption="Internet cube With VPN"][/figure] [/div]

[div class="flex-child hardware{%if arm_sup and not internetcube %} active{% endif %}"] [figure caption="Olinuxino lime1&2 or Orange Pi PC+"][/figure] [/div]

[div class="flex-child hardware{%if arm_unsup %} active{% endif %}"] [figure caption="Others boards"][/figure] [/div] {% elseif vps_debian or vps_ynh %}

[div class="flex-child hardware{%if vps_debian %} active{% endif %}"] [figure caption="VPS or dedicated server with Debian 10"][/figure] [/div]

[div class="flex-child hardware{%if vps_ynh %} active{% endif %}"] [figure caption="VPS or dedicated server with YunoHost pre-installed"][/figure] [/div]

{% endif %}

[/div]

{% if docker %} !! YunoHost doesn’t support Docker officially since issues with versions 2.4+. In question, YunoHost 2.4+ doesn’t work anymore on Docker because YunoHost requires systemd and Docker has chosen to not support it natively (and there are other problems link to the firewall and services). !! !! We strongly discourage you to run YunoHost on docker with those images

Community images

However, community images exist and are available on Docker Hub:

• AMD64 (classic) (ancienne version de YunoHost)
• I386 (old computers) (ancienne version de YunoHost)
• ARMV7 (Raspberry Pi 2/3 ...) (ancienne version de YunoHost)
• ARMV6 (Raspberry Pi 1) (old yunoHost version) {% else %}

Pre-requisites

{% if regular %}

• A x86-compatible hardware dedicated to YunoHost: laptop, nettop, netbook, desktop with 512MB RAM and 16GB capacity (at least) {% elseif rpi2plus %}
• A Raspberry Pi 2, 3 or 4 {% elseif rpi1 %}
• A Raspberry Pi 1 with at least 512MB RAM {% elseif rpi0 %}
• A Raspberry Pi zero {% elseif arm_sup %}
• A VPN with a dedicated IP and a .cube file
• An Orange Pi PC+ or an Onlinuxino Lime 1 or 2 {% elseif arm_sup %}
• An Orange Pi PC+ or an Onlinuxino Lime 1 or 2 {% elseif arm_unsup %}
• An ARM board with at least 512MB RAM {% elseif vps_debian %}
• A dedicated or virtual private server with Debian 10 (with kernel >= 3.12)) preinstalled, 512MB RAM and 16GB capacity (at least) {% elseif vps_ynh %}
• A dedicated or virtual private server with yunohost preinstalled, 512MB RAM and 16GB capacity (at least) {% elseif virtualbox %}
• An x86 computer with VirtualBox installed and enough RAM capacity to be able to run a small virtual machine with 512MB RAM and 8GB capacity (at least) {% endif %} {% if arm %}
• A power supply (either an adapter or a MicroUSB cable) for your board;
• A microSD card: 16GB capacity (at least) and Class 10 speed rate are highly recommended (like the Transcend 300x); {% endif %} {% if regular %}
• A USB stick at least 1GB capacity) OR a standard blank CD {% endif %} {% if at_home %}
• A reasonable ISP, preferably with a good and unlimited upstream bandwidth {% if rpi0 %}
• An usb OTG or a wifi dongle to connect your Raspberry Pi Zero {% else %}
• An ethernet cable (RJ-45) to connect your server to your router. {% endif %}
• A computer to read this guide, write the image and access to your server. {% endif %} {% if not at_home %}
• A computer or a smartphone to read this guide and access to your server. {% endif %}

{% if virtualbox %} ! N.B. : Installing YunoHost in a VirtualBox is usually intended for testing. To run an actual server on the long-term, you usually need a dedicated physical machine (old computer, ARM board...) or a VPS online. {% endif %}

{% if vps_ynh %}

YunoHost VPS providers

Here are some VPS providers supporting YunoHost natively :

[div class="flex-container"]

[div class="flex-child"] [figure caption="Alsace Réseau Neutre - FR"][/figure] [/div]

[/div] {% endif %}

{% if at_home %}

[fa=download /] Download the YunoHost image

{% if virtualbox %} !!! If your host OS 32 bits, be sure to download the 32-bit image. {% endif %}

{% if not virtualbox %}

{% if arm %}

Flash the YunoHost image

{% else %}

Flash the YunoHost image

{% endif %}

Now that you downloaded the image of YunoHost, you should flash it on {% if arm %}a SD card{% else %}a USB stick or a CD.{% endif %}

[ui-tabs position="top-left" active="0" theme="lite"] [ui-tab title="(Recommended) With Etcher"]

Download Etcher for your operating system and install it.

Plug your USB stick, select your YunoHost image and click "Flash"

[/ui-tab] [ui-tab title="With UNetbootin"]

Download UNetbootin for your operating system and install it.

Put your USB stick on, select your YunoHost image and click "OK"

[/ui-tab] [ui-tab title="With dd"]

If you are on GNU/Linux / macOS and know your way around command line, you may also flash your USB stick or SD card with dd. You can identify which device corresponds to your USB stick or SD card with fdisk -l or lsblk. A typical SD card name is something like /dev/mmcblk0. BE CAREFUL and make sure you got the right name.

Then run :

# Replace /dev/mmcblk0 if the name of your device is different...
dd if=/path/to/yunohost.img of=/dev/mmcblk0

[/ui-tab] {% if regular %} [ui-tab title="Burning a CD/DVD"] For older devices, you might want to burn a CD/DVD. The software to use depends on your operating system.

• On Windows, use ImgBurn to write the image file on the disc

• On macOS, use Disk Utility

• On GNU/Linux, you have plenty of choices, like Brasero or K3b [/ui-tab] {% endif %} [/ui-tabs]

{% else %}

Create a new virtual machine

Change network settings

! This step is important to properly expose the virtual machine on the network

Go to Settings > Network:

• Select Bridged adapter
• Select your interface's name: wlan0 if you are connected wirelessly, else eth0.

{% endif %}

{% if arm %}

[fa=plug /] Power up the board

• Plug the ethernet cable (one side on your main router, the other on your board).
  • For advanced users willing to configure the board to connect to WiFi instead, see for example here.
• Plug the SD card
• (Optional) You can connect a screen+keyboard directly on your board if you want to troubleshoot the boot process or if you're more comfortable to "see what happens" or want a direct access to the board.[/details]
• Power up the board
• Wait a couple minutes while the board autoconfigure itself during the first boot
• Make sure that your computer (desktop/laptop) is connected to the same local network (i.e. same internet box) as your server.

{% elseif virtualbox %}

[fa=plug /] Boot up the virtual machine

Start the virtual machine after selecting the YunoHost image.

! If you encounter the error "VT-x is not available", you need probably need to enable Virtualization in the BIOS of your computer.

{% else %}

[fa=plug /] Boot the machine on your USB stick

• Plug the ethernet cable (one side on your main router, the other on your server).
• Boot up your server with the USB stick or a CD-ROM inserted, and select it as bootable device by pressing one of the following keys (hardware specific): <ESC>, <F9>, <F10>, <F11>, <F12> or <DEL>.
  • N.B. : if the server was previously installed with a recent version of Windows (8+), you first need to tell Windows, to "actually reboot". This can be done somewhere in "Advanced startup options". {% endif %}

{% if regular or virtualbox %}

[fa=rocket /] Launch graphical install

!! N.B. : The installation will totally erase the data on the server's hard drive!

You should see a screen like this:

[figure class="nomargin" caption="Preview of the ISO menu"] [/figure]

1. Select Graphical install
2. Select your language, your location and your keyboard layout
3. The installer will then download and install all required packages.

{% endif %}

{% elseif vps_debian %}

[fa=rocket /] Run the install script

Once you have access to a command line on your server (either directly or through SSH), you can install YunoHost by running (as root) :

curl https://install.yunohost.org | bash

!!! If curl is not installed on your system, you might need to install it with apt install curl. !!! Otherwise, if the command does not do anything, you might want to apt install ca-certificates

!!! Note for advanced users concerned with the curl|bash approach: consider reading "Is curl|bash insecure?" on Sandstom's blog, and possibly this discussion on Hacker News.

{% endif %}

Proceed with initial configuration

!!! If you are in the process of restoring a server using a YunoHost backup, you should skip this step and instead restore the backup instead of the postinstall step.

[ui-tabs position="top-left" active="0" theme="lite"] [ui-tab title="From the web interface"] {%if at_home %} In an internet browser, type {% if internetcube %}https://internetcube.local{% else %}https://yunohost.local{% endif %}.

!!! If this doesn't work, you can look for the the local IP address of your server (see finding your local IP). The address typically looks like 192.168.x.y, and you should therefore type https://192.168.x.y in your browser's address bar. {% else %} You can perform the post-installation with the web interface the public IP address of your server. Typically, your VPS provider should have provided you with the IP of the server. {% endif %}

! During the first visit, you will very likely encounter a security warning related to the certificate used by the server. For now, your server uses a self-signed certificate. You will later be able to add a certificate automatically recognized by web browsers as described in the certificate documentation. For now, you should add a security exception to accept the current certificate. (Though PLEASE, don't take the habit to blindly accepting this kind of security alerts !)

{% if not internetcube %} You should then land on this page :

[figure class="nomargin" caption="Preview of the Web initial configuration page"] [/figure]

{% endif %} [/ui-tab] [ui-tab title="From the command line"]

You can also perform the postinstallation with the command yunohost tools postinstall directly on the server, or via SSH.

[figure class="nomargin" caption="Preview of the command-line post-installation"] [/figure]

[/ui-tab] [/ui-tabs]

{% if not internetcube %}

[fa=globe /] Main domain

This will be the domain used by your server's users to access the authentication portal. It can later be changed if needed.

• If you're new to self-hosting and do not already have a domain name, you might want to choose a sub-domain of .nohost.me, .noho.st or .ynh.fr (e.g. homersimpson.nohost.me). Provided that it's not already taken, the domain will be configured automatically and you won't need any further configuration step. Please note that the downside is that you won't have full-control over the DNS configuration.

• If you already own a domain name, you probably want to use it here. You will later need to configure DNS records as explained here.

!!! Yes, you have to configure a domain name. If you don't have any domain name and don't want a .nohost.me / .noho.st / .ynh.fr either, you can set up a dummy domain such as yolo.test and tweak your /etc/hosts file such that this dummy domain points to the appropriate IP, as explained here).

[fa=key /] Administration password

This password will be used to access to your server's administration interface. You would also use it to connect via SSH or SFTP. In general terms, this is your system's key, choose it carefully!

[fa=user /] Create a first user

Once the postinstall is done, you should be able to connect to actually log in the web admin interface using the administration password.

So far, your server has an admin user - but this user is not a "regular" user and can't be used to log on the user portal.

Let's therefore add a first user.

!!! The first user you create is a bit special : it will receive emails sent to root@yourdomain.tld and admin@yourdomain.tld. These emails may be used to send technical informations or alerts.

[ui-tabs position="top-left" active="0" theme="lite"] [ui-tab title="From the web interface"]

Go in Users > Add

TODO: add a screenshot [/ui-tab] [ui-tab title="From the command line"]

yunohost user create johndoe

TODO : copypasta an actual shell session will all info asked etc..

[/ui-tab] [/ui-tabs] {% endif %}

[fa=stethoscope /] Run the initial diagnosis

The diagnosis system is meant to provide an easy way to validate that all critical aspects of your server are properly configured. The diagnosis will run twice a day and send an alert if something's not okay.

!!! N.B. : don't run away ! The first time you run the diagnosis, it is quite expected to see a bunch of yellow/red alerts because you typically need to configure DNS records (if not using a .nohost.me/noho.st/ynh.fr domain) and/or port forwarding (if hosting at home).

!!! If an alert is not relevant (for example because you don't intend on using a specific feature), it is perfectly fine to flag the issue as 'ignored' by going in the webadmin > Diagnosis, and clicking the ignore button for this specifc issue.

[ui-tabs position="top-left" active="0" theme="lite"] [ui-tab title="(Recommended) From the web interface"] To run a diagnosis, go on Web Admin in the Diagnosis section. You should get a screen like this :

[figure class="nomargin" caption="Preview of the diagnostic panel"] [/figure]

[/ui-tab] [ui-tab title="From the command line"]

yunohost diagnosis run
yunohost diagnosis show --issues --human-readable

[/ui-tab] [/ui-tabs]

[fa=lock /] Get a Let's Encrypt certificate

Once your DNS and router configuration are ok, you should be able to install a a Let's Encrypt certificate. This will get rid of the spooky security warning from earlier for new visitors.

For more detailled instructions, or to lear more about SSL/TLS certificates, see the corresponding page here.

[ui-tabs position="top-left" active="0" theme="lite"] [ui-tab title="From the web interface"]

[figure class="nomargin" caption="Preview of the diagnostic panel"] [/figure]

[/ui-tab] [ui-tab title="From the command line"]

yunohost domain cert-install

[/ui-tab] [/ui-tabs] {% endif %}

Congratz!

You now have a pretty well configured server. If you're new to YunoHost, we recommend to have a look at the guided tour. You should also be able to install applications. Don't forget to configure backups !