In terms of free software for handling multimedia files, FFmpeg is a powerful and flexible tool. It can be used to convert, edit, and stream videos and audios.

However, using FFmpeg on shared hosting presents certain challenges and limitations for both users and hosts.

You should opt for the Cloud Server offer for using FFmpeg.

You can also turn to the service of VOD/AOD Infomaniak.

This guide explains how to mount the volume dedicated to storing your data on your VPS Cloud on Windows. In the case of a VPS Lite, the procedure is not necessary as there is only one disk, even on Windows.

Mount the storage volume

To mount the storage volume on Windows, you need to go to the "Disk Management" tool and bring the disk online:

• Right-click on the Start menu.
• Search for Disk Management.
• On the left-hand side, identify the offline disk (usually an icon with a white arrow on a red background and a blue icon).
• Right-click on it to select Online.

To initialize the disk and create a volume:

• Once the disk is online, right-click on it and select Initialize Disk.
• Choose between MBR (for disks < 2 TB) and GPT (recommended for disks > 2 TB), then click OK.
• Then, right-click on the unallocated space on the disk and select New Simple Volume.
• Follow the wizard steps to assign a drive letter, format the volume in NTFS, and then finish by clicking Finish.

The disk will now be accessible from Windows File Explorer.

You can also use diskpart the Windows disk and partition management utility.

This guide explains how to reboot a VPS Cloud / VPS Lite and what you can do if you no longer have access to the server.

Reboot of VPS Cloud / VPS Lite

The classic mode allows you to normally reboot your server. To access the VPS Cloud / VPS Lite:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on the Manage button.
4. Click on Restart (classic mode):
   
    

Enable/disable safe mode

If you have lost your SSH key, or made a configuration error, etc.

You have the option to reboot in rescue mode. This involves rebooting from a base image from which you can mount the partitions of your cloud. This way, you will be able to modify/repair your configuration.

To activate the rescue mode:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on the Manage button.
4. Click on Reboot (safe mode):
   
   
    

Perform operations

Once safe mode is active, access your Cloud via SSH, either with your ssh key or with the temporary password available in the interface.

Once connected, do:

sudo -i

then list the available partitions (replace ov-abcd by your hostname):

[root@ov-abcd ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 8G 0 disk
└─vda1 253:1 0 8G 0 part /
vdb 253:16 0 20G 0 disk
└─vdb1 253:17 0 20G 0 part

vdb corresponds to your cloud disk.

To access it in write mode, you must mount it:

[root@ov-abcd ~]# mount /dev/vdb1 /mnt/

You can then edit the files:

[root@ov-abcd ~]# ls /mnt/
bin boot dev etc home initrd.img initrd.img.old lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.old

Depending on your cloud's operating system, you can also perform a chroot to replicate your usual environment:

[root@ov-abcd ~]# chroot /mnt/
bash: ls: command not found
root@ov-abcd:/# export PATH="$PATH:/usr/sbin:/sbin:/bin"
root@ov-abcd:/# ls
bin boot dev etc home initrd.img initrd.img.old lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.old

Once the necessary modifications have been made, disable safe mode to restart your cloud on the original disk.

This guide details the creation of a GIT repository both on your Web Hosting and on your Cloud Server Infomaniak.

Preamble

• GIT and GITHub are available by default on the two aforementioned supports.
• For additional help, contact a partner or launch a free tender — also discover the role of the host.

Creation of the GIT repository

Setting up on the server:

• The GIT repository is located at /git_depot
• The site is located in the folder /web/[projet] (on your FTP server)

Commands to enter:

cd
mkdir git_depot
cd git_depot/
git init --bare [projet].git
cd [projet].git
git update-server-info

Sending the local repository to the server

To do on the local machine:

git init
git remote add origin ssh://user@[xxxxx].ftp.infomaniak.com:/home/clients/[123465789]/git_depot/[projet].git
git status
git add .
git commit -a -m "init"
git push --set-upstream origin master
git push

Cloning the site to the server directory

To do on the server:

cd
cd web
rm -r [projet]/
git clone /home/clients/[123465789]/git_depot/[projet].git [projet]/

This guide helps resolve any issues with activating your Windows Server license.

Change the registered key

Open the Run utility (key Windows logo + R).

Remove the registered key

Run the following command:

cscript.exe c:\windows\system32\slmgr.vbs -upk

Add a new key

Relaunch the Run utility and then execute the following command:

cscript.exe c:\windows\system32\slmgr.vbs -ipk {CLE}

replacing {CLE} with the key from your configuration below:

Activate Windows

Restart the Run utility and then run the following command to associate the key with the Infomaniak activation bot:

cscript.exe c:\windows\system32\slmgr.vbs -skms kms.infomaniak.cloud

Restart the Run utility and then run the following command to activate your Windows system:

cscript.exe c:\windows\system32\slmgr.vbs -ato

The CGID module for Apache has been disabled on Infomaniak's shared web hosting offers.

If necessary, you should consider switching to a **Cloud Server** if you are currently on shared web hosting. This can be done seamlessly: refer to **this other guide** for more information.

This guide explains how to replace, within an Infomaniak Web hosting, the address of a site currently a subdomain (https://dev.domain.xyz for example) with the main domain (https://domain.xyz).

Preamble

• The operations in brief:
  1. We start with a site created and accessible via the URL of the main domain dev.domain.xyz.
  2. We add an alias domain.xyz.
  3. We swap the two types (the main domain becomes an alias and the alias becomes the main domain).
  4. We remove the old name dev.domain.xyz.
• Note that the site remains in the original folder on the server; the name of this location may be in the form /sites/dev.domain.xyz but this has absolutely no impact on the live site.
• Also, familiarize yourself with the last chapter of this other guide.

The operations in detail

To switch from a site with a subdomain address "dev.domain.xyz" to a direct address "domain.xyz":

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on the chevron ‍ to expand the Domains section of this site:
4. Click on the button Add a domain:
   
5. Add the desired new name, check the corresponding boxes.
6. Click on the button to Confirm:
   
7. Once the addition is complete, click on the action menu ⋮ located to the right of the relevant item.
8. Choose to set the item as the primary domain:
   
9. Confirm the operation to proceed with the domain swap.

This guide provides instructions to synchronize kDrive with a VPS (or vice versa) via the WebDAV protocol found in the rClone application.

Prerequisites

• Have a VPS.
• Know your kDrive identifier (kDrive ID).

Synchronize kDrive and VPS via rClone

The operation allows you to retrieve in real-time the files and folders from kDrive and to read, create or modify these files from your VPS while ensuring that they are synchronized again on the kDrive server. An rClone mount point can be created with a folder on your VPS to manipulate these kDrive files.

Refer to the rClone documentation if you are looking for information about the available options:

1. Example of rClone command:

   • rclone mount kdrive:/My_kDrive_Folder_Path /home/ubuntu/Target_Folder_Path --vfs-cache-mode full --vfs-cache-max-age 24h --vfs-cache-max-size 10G --cache-dir /home/ubuntu/rclone/cache --daemon --allow-other --dir-cache-time 1h --log-file /home/ubuntu/rclone/rclone.log --log-level INFO

   • The --daemon attribute of this command allows you to start the synchronization in the background because without it, this sync ends with each disconnection of the VPS…
2. Example of an rClone configuration file:

   • [kdrive]
     type = webdav
     url = https://***.connect.kdrive.infomaniak.com/***
     vendor = other
     user = ***
     pass = ***

   • Server address: https://IDkDrive.connect.kdrive.infomaniak.com (see the prerequisites above)
   • Username: email address to log in to the Infomaniak user account
   • Password: application password if two-factor authentication is enabled or ‍your Infomaniak user account password if you have not enabled 2FA

This guide explains how to install and configure systemd on a Serveur Cloud and presents the main commands that can be used.

Prerequisites

• Follow the installation guide for systemd on Serveur Cloud.
• Consult the official documentation to learn about all the possibilities offered by systemd
• The "unit" files must be placed in: ~/.config/systemd/user/ (/home/clients/absolute-path-id/.config/systemd/user) (replacing absolute-path-id visible in your Manager) and the permissions must be set to 0644.
• The --user parameter must be specified in each command.

Main commands

Here is a non-exhaustive list of commands that can be used with systemd.

Force systemd to reload the unit files and take the changes into account:

systemctl --user daemon-reload

Activating a service:

systemctl --user enable --now SERVICENAME.service

Checking the status of a service:

systemctl --user status SERVICENAME.service

Configuration of Node as a service with systemd

It will be necessary to create a "Unit" file with the ".service" extension, which will need to be saved in the directory:

~/.config/systemd/user/

It is possible to reuse the example below by replacing the values starting with {}:

[Unit]
Description={Le nom du service} # Spécifier ici un nom du service. Celui-ci est obligatoire mais n'a pas d'impact sur le fonctionnement

[Service]
Restart=always
Environment=NODE_VERSION={la version souhaitée} # Spécifier ici la version de Node à utiliser. S'assurer qu'elle soit installée au préalable avec "nvm install {la version souhaitée}"
WorkingDirectory=%h/{repertoire du projet Node} # %h correspond à la racine de l'hébergement
ExecStart=/bin/bash -c "exec $HOME/.nvm/nvm-exec {commande de lancement du script node}" # Cette commande dépend du projet. Par exemple, "npm run start", "npm run serve" ou encore "node server.js" sont courants

[Install]
WantedBy=default.target

Additional actions with a Unit file

systemctl --user daemon-reload

Start the service (if it is already active, nothing happens):

systemctl --user start [Nom du Unit]

Stop the service (if it is not active, nothing happens):

systemctl --user stop [Nom du Unit]

Restart the service (if it is not running, it will be started):

systemctl --user restart [Nom du Unit]

Get information about the service; namely:

• "Active" which indicates whether the service is running and for how long
• "CGroup" shows the process group managed by the service, this allows you to see the active processes, with their arguments and their ID

Below "CGroup" are any logs (the standard output and error of the process):

systemctl --user status [Nom du Unit]

Enable automatic startup of the service at server boot; NB: this does not start the service:

systemctl --user enable [Nom du Unit]

Disable the automatic startup of the service at server boot; NB: this does not stop the service:

systemctl --user disable [Nom du Unit]

Configuration with user entries:

[Unit]
Description="nom service"

[Service]
Restart=always
Environment=NODE_VERSION=16.17
WorkingDirectory=%h/sites/"nom-repertoire-site"/
ExecStart=/bin/bash -c "exec $HOME/.nvm/nvm-exec npm run start"

[Install]
WantedBy=default.target

This guide explains how to enable PHP-FPM status to, for example, debug a slow site at the PHP level.

Preamble

• PHP-FPM status allows you to monitor in real-time the scripts that are executed as well as their execution time.
• This operation is only possible on Serveur Cloud.

Enable PHP-FPM status

To activate PHP-FPM on a site, contact Infomaniak support from an email address listed on your user account to authenticate your request.

In your request, please specify the source IP address that should be authorized.

Once PHP-FPM status is activated, the following URL links will display the necessary information:

• https://domain.xyz/fpm-status?json&full
• https://domain.xyz/fpm-status?html&full
• https://domain.xyz/fpm-status?xml&full

Warning: if your site contains rewrite rules including the path /fpm-status, you will likely need to make an exception for it.