This guide explains how to maintain control over your MP3/AAC or HLS Radio Streaming streams by activating unique key (token) protection to decide, for example, whether a listener can listen to your radio or not.

Preamble

• The principle is simple: with each connection, you will make a request to the Infomaniak API, which will return a unique token with a limited and configurable lifespan. This token will authorize anyone who possesses it to consume the stream during this period.
• You can protect an MP3/AAC or HLS stream independently of each other (the same applies to geolocation).
• Activating the restriction involves changing the stream configuration, which may take a few minutes to be replicated on the servers.

Protect an audio stream with a unique key

To do this, simply go to the restriction settings and activate token protection on the stream you wish to secure:

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 concerned.
3. Click on the name of the audio stream concerned.
4. Click on Restrictions in the left sidebar.
5. Choose HLS if necessary.
6. Click on the action menu ⋮ located to the right of the item concerned.
7. Click on Token Restriction:
   
    

Then activate the protection.

Warning, at the moment you activate this option, access to the stream will be instantly blocked for new connections. Adapt your Players to take into account the restriction, as illustrated in the example below:

Create a Radio API Token

To access the Radio API, you must first authenticate using an application token. This step only needs to be done once. To create this application token, refer to this other guide.

The scope is radio and unlimited lifetime to avoid having to regenerate a code regularly. Once the token is generated, copy it to paste it in the example below.

Example of use in PHP language

For MP3/AAC or HLS, the code can be substantially the same, only the URL called in POST changes in its form.

if (!defined('API_TOKEN')) {
     define('API_TOKEN', 'AYF5lSh3c7Xy5974Fs12RTkTThujT-L9R4Xk2ZfGyP6sV7QqJ1oC3jD8nFtKzIxUeMw5oNzR6');
}
/**
 * Fonction générique pour executer des requêtes cURL
 *
 * @param string $method Méthode HTTP (GET, POST, PUT, etc...)
 * @param string $url Url de l'api a requêter
 * @param array $headers Liste des en-têtes HTTP (l'autorisation doit être passée ici avec un ['Authorization: Bearer ']
 * @param array $payload Un tableau contenant les données pour créer un token
 * @return mixed
 */

function request(string $method, string $url, array $headers = [], array $payload = []): mixed{
    // prepare options array
    $opts = [
        CURLOPT_HTTPHEADER => $headers,
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_URL => $url,
        CURLOPT_CUSTOMREQUEST => strtoupper($method),
    ];

    // add payload if relevant
    if ($payload && $method !== 'GET') {
        $opts[CURLOPT_POSTFIELDS] = json_encode($payload);
    }
    $ch = curl_init();
    curl_setopt_array($ch, $opts);
    $result = curl_exec($ch);
    if(curl_errno($ch)){
        throw new Exception(curl_error($ch));
    }
    $data = json_decode($result, true);
    if ($data['result'] === 'error') {
        throw new Exception($data['error']['description'] ?? 'an error occured');

    }
    return $data['data'];
}

We are going to create the token, the URL for creating the token is broken down as follows:

• For an MP3/AAC stream

POST https://api.infomaniak.com/1/radios/acl/streams/mountpoint.mp3/token

Example to protect https://newradiotest.ice.infomaniak.ch/newradiotest-128.aac the route will be: https://api.infomaniak.com/1/radios/acl/streams/newradiotest-128.aac/token

• For an HLS stream

POST https://api.infomaniak.com/1/radios/acl/hls_streams/<stream>/token

Example to protect https://myradiostream.radiohls.infomaniak.com/myradiostream/manifest.m3u8 the route will be: https://api.infomaniak.com/1/radios/acl/hls_streams/myradiostream/token

Example in the case of MP3/AAC, remember to adjust:

$token = request(
    'POST',
   'https://api.infomaniak.com/1/radios/acl/streams/newradiotest-128.aac/token',
    // en-tête d'authorization
    [
        'Authorization: Bearer ' . API_TOKEN,
        'Content-Type: application/json',
    ],
    /**
     * payload pour créer le token, vous pouvez passer les valeurs suivantes
     * window     | 300               | optionnel | durée de validité du token (default: 5 minutes)
     */

    [
        'window' => 3600, // 1h validity
    ]
);

It is important to note that if this code is generated at the time of page loading, the listener will have "window" seconds to start playing the stream. Beyond this deadline, the token will expire, and the stream will no longer be able to be started unless the page is reloaded. Depending on your needs and use case, it will be necessary to adjust this delay in the best possible way.

You will also need to replace the playback URL of your stream below with the one indicated while keeping the parameter $token at the end. And finally, we display the Player (here a simple html5 tag, but you can of course add any overlay afterwards, the token being passed in the parameters $_GET of the url).

$streamUrl = "https://newradiotest.ice.infomaniak.ch/newradiotest-128.aac?$token";
echo "<audio controls=""><source src="$streamUrl"></audio>";

This guide explains the differences between Infomaniak's web hosting offers to help you choose the best solution according to your computer needs.

Starter Web Hosting

Free Web Hosting

Web Starter hosting is offered for free with each domain name registered with Infomaniak. It offers 10 MB of disk space to create a site (basic pages in HTML language only - no PHP, no database) even without particular knowledge thanks to the Welcome Page tool.

• Register or transfer a domain name with Infomaniak
• Learn more about the benefits included with a domain name

Shared Web Hosting

The flagship offer to create your sites

These web hostings are shared offers (the websites will be hosted on servers whose resources are shared with other customers). To ensure the reliability of these shared services, Infomaniak servers use on average only 40% of the CPU power and are equipped with professional last-generation SSD disks.

Web hosting offers a minimum of 250 GB of disk space and allows you to manage multiple websites with multiple domain names. This offer includes all the technologies usually used to create professional sites: PHP, MySQL, FTP and SSH access, SSL certificates and easy installation of WordPress or common CMS, etc. It is also possible to add a Node.js site and/or Site Creator.

Cloud Server

Professional Web Hosting

With a Cloud Server, the resources allocated to you are not shared with other customers and you can customize the hardware and software configuration of your server according to your needs. A Cloud Server also allows you to use components that are not available on shared web hostings (Node.js, mongoDB, Sol, FFMPEG, etc.).

• A Cloud Server allows you to easily administer your server via the same administration interface as web hostings - you manage the sites in the same way.
• A VPS allows you to manage your server 100% autonomously with the version of Windows or the Linux distribution of your choice (Debian, Ubuntu, openSUSE, ...) - solid technical skills are required to use a VPS, including VPS Lite.

Public Cloud (and Kubernetes Service)

Open, proven and secure IaaS solution

For Infomaniak, it is the infrastructure that powers kDrive, Swiss Backup and the Webmail, services used by several million users. But Public Cloud is accessible to everyone and provides the resources you need to develop your projects.

With personalized and tailored offers, you will have no trouble managing your development budget. No setup fees. No minimum amount. Cancellable at any time. You only pay for the resources actually used with Public Cloud at the end of each month, the same goes for Kubernetes Service.

Jelastic Cloud

Custom web hosting with your choice of technologies

Jelastic Cloud allows you to create custom development environments with your choice of technologies (PHP, Java, Docker, Ruby, etc.). It is a flexible cloud offer:

• Horizontal and vertical scaling of resources.
• Payment based on actual resource consumption.
• Easy customization of your infrastructure (redundancy, IP, SSL, load balancing, etc.).

This guide details the technical and administrative aspects of hosting multiple websites on the same platform.

Technically speaking

A hosting encompasses multiple websites. It is therefore possible to add several websites to a hosting (multi-site/multi-domain management). In this case, the resources of the hosting (disk space, databases, script execution time and memory, etc.) are shared among the different websites of the hosting.

The basic Serveur Cloud plan includes a certain number of hostings (for example 5) and a higher number of websites (for example 20). In this example, this means that you can create 20 websites (with 20 different domain names/subdomains) that you can freely organize across your 5 hostings.

Administratively

At the Organization level on the Infomaniak Manager, management and access rights cannot be assigned to a specific website on a hosting plan. A user you add to the Organization will not be able to have a right limited to a single site; they will always access the entire hosting plan.

However, it is possible to create an FTP user restricted to a specific folder on the server (in this case, it should be limited to the folder containing the site).

Limited management of one site among others on the same hosting can also be considered directly within the tool used for the site (WordPress user management for example).

This guide details the Managed Cloud Server offer from Infomaniak and the VPS offer from Infomaniak, which are intended for different uses.

Preamble

• Infomaniak offers two advanced hosting solutions:
  1. the Managed Cloud Server, which allows you to create multiple hosts (FTP/SSH spaces) on which you add your sites (Apache vhosts),
  2. and the VPS (Virtual Private Server), which offers complete administrative freedom and meets different needs.

Managed Cloud Server

The Cloud Server allows you to go beyond the limits of shared hosting. You can create and distribute your sites as you wish, define the root directory of each site, and adjust parameters such as memory_limit and max_execution_time.

Integrated tools are provided: cronjobs, Site Creator, simplified installation of WordPress, access and error logs (logs). It is also possible to add specific Apache modules or install a caching system.

The software environment is managed by Infomaniak (FastCGI, PHP-FPM). You do not have complete freedom to configure the server (no arbitrary software installation), but certain specific programs can be installed.

VPS (unmanaged)

The VPS gives you full control over the server, but it is your responsibility. Infomaniak manages the hardware and installs the version of Linux or Windows chosen at the time of ordering. No software intervention is performed by Infomaniak: you administer the system, install, and configure the software.

You can restart the server via the Infomaniak Manager. A snapshot system is available (excluding the VPS Lite offer).

Video content and alternatives

If your project mainly involves a large volume of videos, it is often preferable to separate video streaming from the main hosting. Associated with shared hosting, the Infomaniak VOD/AOD space allows you to efficiently store and stream videos, support traffic spikes, and obtain detailed viewing statistics.

Migration between Cloud Server and VPS

There is no automatic migration solution between a Managed Cloud Server and a VPS. To switch from one offer to another, you must cancel the product you no longer use and order the new offer. Infomaniak refunds, upon request, any new server if the cancellation occurs within 30 days of the order.

Thank you for trusting Infomaniak with the hosting of your website.

Preamble

• A web hosting is a storage space available on a computer, also called a "server", connected to the Internet and managed by a web host, Infomaniak.
• This storage space, made available to professionals and individuals, is used to install websites or other types of tools (CRM, extranet, intranet...) that need to be accessible via the Internet.
• These guides allow you to quickly use the essential functions of your new product, your web hosting, which can accommodate multiple websites.

Where to start?

1. Create a WordPress website
2. Build the site with Site Creator
3. Install a web application (ownCloud, Joomla, Typo3, Drupal, phpBB, Simple Machines Forum, Magento, Prestashop, ...)
4. Manage your FTP accounts/users
5. Manage and publish files on your hosting via FTP Manager
6. Manage your MySQL databases
7. Add a site or subdomain to your hosting (multisites/multi domains)
8. Link another domain name to an existing website (domain alias)
9. Preview your site even if your domain name does not yet point to Infomaniak's servers

IMPORTANT: the domain name...

A web hosting, to be visible to the public on the Internet, must be associated with a domain name!

Your domain name is not managed by Infomaniak? Or is it in a different Organization than that of your web hosting? Then refer to this other guide to configure the DNS or the "A records" in order to link the domain name to your web hosting.

In case of a problem

To resolve a problem, please consult the Web Hosting Knowledge Base before contacting Infomaniak support.

Click here to share a review or suggestion about an Infomaniak product.

This guide concerns UTM tags, or Urchin Tracking Module, tags added to URLs to track and analyze the performance of online marketing campaigns from the Newsletter tool.

Preamble

• These UTM tags, which are optional, consist of specific parameters such as source, medium, campaign, term, and content, which help identify the origin of a link's traffic.
• By using UTM tags, marketers can understand which campaigns generate traffic, which channels are most effective, and which ads or strategies work best, based on data collected by web analytics tools.
• The UTM tags thus allow you to create a match between the links present in your newsletters and the tracking of a tool like Google Analytics on your site.

Enable the UTM feature

To access your Newsletter:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. If necessary, click on the domain name concerned in the table that appears.
3. The interface of the Newsletter appears.

Enable this option in the very first step of creating your Newsletter. You will find three fields allowing you to enter keywords of type utm_parameters:

• campaign source (utm_source)
• campaign medium (utm_medium such as email for example)
• campaign name (utm_campaign = the name of your campaign for example)

So:

1. Fill in the 3 UTM fields in step 1 of Newsletter creation.
2. Insert a link to the URL of your site (the latter must be properly configured and analyzed by Google Analytics, for example) in the body of the Newsletter in step 3.
3. When the reader clicks on it, they will be taken to the URL followed by the terms "?utm_source=...&utm_medium=...&utm_campaign=..." with obviously your keywords in place of "...".

If you enter multiple keywords in these fields, any spaces will be replaced with underscores underscore _.

Later, it is planned to be able to enter dynamic formulas in these fields, such as today's date for example. Also, refer to the article https://news.infomaniak.com/comment-creer-un-objectif-google-analytics.

This guide concerns the recovery of the password for a Windows image (any version) on Public Cloud.

Connecting to the Windows instance

The default username is Administrator.

The password is generated during the first boot sequence of the instance.

If you cannot establish the first connection to your Windows instance, you need the private key used during the deployment process. Enter this command to install or check that nova-client is installed:

pip3 install python-novaclient

Then to retrieve the password for the instance:

nova get-password <INSTANCE_ID> <PRIVATE_KEY_FILE>

Refer to the official documentation. Also, be aware of any current issues on https://infomaniakstatus.com/. For Public Cloud specifically, the list of scheduled maintenances and current issues is at https://status.infomaniak.cloud/.

This guide presents several examples of using Varnish on Cloud Server Infomaniak.

Varnish Configuration

After installation, configuring Varnish includes important rules for caching and purging. Be careful not to accidentally allow unwanted IP addresses.

Here is what a basic configuration file might look like with a few common cases and different actions/rules in one example:

vcl 4.0;
# Configuration du backend par défaut
backend default {
    .host = "127.0.0.80";  # Adresse IP du backend
    .port = "80";           # Port du backend
}
# Définition d'une liste de contrôle d'accès (ACL) pour les IPs autorisées à purger le cache
acl purge {
    "localhost";            # IP locale
    "1.2.3.4";              # IP de votre domicile
    "42.42.42.0"/24;        # Plage d'IP publique de votre entreprise
    ! "42.42.42.7";         # Exclusion d'une IP spécifique (ex : un collègue gênant)
}
# Traitement des requêtes à leur réception par Varnish
sub vcl_recv {
    # Autoriser les requêtes de purge
    if (req.method == "PURGE") {
        # Vérification si l'IP du client est autorisée à purger
        if (!client.ip ~ purge) {  # 'purge' fait référence à l'ACL définie plus haut
            # Retourne une page d'erreur si l'IP n'est pas autorisée
            return (synth(405, "Cette IP n'est pas autorisée à envoyer des requêtes PURGE."));
        }
        # Si l'IP est autorisée, purger le cache pour cette requête
        return (purge);
    }
    # Autoriser la purge de toutes les images via une requête PURGEALL
    if (req.method == "PURGEALL" && req.url == "/images") {
        if (!client.ip ~ purge) {
            return (synth(405, "Cette IP n'est pas autorisée à envoyer des requêtes PURGE."));
        }
        # Invalider tous les objets en cache correspondant à des images
        ban("req.url ~ \.(jpg|png|gif|svg)$");
        return (synth(200, "Images purgées."));
    }
    # Ne pas mettre en cache les pages avec une autorisation (header Authorization)
    if (req.http.Authorization) {
        # Passer la requête directement au backend sans la mettre en cache
        return (pass);
    }
}
# Traitement de la réponse du backend avant de la renvoyer au client
sub vcl_backend_response {
    # Mise en cache des images pour une durée de 1 jour
    if (beresp.http.content-type ~ "image") {
        set beresp.ttl = 1d;
    }
    # Si le backend indique que la réponse ne doit pas être mise en cache, respecter cette consigne
    if (beresp.http.uncacheable) {
        set beresp.uncacheable = true;
    }
}

Purge from the CLI interface

From there, the rules stated in the configuration above apply to all requests, so if the configured site is "domain.xyz", you can simply use the CLI tool "curl" and do the following:

# Envoyer une requête PURGE pour purger la page d'accueil de "domain.xyz"
$ curl -X PURGE https://domain.xyz/
# Réponse renvoyée par le serveur Varnish
<!DOCTYPE html>
<html>
<head>
    <title>200 Purged</title>
</head>
<body>
    <h1>Erreur 200 : Purge effectuée</h1>
    <p>La page a été purgée avec succès.</p>
    <h3>Guru Meditation:</h3>
    <p>XID: 2</p>
    <hr>
    <p>Serveur de cache Varnish</p>
</body>
</html>

And there, the homepage has been purged. Or to purge another URL, simply point the request to the latter:

# Envoyer une requête PURGE pour purger un fichier spécifique à "domain.xyz"
$ curl -X PURGE https://domain.xyz/some_path/some_file.html
# Réponse renvoyée par le serveur Varnish
<!DOCTYPE html>
<html>
<head>
    <title>200 Purged</title>
</head>
<body>
    <h1>Erreur 200 : Purge effectuée</h1>
    <p>Le fichier a été purgé avec succès.</p>
    <h3>Guru Meditation:</h3>
    <p>XID: 4</p>
    <hr>
    <p>Serveur de cache Varnish</p>
</body>
</html>

Or, as indicated in the VCL configuration, purge all images:

# Envoyer une requête PURGEALL pour purger toutes les images dans "domain.xyz"
$ curl -X PURGEALL https://domain.xyz/images
# Réponse renvoyée par le serveur Varnish
<!DOCTYPE html>
<html>
<head>
    <title>200 Purged images</title>
</head>
<body>
    <h1>Erreur 200 : Images purgées</h1>
    <p>Toutes les images ont été purgées avec succès.</p>
    <h3>Guru Meditation:</h3>
    <p>XID: 32770</p>
    <hr>
    <p>Serveur de cache Varnish</p>
</body>
</html>

Purge from a CMS

It is a bit more difficult to illustrate this case because there are many ways to manage caching from a backend. In the configuration example above, a control on the header "Uncacheable" is added, which disables caching. With this option, any CMS could simply set this header on the response to disable caching for this request, for example.

From any PHP code and with the configuration above, you can simply send an HTTP request and use this snippet to perform a PURGE of the cache:

<?php
if ($curl = curl_init("http://127.0.0.1/some_url")) {
    curl_setopt_array($curl, [
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_CUSTOMREQUEST => "PURGE",
        CURLOPT_HTTPHEADER => [
            "Host: {$_SERVER['HTTP_HOST']}"
        ]
    ]);
    curl_exec($curl);
    if (curl_getinfo($curl, CURLINFO_HTTP_CODE) == 200) {
        echo "Cache purged!";
    }
    curl_close($curl);
}
?>

Learn more

Useful links regarding the Varnish configuration language (VCL) to control request processing, routing, caching and several other aspects:

• VCL Tutorial
• VCL user guide
• VCL Reference

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 create sorting rules to automatically categorize your incoming emails on Infomaniak based on certain conditions.

⚠ Available with:

* advanced (expert) mode unavailable

Preamble

• These rules allow the following automatic actions:
  • Delete or move messages from email addresses you no longer want to see.
  • Forward to your spouse the emails from an email address so that you both receive them.
  • Copy messages containing a specific keyword to a folder.
  • etc.
• Unlike the sorting rules offered within email software/clients (Microsoft Outlook, Mozilla Thunderbird, Apple Mail...), these rules will act directly on the server of your mailboxes before even the IMAP connection.
• You can make a template for all the addresses of your Mail Service.
• If you use an email software/client configured in POP, in parallel with Mail Infomaniak, the messages sorted into folders will no longer be downloaded by your application because the POP protocol only retrieves the messages that are in your main inbox. To view the sorted messages, it will be necessary to use the IMAP protocol or Mail only.

Access the rules from the Infomaniak Web Mail app

Prerequisites

• Permission to manage rules: if you had been invited to the Mail Infomaniak Web app (online service ksuite.infomaniak.com/mail) to manage your address, it is possible that the Mail Service manager has removed this right from their admin account.

To access the sorting filters for your Infomaniak mailbox:

1. Click here to access the Mail Infomaniak Web app (online service ksuite.infomaniak.com/mail).
2. Click on the Settings icon ‍ in the top right corner.
3. Check or select the email address concerned in the dropdown menu.
4. Click on Filters and rules:
   

Define a rule based on a received email

You can also create a rule directly from the received email:

1. Click here to access the Mail Infomaniak Web app (online service ksuite.infomaniak.com/mail).
2. Open the message from the sender concerned.
3. Click on the action menu ⋮ in the top right corner of the open message.
4. Choose Create a rule to open the creation assistant which will be pre-filled with the elements of the message:
   ‍

Access rules from the Mail Service

To access the sorting filters for your Infomaniak mailbox:

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 concerned.
3. Click on the email address concerned in the table that appears.
4. Click on the Filters and rules tab from the left sidebar:
   

Configure sorting filters & rules

Create a new rule in Standard mode

• Click on the Add a rule button in Standard mode to create a new rule using a creation assistant/form:
  
• The different conditions available for sorting filters are presented in this other guide.
• Once a filter is created, click on Continue to activate it.

Add or modify a rule in Standard mode

If there are already sorting filters, the button ‍ to add more is at the top right of the table:

These settings can be modified at any time by clicking on the pencil icon ✎ located to the right of the concerned element.

Create a new rule in Advanced (expert) mode

Read the prerequisites

• The advanced mode allows you to configure sorting rules directly from a script in Sieve language.
• It is possible to import Sieve files via the button.
• By activating this mode, the existing rules will be kept but deactivated.

First example of advanced sorting

Here is a simple example of a command using this language:

require ["fileinto"];
if address :contains "from" "facebook.com" {
    fileinto "fb";
} elsif header :matches "List-Unsubscribe" "*" {
    fileinto "nl";
} else {
    keep;
}

Explanations:

1. Loading required extensions: use require ["fileinto"]; to indicate that you will use the fileinto function.
2. Filtering Facebook messages: use if address :contains "from" "facebook.com" to check if the sender's address contains "facebook.com"; if so, the message is filed in the "fb" folder with fileinto "fb";.
3. Filtering messages with an unsubscribe link: use elsif header :matches "List-Unsubscribe" "*" to check if the "List-Unsubscribe" header is present in the message; if so, the message is filed in the "nl" folder with fileinto "nl";.
4. Keeping other messages: use else { keep; } to keep all other messages that do not match the previous criteria.

Warning:

• If you need to mention a subfolder, use the separator / (as in the second example), but it is not necessary to specify INBOX in your codes
• Make sure that the folders "fb" and "nl" already exist in your inbox; otherwise, the messages may not be sorted correctly
• The filter address :contains "from" "facebook.com" works correctly for addresses that contain "facebook.com" in the "from" field
• The filter header :matches "List-Unsubscribe" "*" checks only for the presence of the "List-Unsubscribe" header, not its content

Second example of advanced sorting

This code modifies the subject based on thesender (adds a prefix to the subject when an email passes the filter, for example):

require ["fileinto", "editheader", "variables", "regex"];
if address "sender" "owner-scientific-linux-devel at LISTSERV.FNAL.GOV" {
    if header :regex "subject" "((Re|Fwd): *)\\[SCIENTIFIC-LINUX-DEVEL\\] *(.*)" {
        deleteheader "Subject";
        addheader "Subject" "${1}${3}";
    } else {
        # Ajouter un préfixe si l'objet ne correspond pas déjà au modèle
        deleteheader "Subject";
        addheader "Subject" "[SL-Devel] ${1}";
    }
    fileinto "Mail List/SL-Devel";
}

Explanations:

1. Required extensions:
   1. fileinto: to sort messages into folders.
   2. editheader: to modify email headers.
   3. variables: to use variables in expressions.
   4. regex: for regular expressions.
2. Condition on the sender:
   1. if address "sender" "owner-scientific-linux-devel at LISTSERV.FNAL.GOV": checks if the sender matches.
3. Condition on the subject:
   1. if header :regex "subject" "((Re|Fwd): *)\\[SCIENTIFIC-LINUX-DEVEL\\] *(.*)": checks if the subject matches the specified pattern.
   2. deleteheader "Subject"; and addheader "Subject" "${1}${3}";: removes the existing subject and adds a new subject with the captured parts.
4. Adding a prefix if the subject does not already match the pattern:
   1. addheader "Subject" "[SL-Devel] ${1}";: adds a prefix "[SL-Devel]" to the subject if it is not already present.
5. Sorting the message:
   1. fileinto "Mail List/SL-Devel";: sorts messages into the "Mail List/SL-Devel" folder.

Warning:

• Make sure the folder Mail List/SL-Devel already exists in your inbox.
• Check that the script correctly modifies the subject of emails to add or adjust the prefix if necessary.

This guide allows you to quickly use the essential functions of your new Cloud Server.

Install an application

• Create a WordPress website
• Install a Web application (ownCloud, Joomla, Typo3, Drupal, phpBB, Simple Machines Forum, Magento, Prestashop, …)
• Install applications/technologies on Cloud Server (Fast Installer)

Configure the server

• Manage your MySQL databases
• Manage MySQL limits
• Manage your FTP accounts/users
• Manage and publish files on your hosting via FTP
• Modify the resources and configuration

Manage the sites and domains

If your domain name is not managed by Infomaniak or if your hosting is not managed under the same user account as your domain name, refer to this other guide to configure the DNS or records to link the domain name to your hosting. Also:

• Transfer a shared web hosting to a Cloud Server
• Add a site or subdomain to your hosting (multisite)
• Preview your site even if your domain name is not yet pointing to Infomaniak's servers

This guide details how to get started with Swiss Backup, the backup solution in an independent Swiss cloud.

2 Swiss Backup variants

Infomaniak offers two backup modes depending on what you want to back up:

 

1. CLOUD Backups

Allows you to back up and sync files via the protocols:

• Swift (recommended)
• FTP / SFTP
• S3
• Synology NAS system

with the application of your choice

Cloud Backup Getting Started Guide

2. ACRONIS Backups

Ideal solution for backing up:

• workstations Windows / macOS
• mobiles iOS / Android (iPhone / Samsung, etc.)
• Windows/Linux servers
• websites
• virtual machines VMware, Hyper-V, Virtuozzo...
• Microsoft 365 / Google Workspace spaces...

using the software Acronis Cyber Protect Cloud which will perform automatic and customized backups

Acronis Backup Start Guide

Click here to share a review or suggestion about an Infomaniak product.

This guide details the two main types of identifiers. They are distinct, even if the email address can be the same.

Infomaniak Account vs Email Address

Here is a summary of these 2 types of identifiers:

What to do in case of connection issues?

It is not necessary to contact Infomaniak Support (who does not have any of your passwords)…

• Issue with the Infomaniak account? Reset the account password.
• Issue with an email address? Test the address/password pair and, if necessary, reset the email password.

Explanations

1. As with many other online services, you registered with Infomaniak using a personal email address.
2. This personal email address serves as your login identifier when you want to access Infomaniak services.
3. This login identifier has its own password (set when your Infomaniak user account was created – your personal email address, see above).

There is no link between…

• … this identifier/password pair described in points 1/2/3 above…
• ... and the email addresses you have created or obtained subsequently from Infomaniak.

A link could exist if the address is identical (for example, you signed up with the email address toto@abc.xyz and you also manage this same email address at Infomaniak) but even in this case, the password will very likely be different — once for the login identifier toto@abc.xyz and once for the email address toto@abc.xyz.

Unified passwords?

Assume that within the Mail Service you own in your Infomaniak account, you create an email address named julie@entreprise-familiale.xyz (password 123-Abc).

If then an Infomaniak account…

• … is created with this same address (julie@entreprise-familiale.xyz – regardless of the password)…
• … is the only account to access the email address julie@entreprise-familiale.xyz via ksuite.infomaniak.com/mail…
• … has the necessary permissions to change the password of this email address…

… then the password unification will be proposed when you attempt to change the password of this email address from the relevant Infomaniak account.

Other identifiers?

Acquiring other Infomaniak products involves obtaining other identifiers, such as those required for FTP, MySQL, SSH, WebDAV connections, etc., but these identifiers are entirely independent of the two types described above.

This guide explains what you need to determine as a website visitor if you encounter a 403 error in order to resolve the issue.

What is the 403 error?

The HTTP 403 error code generally means that access to a resource is denied to the client by the server.

In which case does this error occur?

The user is not authenticated: the server requires the user to identify themselves to access the resource. This can be the case for private pages requiring authentication, for example.

The user is authenticated but does not have the necessary permissions: the server recognizes the user but does not authorize access to the requested resource due to permission or role restrictions. This cause of error 403 may be an incorrect permission issue, on a folder or a file. For a folder, the error message is of type "403 Forbidden", for a file, "failed to open stream: Permission denied". In this case, you must check that the permissions of your folders/files are correct, namely a minimum of 644 for a file and 755 for a folder. Learn more

The user's IP address is blocked or restricted: the server may block access to a specific IP address for security reasons, protection against attacks... Learn more

The requested resource does not exist on the server: in this case, the server returns a 403 error instead of a 404 error to avoid disclosing confidential information. If you are trying to access your homepage or a part of your site by entering an address of the type www.domaine.xyz or www.domaine.xyz/dossier/ make sure there is a homepage named "index.html or .htm or .php" placed in the correct location (at the root of your FTP space, in the /web directory, or in the /dossier/ directory). Learn more

Moreover, check that there are no uppercase letters in the file name, all file names or folders present must be in lowercase, without accents or spaces.

Script-related error: if you were running a script, filling out a form, or uploading a file online and you receive this type of message:

Accès interdit!
Vous n'avez pas le droit d'accéder à l'objet demandé.
Soit celui-ci est protégé, soit il ne peut être lu par le serveur.
Si vous pensez qu'il s'agit d'une erreur du serveur, veuillez contacter le gestionnaire du site.
Error 403

The cause may be a filter that prevents the unwanted use of scripts by spammers. Indeed, the Infomaniak antivirus blocks the uploading of files via scripts or via FTP. This concretely means that when a hacker sends a file identified as a virus via a form, an unsecured script or via FTP, its installation is directly blocked, the file is not uploaded to the server and the upload generates a 403 error.

In case of a false positive, contact Infomaniak support by providing the URL of the page where you encounter this error message to precisely diagnose the origin of the problem.

However, there are many other cases in which you might receive a "403 forbidden" message for various reasons (PHP scripts, Perl, mod_security, .htaccess, ...).

This guide explains how to optimize the site you manage on a Web Hosting to make it faster and allow all visitors to browse it from the Internet without difficulty, regardless of their connection speed.

The role of the hoster

1. … your hosting server is functioning normally and has not encountered any issues in the last 48 hours.
2. … the network infrastructure has not experienced any disruptions in the last 48 hours.

The role of the site owner and the webmaster

Infomaniak does not intervene in the content of the servers or the development of websites. The creation or maintenance of a site is a different job, although it is related to its activities since the tools and services that a webmaster uses to create websites are offered.

Analyzing the cause of slowdowns

Here is what you should do if you notice slowness with your site:

1. Follow the Google PageSpeed Insights recommendations to optimize your website... The points highlighted concern the design of the website and not the server configuration; refer to this other guide if the test result suggests enabling resource compression on your site.
2. In case of slowness from abroad, consider activating DNS Fast Anycast.
3. Install and configure a cache system on your site to avoid redundant access to databases and speed up the display of your site.
4. Consider a CDN.
5. Test the server's response speed (TTFB).
6. Scan your hosting for viruses.
7. Purge the databases regularly and delete unnecessary entries.
8. Use the latest PHP version compatible with your site/CMS/Web application.
9. Avoid using images, counters, CGI, or media hosted by external providers, as if they are unreachable, your site will seem slow.
10. Disable any unnecessary WordPress extensions that consume a lot of resources in your CMS.
11. Keep your CMS/Web applications up to date regularly.
12. Implement a crawl delay for indexing bots, as some have a very "aggressive" operation; it is possible to limit their impact by implementing a Crawl-delay.
13. Check the possible error-logs which group all the errors generated by your site; by correcting these errors, your site will be more performant.
14. Check the slowlogs: they group the queries that take more than 5 seconds to execute; it is important to correct the queries listed in this file (SQL optimization examples).
15. Add a server cache system like Memcached (Cloud server only).
16. Increase the max_children value (Cloud server only).

If a problem persists...

As a site owner, if you are a webmaster or have hired a webmaster who also cannot find the cause of the slowness, contact Infomaniak support in writing only after obtaining the following information:

1. Hosted site name.
2. Dates and times when slowness was encountered.
3. Name of the database potentially involved / same for FTP account.
4. Your public IP address at the time of the tests (visible for example on https://www.infomaniak.com/ip).
5. Type of slowness observed (site display, FTP transfers...).
6. Issues (such as slowness) accessing the Infomaniak site intermittently?
7. Result of a traceroute to 84.16.66.66 and copy-paste the complete results (screenshot if necessary).
8. Result of a speedtest by choosing Infomaniak as the destination (speedtest.net — click on Change Server to select Infomaniak).

If your needs skyrocket…

If shared hosting no longer suits your site, you should consider moving to a Serveur Cloud. Your site can be easily moved to this type of server where it will be alone and on which you can install a cache engine, for example.

This guide explains how to restore backups of previous versions of your files and other web data from your Infomaniak hostings, and how to set up an effective backup policy if the backups automatically and freely provided do not meet your availability or security needs.

Web Hostings (Starter, Shared, Cloud Server)

Refer to these guides to restore automatic backups:

• of an entire hosting (FTP + MySQL),
• of specific files on the hosting,
• of specific databases,
• of a Web Application (Wordpress & Apps),
• of Cloud Server SSH crons.

Refer to these guides to backup and restore:

• a hosting with Swiss Backup and Acronis (simple),
• a hosting with Swiss Backup and Restic (advanced),
• WordPress with Swiss Backup,
• WordPress with an extension.

Also refer to https://faq.infomaniak.com/snapshot.

Hostings v1 (old 60 Go offer)

• View and/or download the automatic backup (versioning) of your data on your FTP space under /backups and /backup_mysql at the root of the domain (above /web).
• Restore this data.

Mail

• Restore messages from Infomaniak automatic backups.
• Restore contacts or calendar events.
• Save the current content of a mail account:
  • by downloading the current content locally,
  • by duplicating all current content to a backup box,
  • by copying future emails as they arrive to a backup box.

Domains / DNS Zones

• Restore deleted DNS records from Infomaniak automatic backups.
• Restore an expired domain in the redemption period.

This guide details the limits of Site Creator by Infomaniak.

Site Creator Limits

Access the description of the Site Creator Free, Lite and Pro offers to compare the limits according to the offer you have.

In summary, Site Creator is available…

• … with each paid web hosting (the offer is equivalent to a Site Creator Pro without the free domain name)
• … or standalone (standalone available in 3 versions Free, Lite and Pro) and does not require any other particular offer in this case

Content

• The maximum number of pages that can be created, indicated on the sales page, includes any legal pages if you use them.
• With the Pro version, there is no limit to the number of pages or shop articles that can be added by Site Creator.
• The remaining free disk space available depending on the offer you have is specified on your dashboard:
  

FTP Management

• You cannot access the files of your site on the server side, either by FTP or by any other means than the manager proposed from the Infomaniak Manager.

Web Site Export

• It is not possible to import or export the website (to another host or other hosting for example).
• Themes or modules are not exportable (nor importable — refer to this other guide).

This guide explains why a website may be "broken" or stop displaying anything, following a password change at the level of a Web Hosting.

Broken link with the database

When your website, and more specifically a script (CMS, WordPress, Prestashop or any other application using MySQL databases), can no longer connect to the MySQL MariaDB or other database, an error message may display, such as:

• Erreur lors de la connexion à la base de données
• Database Error: Unable to connect to the database:Could not connect to MySQL
• Link to database cannot be established

Remember your last action…

In case an error occurs on your site, you should always examine the recent history. In this case, has there been…

1. … an action on your part regarding the configuration file of the script in question? Has it been altered, modified, or moved?
   
   Sometimes, the unintentional insertion of a space before or after a word can sever the connection between the web server and the database server. Go back and review your file modifications.
   If necessary, restore an older version of the files that you recently modified.
    
2. … an action regarding the database password in the Infomaniak Manager?
   
   If you change the password of your database via the Infomaniak Manager, then your script, which retrieves its information from the databases, will no longer display anything.Changing something in the Infomaniak Manager means you have to change it everywhere else. This change that you made in the Manager, you also need to report / reflect it in the configuration file of the script by connecting via FTP and going to modify the appropriate file, usually "wp-config.php", "configuration.php" or similar.
    
3. … a server move announced by Infomaniak?
   
   If this error follows a server move or another operation announced by email and related to the product in question, do not hesitate to contact Infomaniak support.

This guide allows you to quickly use the essential functions of the Streaming Radio (or broadcast audio, live audio streaming... different terms used to refer to the same technology: sending content "live" or with a slight delay allowing it to be played as it is broadcast).

Set up Radio streams

• Add a Radio Streaming feed
• Add an audio stream relay
• Add a backup audio stream
• Configure an encoder (example with the application Butt)
• Create an audio player to broadcast the stream
• Delete a stream

To go further…

• Secure an MP3/AAC or HLS stream with a unique key
• Secure an audio stream by GeoIP restriction
• View listening statistics
• Export the Streaming Radio logs via FTP
• Export the logs to ACPM (France)
• Export the logs to Mediapulse (Switzerland)
• Troubleshoot a broadcasting issue
• Transfer the complete product | Transfer streams

A question or feedback?

• If you encounter any issues, please consult the knowledge base before contacting support.
• Click here to share a review or suggestion about an Infomaniak product.

This guide explains how to obtain a backup space Swiss Backup, the backup solution in an independent Swiss cloud.

Prerequisites

• Determine which type of device will need to be backed up on Swiss Backup:
  

  1. CLOUD BACKUPS - allows you to back up and synchronize files via the protocols:

     1. Swift (recommended)
     2. FTP / SFTP
     3. S3 Compatible
     4. Synology NAS system

     with the application of your choice…

  2. ACRONIS BACKUPS - ideal solution for backing up:

     1. Windows / macOS workstations
     2. Android / iOS (iPhone) mobiles
     3. Windows / Linux servers
     4. websites
     5. VMware, Hyper-V, Virtuozzo virtual machines...
     6. Microsoft 365 / Google Workspace spaces…

     using the Acronis Cyber Protect Cloud software which allows you to store backup data using Swift in the backend and to create "protection plans" where you can choose between:

     1. full machine backup (all hard drives attached to the machine in SATA)
     2. file / folder backup (specifically of your choice)
     3. volume / disk backup (if you have external drives)
     4. backup scheduling
     5. backup retention period
     6. backup restoration
     7. backup encryption

Obtain Swiss Backup

To order a Swiss Backup backup space:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on Order:
   
   or on the shopping cart icon if a product is already active and you want to order an additional Swiss Backup:
   
3. Choose the maximum size of all the storage space needed for your project(s), regardless of the number and type of backups you will perform
   

4. Here the example project is to back up 2 things:

   1. important and voluminous documents located on 1 NAS
   2. photos/videos from an Android mobile device

   

5. Complete the order and pay.
6. The Swiss Backup product appears in your Manager with the disk space and quotas selected during the order:
     
   
    
7. You can then add the desired devices to your Swiss Backup interface: refer to this other guide.