Select the hardware on which you want install YunoHost :
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 server online.
The links to the images are currently broken. While we resolve the issue, you can find them directly on https://build.yunohost.org/
If your host OS is 32 bits, be sure to download the 32-bit image.
If you wish to check the validity of our signed images, you can download our public key.
It's okay if you can only have 32-bit versions, just be sure that you downloaded the 32-bit image previously.
This step is important to properly expose the virtual machine on the network
Go to Settings > Network:
Start the virtual machine after selecting the YunoHost image.
If you encounter the error "VT-x is not available", you probably need to enable Virtualization in the BIOS of your computer.
You should see a screen like this:
N.B.: Once you have validated the keyboard layout, the installation will be launched and will completely erase the data on your hard disk!
The YunoHost project simplified the classic installation as much as possible in order to avoid as many people as possible being lost with questions that are too technical or related to specific cases.
With the expert mode installation, you have more possibilities, especially concerning the exact partitioning of your storage media. You can also decide to use the classic mode and add your disks afterwards.
Expert graphical install.
In general, we recommend against partitioning
/root on separate partitions. This will prevent you from having to worry about full partitions that could crash your machine, cause app installations to fail, or even corrupt your databases.
For performance reasons, it is recommended to mount your fastest storage (SSD) on the root
If you have one or more hard drives to store data, you can choose to mount it on one of these folders depending on your usage.
||User folders accessible via SFTP|
||YunoHost backups to be placed ideally elsewhere than on the disks that manage the data|
||Heavy data from YunoHost applications (nextcloud, matrix...)|
||Heavy data shared between several applications|
If you want flexibility and don't want to (re)size partitions, you can also choose to mount on
/mnt/hdd and follow this tutorial to mount all these folders with
Be aware that if you encrypt all or part of your disks, you will have to type the passphrase every time you restart your server, which can be a problem if you are not on site. There are however solutions (quite difficult to implement) that allow you to type the passphrase via SSH or via a web page (search for "dropbear encrypted disk").
Keep in mind that:
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.
In an internet browser, type
yunohost-2.local, and so on if multiple YunoHost servers are on your network).
If this doesn't work, you can look for the the local IP address of your server. 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.
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, do not take the habit of blindly accepting this kind of security alert!)
You should then land on this page :
You can also perform the postinstallation with the command
yunohost tools postinstall directly on the server, or via SSH.
This will be the domain used by your server's users to access the authentication portal. You can later add other domains, and change which one is the main domain if needed.
If you're new to self-hosting and do not already have a domain name, we recommend using a .nohost.me / .noho.st / .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).
This password will be used to access to your server's administration interface. You will also use it to connect via SSH or SFTP . In general terms, this is your system's key, choose it carefully!
Once the postinstall is done, you should be able to actually log in the web admin interface using the administration password.
So far, your server now has an
admin user - but
admin is not a "regular" user and can't be used to log on the user portal.
Let's therefore add a first "regular" user.
The first user you create is a bit special : it will receive emails sent to
email@example.com. These emails may be used to send technical informations or alerts.
Go in Users > Click on "+ New User" button
yunohost user create johndoe
The diagnosis system is meant to provide an easy way to validate that all critical aspects of your server are properly configured - and guide you in how to fix issues. The diagnosis will run twice a day and send an alert if issues are detected.
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
ynh.fr domain), add a swapfile if not enough ram and/or port forwarding.
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.
To run a diagnosis, go on Web Admin in the Diagnosis section. Click Run initial diagnosis and you should get a screen like this :
yunohost diagnosis run yunohost diagnosis show --issues --human-readable
Once you configured DNS records and port forwarding (if needed), you should be able to install a Let's Encrypt certificate. This will get rid of the spooky security warning from earlier for new visitors.
For more detailed instructions, or to lean more about SSL/TLS certificates, see the corresponding page here.
Go in Domains > Click on your domain > SSL Certificate
yunohost domain cert install
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 your favourite applications. Don't forget to plan backups !
Found errors? Think you can improve this documentation? Simply click the Edit link at the top of the page, and then the icon on Github to suggest changes.
Powered by Grav + with by Trilby Media.