This guide details how to create a GIT repository on both your Web Hosting and your Cloud Server with Infomaniak.

Introduction

• GIT and GitHub are available by default on both of the aforementioned platforms.

Creating the GIT repository

Setup on the server:

• The GIT repository is located at /git_depot
• The website is located in the /web/[project] folder (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 be done on the local machine:

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

Cloning the website to the server directory

To be done on the server:

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

You are directed to this page because you have a web redirection on your domain that is misconfigured. Infomaniak is unable to identify the correct path of this redirection, so you are redirected to this page to help you correct this situation.

DNS zone verification

To restore the functionality of your redirection, you must first remove traces of an old misconfigured redirection:

1. Access your DNS zone.
2. Delete the relevant records (see the list below) that correspond to your redirection.
3. Click on the ⋮ icon to the right of the DNS entry and select Delete:
   
   • You probably won't find all the records listed, that's perfectly normal.
   • Any addition/modification can take up to 48 hours to propagate.
4. Recreate the web redirection.

List of records to check and delete

DNS records can be of type:

• A and pointing to xx.xx.xx.xx (only digits)
• AAAA and pointing to an IP xxxx:xxxx:x:x::x (digits and letters)
• TXT whose string resembles “(number)|(URL)”
  • for example 1|infomaniak.com if your redirection points to infomaniak.com
• TXT whose string resembles “(letter)|(text)”
  • for example t|Text, d|Text or k|Text

This guide details the open ports available for Node.js sites (only) hosted by Infomaniak.

Outbound open ports

Web

• HTTP (tcp/80)
• Alternative HTTP (tcp/8080)
• HTTPS (tcp/443)
• FTP Data (tcp/20)
• FTP Control (tcp/21)

Mail

• POP3 (tcp/110)
• IMAP (tcp/143)
• SMTP submission (+ STARTTLS) (tcp/587)
• SMTPS (tcp/465)
• IMAPS (tcp/993)
• POP3S (tcp/995)

DB

• MySQL (tcp/3306)
• MongoDB (tcp/27017)
• PostgreSQL (tcp/5432)
• Redis (tcp/6379)
• Redis TLS (tcp/6380)
• ElasticSearch (tcp/9200)

Misc

• SSH (tcp/22)
• Git pack transfer (tcp/9418)

Inbound open ports

• HTTP (tcp/80)
• HTTPS (tcp/443)
• SSH (tcp/22)

This guide explains how to resolve an issue with the installation of an SSL certificate (Let's Encrypt or Sectigo) if you are using Cloudflare with strict security rules, such as country or IP address filtering.

Adjust SSL / geoblocking settings

When an SSL certificate is requested via Infomaniak (free Let's Encrypt or Sectigo), the certificate authority must verify that you are the owner of the domain. This verification can be done via HTTP (using special files placed on your website), DNS, or email:

• Let's Encrypt uses /.well-known/acme-challenge/.
• Sectigo generally uses /.well-known/pki-validation/ (or DNS / email, depending on the option chosen).

If these checks fail (for example, because Cloudflare blocks access), the certificate cannot be issued or renewed. However, Let's Encrypt no longer verifies only from a single location. For some time now (and even more so since March 2024), it performs its checks from several countries simultaneously – including new ones such as Sweden or Singapore. As a result, if one of these countries is blocked by your Cloudflare settings, the certificate request may fail, even if everything else is configured correctly.

Even worse: even if you try to create an exception specifically for the challenge address (.well-known/acme-challenge), it may not work with certain Cloudflare rules. Indeed, blocking rules based on country or IP address are applied before any exception based on URL paths.

Adjust the SSL/TLS mode

In Cloudflare, use Full or Full (strict) mode. These modes temporarily tolerate an expired or self-signed certificate while validation is in progress:

Allow validation paths

Avoid restrictive "IP Access Rules" and instead use "Custom Rules" that allow unrestricted access to the following paths:

• /.well-known/acme-challenge/ (Let's Encrypt)
• /.well-known/pki-validation/ (Sectigo)

Temporarily disable geoblocking

If necessary, temporarily disable geographic or IP blocking during the validation process, then re-enable your security measures after the certificate is issued or renewed.

Infomaniak offers various Site Creator plans, both free and paid, to meet different needs. It is essential to understand the terms and conditions associated with each type of plan before making your choice.

Understanding the Different Site Creator Plans

Site Creator is available…

• … either free of charge with every existing paid web hosting plan (add one if necessary):
  
  • In this case, only 1 Site Creator can be set up per Infomaniak web hosting plan.
  • To manage multiple sites created with Site Creator within the same Organization, it is therefore necessary to have multiple web hosting plans.
• … orindependently (standalone available in 3 versions)and in this case, does not require any other specific offer:
  
  1. Site Creator Free
  2. Site Creator Lite
  3. Site Creator Pro

1. Site Creator Free

This offer is designed as a trial and discovery solution and is completely free. It is intended for users who want to familiarize themselves with the tool or publish a very simple web page:

• It only allows one web page and offers limited disk space (5 GB).
• This offer does not allow connection to a custom domain name (it will be in the format *.infomaniak.site) and includes the mandatory display of Infomaniak's advertising message.
• Important growth modules, such as full blog management, the use of Artificial Intelligence for text generation, or the "Sitemap" function, are not included.

2. Site Creator Lite

The Lite plan is Infomaniak's entry-level paid plan. It is ideal for creating a simple showcase website or personal blog, as it eliminates the main limitations of the free version and unlocks the modules needed for a complete website:

• It allows you to create a more comprehensive website with a limit of 6 web pages and more storage space (15 GB).
• It includes a domain name for one year and, most importantly, removes all Infomaniak advertising from the website.
• Unlike the Free plan, the Lite plan unlocks access to important features for navigation and organization, including the Blog Creation and Management module and the Sitemap module.

3. Site Creator Pro

The Pro plan is the premium plan for Site Creator. It is exclusively designed for the most ambitious projects, such as launching a complete online store, by removing all content restrictions and integrating advanced e-commerce and analytics tools:

• It removes all limitations on content by offering unlimited web pages and a large disk space of 50 GB.
• This is the only plan that includes complete e-commerce management (orders, inventory, discounts) and allows integration of essential payment gateways (Stripe, PayPal, Mollie) for an online business.
• The Pro plan is the only one that provides access to crucial external analysis and performance tracking tools, such as Google Analytics, Hotjar, and tools like Google reCaptcha.

Commitment related to paid offers

Unlike other Infomaniak products, some Site Creator offers include a free domain name. These offers require a firm commitment for a minimum period of 12 months, with no possibility of a refund, even partial, even if:

• you decide to stop using Site Creator before the end of the first year,
• you cancel your products,
• you close your user account or your Organization.

Changes to offers and maintaining your site

You can upgrade from a free plan to a more comprehensive paid plan:

1. Click here to access your website management in the Infomaniak Manager (need help?).
2. Click on the action menu ⋮ to the right of the website in question in the table that appears.
3. Click on Modify offer:
   

It is also possible to upgrade to a higher plan (e.g., from Lite to Pro).

If you want to keep your site active, you must renew the same paid plan. It is not possible to switch to a free version of Site Creator, even if:

• you are not using any of the paid modules,
• your website only has one page.

What should you do if you want to revert to the free plan?

In this case, you must:

• cancel your current site after manually copying all the information you want to keep,
• activate a new free Site Creator offer,
• recreate your site by pasting the content retrieved from the old one.

This guide details the installation and maintenance of Ghost on an Infomaniak Web Hosting, to obtain a platform optimized for blogging and editorial publishing, a powerful alternative to Substack or Medium.

Prerequisites

• A Node.js type site (v22 recommended).
• An active SSH access.
• A MySQL/MariaDB database.
• Stop the Node.js application from the dashboard of your Node.js site before any technical operation.

Installation of Ghost

To do this:

1. Connect to your server via SSH (need help?).

2. Run the following commands to start the installer:

   # Clone tools repo
   git clone https://github.com/Infomaniak/hosting-tools.git
   cd hosting-tools/h3-ghost
   # Run installation script
   bash ./install.sh

3. The script will now:
   • ask you a few questions (site URL, database information, SMTP, etc.)…
   • download and configure Ghost automatically…
   • take a few minutes — be patient!

Answer the questions carefully using the details you have noted. Do not close the terminal until it has finished!

Configuration of the Manager (Node.js)

Once the script is complete, go to your Infomaniak Control Panel:

1. Click here to access the management of your site on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the site concerned:
   
3. Click on Manage advanced settings:
   
4. Click on the Node.js tab to access the settings.

5. In the execution command field, enter:

   /srv/customer/node_modules/ghost-cli/bin/ghost run

6. Check that the port number is 3000.
7. Command case build : disable it.
8. Click on the Save button at the bottom of the page:
   
9. On the main page, click on the Start button (or Restart if already running).
10. Confirm the operation if necessary:
    
11. Observe the logs showing the creation of the database and the startup of the application.

Updating Ghost

To update Ghost CMS to the latest version or a specific version, follow these steps:

1. Stop the Node.js application in the Infomaniak Manager.

2. Access the directory of your Ghost site

   # Navigate to your Ghost site directory
   cd ~/sites/ghost-site-name

   Replace ghost-site-name with the actual name of your folder (e.g., blog, mysite, etc.).

3. Ensure that the file permissions are correct (the operation may take several minutes):

   # Ensure file permissions are correct
   find ./ -type d -exec chmod -v 00775 {} \;

4. Check for available updates:

   # Check available ghost updates
   /srv/customer/node_modules/ghost-cli/bin/ghost check-update

   For the latest version (the operation may take several minutes):

   # Update to the latest version
   /srv/customer/node_modules/ghost-cli/bin/ghost update

   For a specific version such as v5 (the operation may take several minutes):

   # Update to a specific version (e.g., v5)
   /srv/customer/node_modules/ghost-cli/bin/ghost update v5

   • Why go through v5? If you are using Ghost v4 and want to upgrade to v6, Ghost requires going through v5 as an intermediate step. This is essential for major version upgrades.
5. Wait until the update is complete, then restart the application from the site dashboard to apply the update.

Done! Access your Ghost blog

Go to the URL of your site to get started:

1. Open your browser and go to https://domain.xyz/ghost (replace domain.xyz with your current domain).
2. The first time:
   1. You will create an administrator account (your login for the blog)…
   2. Then, you can start writing articles!

User / mail configuration

To create the first user, add /ghost to the URL of your site (for example https://ghost.domain.xyz/ghost) and follow the assistant.

You can also configure the "member portal support address": when new members want to register, the portal sends the double opt-in confirmation from a specific address.

By default, this is the “noreply” address of your domain. To update it, navigate to “Settings”, “Membership”, “Portal Settings”, “Customize”, and “Account Page”:

Resolve a technical incompatibility between Ghost and MariaDB

Some SQL queries cause HTTP 400 errors on MariaDB, resulting in this type of error:

[2025-01-01 12:54:28] ERROR "GET /ghost/api/admin/posts/6834625e35802b06f1496305/?formats=mobiledoc%2Clexical&include=tags%2Cauthors%2Cauthors.roles%2Cemail%2Ctiers%2Cnewsletter%2Ccount.conversions%2Ccount.clicks%2Csentiment%2Ccount.positive_feedback%2Ccount.negative_feedback" 400 27ms
Could not understand request.
Error ID:
8f2b0d90-3a30-11f0-a25f-fd9c83e1cf02
Error Code:
ER_BAD_FIELD_ERROR
----------------------------------------
Error: select `posts`.*,
...

If necessary, a patch exists to adapt Ghost's behavior.

To use this patch, enter this command:

# Enter the current version folder and apply the MariaDB patch
cd current
curl -L https://gist.githubusercontent.com/reneluria/8cbbfbc001e542c77d6d5887fbafe5d3/raw/65e0ce31753b4687d0eb67fc030734a35d3ffbad/ghost-post.patch | patch -p0

This guide helps you troubleshoot an issue with the CMS Prestashop, specifically with its “Faceted search” module, which manages filters on product category pages.

The problem

This specific Prestashop search module creates a database cache to speed up searches, however, the corresponding table is never cleared, which poses a problem for the hosting infrastructure.

First solution

The first solution is to disable the caching feature.

To do this:

1. In the PrestaShop administration panel, go to Modules → Module Manager.
2. Select Modules and use the search field to find “facet”.
3. Click on Configure next to the module found:
   
4. Disable this button:
   

Second solution

The second solution is to set up a cron job to clean the table, for example, every evening:

1. From the module settings, copy the existing URL from the Clear cache button:
   

Then, from the Infomaniak Manager, create a webcron (refer to this other guide for more information) to execute the URL copied in step 1 above, for example once a day and at night.

This guide concerns the Drupal module "Infomaniak_Connect" which allows users to log in to your Drupal site (whether it is hosted by Infomaniak or not) using their Infomaniak credentials.

Introduction

• Allowing login via an Infomaniak account on your Drupal site enables your visitors to comment, register for courses, or access any content reserved for members with a single click, without having to create a new account.
• This saves them time and provides a more secure method for you, as you don't have to manage additional passwords.
• This external module functions identically to the "Log in with Google", "Log in with Facebook", or “Log in with Apple” options; it uses the standard OAuth2 and OpenID Connect protocols to enable single sign-on (SSO).

A. Create an application with Auth Infomaniak

To do this:

1. Click here to access the management of your Auth product on the Infomaniak Manager (need help?).
2. Click the button to Create a new application:
   
3. Choose the “Web Front-End” type.
4. Give your application a name.
5. In the URL field, enter the domain name corresponding to your Drupal site followed by /openid-connect-authorize (refer to the GitHub documentation if needed).
6. Click the button to complete the app creation:
   
7. Carefully note the 2 pieces of information obtained when finalizing your OAuth2 application:
   

B. Configure the Drupal extension

Via SSH, deploy Composer if necessary to retrieve the openid_connect and infomaniak_connect extensions. To do this:

• You may need to edit the composer.json file because the version of openid_connect is not yet considered stable. Add:

• "minimum-stability": "dev",
  "prefer-stable": true

• The SSH commands for installing the 2 extensions are available here:
  • https://www.drupal.org/project/openid_connect
  • https://www.drupal.org/project/infomaniak_connect

Next, in Drupal:

1. Find the Infomaniak module among your pre-installed modules.
2. Select it.
3. Click on the Install button:
   
4. The dependencies will now be installed:
   
5. Under Configuration, click to configure the OpenID connection:
   
6. Click the edit button:
   
7. The only fields to fill in are Client ID and Client Secret, and these come from the information obtained in step A above:
   
8. Don't forget to save the changes made to the extension settings.
9. In the Settings tab, you can choose the display type for your login page; remember to save:
   
10. An additional button, for logging in with your Infomaniak credentials, is now visible on your login page for users:
     

This guide explains why it is important to use a recent version of Node.js for your application and how to select a more recent version with a Node.js site hosted on the Infomaniak infrastructure.

Preamble

• Node.js = official name of the language/environment.
• NodeJS = "technical" or simplified name in certain contexts (often for practical reasons, no real technical difference).

Is an outdated version of Node.js dangerous?

When you use a version of Node.js that is approaching the end of its support, a warning message appears in the dashboard of the affected site.

The Node.js runtime is regularly updated: each new version brings performance, security improvements, and support for recent features. Using a version that is no longer maintained exposes you to security risks and operational issues with other components. Malicious individuals could exploit known vulnerabilities in these versions to compromise your application. It is therefore strongly recommended to use a recent and officially supported version.

Three situations are possible:

• Fully supported version: no action required
• Version with security support only: it is recommended to switch to a more recent version
• Outdated version: it is strongly recommended to update to a more recent version

Using a more recent version of Node.js

The most recent versions of Node.js offer better performance and more stable behavior for your modern applications.

Before modifying the version used

• If your application uses a specific framework or library (Next.js, Express, etc.), check the proper support of the targeted version of Node.js.
• If your code was custom-developed, consult the official Node.js documentation to identify the changes made (deprecated APIs, module management, etc.).

What if a problem occurs?

If your application does not work correctly after changing the version of Node.js, you can revert to a previous version (if it is still supported) via the Advanced settings tab of the affected site.

This guide explains how to adjust the configuration of a Node.js site hosted on the Infomaniak infrastructure. You will learn how to adapt the behavior of your application according to its evolution, its dependencies, or your technical preferences.

Prerequisites

• Install a Node.js site on your hosting.
• Test your changes locally before applying them to production.
• Check that your scripts (start, build) are properly defined in your package.json file.
• If you modify the structure of your project, remember to adjust the execution folder and the associated commands.
• Important: the listening port defined in the Manager must match the one used in the application code.

Access the configuration

Each site has a dedicated dashboard to control the application (start, stop, restart), view the execution logs, manage Node.js versions, and activate SSL certificates:

1. Click here to access the management of your site on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the site in question:
   
3. Click on Manage advanced settings:
   
4. Click on the Node.js tab to access the settings:
   

Commands and automation

Execution folder

The execution folder indicates the location on the server where the build and launch commands will be executed. It must point to the root directory of your application, where your package.json file is located.

./          // Root directory
./app       // Subfolder named app
./backend   // Subfolder named backend

Build command

If your application requires a preparation step (installing dependencies, compiling TypeScript, minification), specify the command to execute here. This is the recommended method for deploying your updates.

Unlike manual execution via SSH, this interface uses an environment with boosted performance to ensure fast building without impacting the resources of your production site. You can chain multiple tasks (such as a git pull followed by a build) and monitor the progress and logs of the process in real-time directly from the Manager.

# Example: install dependencies and build
npm install && npm run build

# Example: update code and build with yarn
git pull && yarn install && yarn build

Note: If your project is already compiled or requires no intermediate steps, this field can be left empty.

Start command

This instruction starts your server. It must be identical to the one used in your local development environment to launch the application's entry point.

# Option 1: Direct file launch
node index.js

# Option 2: Using npm script
npm start

# Option 3: Using yarn script
yarn start

Listening port

Your application must listen on the dynamic port assigned by the Manager. This port is passed to your code via the PORT environment variable.

// Use the port provided by the environment
const port = process.env.PORT || 8080;

app.listen(port, () => {
  console.log(`Application started on port ${port}`);
});

Node.js version

You can select the desired Node.js version in the settings. It is recommended to prioritize a stable version (LTS) to ensure the security and longevity of your project.

Apply and validate changes

Once your modifications are saved in the Manager, you must restart your application from the dashboard for the new parameters (new Node version, new port, or new build command) to take effect.

If you encounter startup issues, you can check the execution console or refer to this other guide for troubleshooting.

This guide helps you quickly diagnose the cause of a problem if your Node.js site, hosted on Infomaniak infrastructure, is not working as expected.

Check the application status

From the dashboard of your Node.js site, you can view the current status of the application:

• Active : your application is running normally.
• Restarting : the application is restarting, please wait a few moments.
• Stopped or In error : there is a problem.

In case of an error or a stop:

• Click on "Start" or "Restart" the application.
• Immediately check the execution console to identify any technical errors.

Read the execution console

The console displays error messages generated when launching your application. Here are the common errors:

• Incorrect launch command : check that you are using the correct syntax (example: npm start, node app.js, etc.).
• Error in the source code : this could be an unhandled exception, a missing module, or an incorrectly defined port.

Check the application settings

In the Advanced Settings section of the site, make sure all settings are correct:

• Execution folder : folder in which the build and start commands are launched.
• Build command (optional) : for example npm run build if your app requires one.
• Launch command : for example node index.js, npm start, etc.
• Listening port : the port on which the application waits for requests (for example 8080, 3000, etc.).
  • The port configured in your application must match the one defined in the Manager.
• Node.js version : make sure it is compatible with your code.

Infomaniak provides the NPM and Yarn package managers. You can choose the one that suits your project in the configuration assistant.

Still stuck?

Is the site still inaccessible?

• Your application may be in maintenance mode.
• The application's listening port may be incorrect or blocked.
• The application does not return a correct HTTP response (e.g., no res.send() or res.end() in your server).

Did you use an advanced installation method?

If you have imported your code via Git, ZIP, SSH, or SFTP, make sure that:

• The code has been correctly decompressed or cloned into the right folder.
• The essential files (package.json, server.js, index.js, etc.) are present.
• The dependencies are correctly installed (node_modules present after npm install or yarn install).

If the problem persists after all these checks:

• Try creating a new site using the simple method to test with a working example.
• Compare your configuration with the provided example.
• Refer to the official Node.js documentation for specific errors.
• If needed, contact Infomaniak support with a copy of the logs displayed in the console.

Infomaniak's Node.js hosting plans allow you to run Node.js applications in a flexible, ready-to-use environment, without having to manage server infrastructure.

Introduction

• Offering the flexibility of a server without the complexity of its administration, this type of hosting is particularly suitable for API REST projects, for deploying the CMS Ghost, n8n, Strapi, or frameworks like Express.js, NestJS, or even socket.io, next.js, business tools, or prototypes for:
  • developers who want to deploy Node.js applications without managing infrastructure.
  • webmasters looking to experiment with or learn Node.js.
  • agencies and freelancers working on multiple client projects.
  • students, teachers, and schools needing a simple environment to test code.
• The NPM and Yarn package managers are supported.
• If you install Node.js on a web hosting plan within a Cloud Server, your site will not work with the guaranteed resources of the managed Cloud Server.
  • Refer to this other guide to use Fast Installer and deploy NVM.
• Node.js = official name of the language/environment; NodeJS = "technical" or simplified name in some contexts (often for practical reasons, no real technical difference).

Create a Node.js site

To access a web hosting plan and add a Node.js site:

1. Click here to access the management of your web hosting in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the web hosting in question:
   
3. Click on the blue Add button:
   
4. Choose a project with advanced technologies.
5. Click on Next:
   
6. Choose Node.js.
7. Select any other version if necessary.
8. Click on Next:
   
9. Choose the domain type to assign to this new site:
   1. a domain name already acquired
   2. a subdomain created from a domain name already acquired
   3. a domain name that is still available and to be ordered
10. Enter the domain name or subdomain.
11. Choose any possible advanced options.
12. Click on Next:
    
13. Choose one of the two possible approaches:
    
    1. Quick method:
       • A preconfigured sample project is automatically installed.
       • This approach is ideal for discovering Node.js or quickly starting a functional base.
    2. Custom method:
       • The source code can be imported via ZIP archive, SSH, or SFTP.
       • You can also choose to use public repositories hosted on GitLab, GitHub, or any other platform compatible with Git.
       • Private repositories are also supported using HTTP Basic authentication: https://username:password@github.com/…
       • You define the scripts, entry points, listening port, and build commands yourself.
14. That's it, the site is ready:
    

Each site has a dedicated dashboard to control the application (start, stop, restart), view the execution console, manage Node.js versions, configure domains, and activate SSL certificates:

To go further in the configuration of your Node.js site, refer to this other guide.

This guide explains how to import external data (files, folders, etc.) to your kDrive using the WebDAV protocol provided by your Cloud host.

Preamble

• Refer to this other guide if you are looking for information on how to copy specific data from one kDrive to another when your user has access to both kDrives concerned.

Import external data via WebDAV

Prerequisites

• Have a kDrive or kSuite offer
• Have sufficient permissions within kDrive or kSuite.
• Do not change your passwords until the import is complete!

To access the import tool, where the data needs to be imported:

1. Click here to access the Infomaniak kDrive Web app (online service ksuite.infomaniak.com/kdrive).
2. Click on the Settings icon in the top right corner.
3. Check or select the kDrive concerned in the dropdown menu of the left sidebar.
4. Click on General in the left sidebar.
5. Click on Import external data:
   
6. Click the blue Start button:
   
7. Click on WebDAV.
8. Complete the requested information based on the source (including the WebDAV address you have - obtained from the source).
9. Choose the destination kDrive and the desired location to host the imported data.
10. Click on Start:
    

This guide details the specific rules to follow when creating a user password with mysqli_connect() that contains the “dollar” character $ on Infomaniak platforms.

Preamble

• If, when using mysqli_connect(), you get the error message "Access denied for user" and your database user password contains a $ sign, the problem may be due to the functioning of strings in PHP.
• The problem can also occur with messaging scripts.

Rules to follow

When the special character $ is used in a user password and is followed by any character other than a number, the variable name is not valid and the substitution does not occur correctly.

Here are solutions to fix this:

• Place the password in single quotes: '$******'
• Ensure a number directly follows the dollar: "$2*****"
• Use a backslash to "escape" the dollar in the password: "\$****"

This guide explains the differences between a Domain (or main website), a Subdomain, and an Alias.

Introduction

• Although they are related, these three elements (Domain, Subdomain, and Alias) have different functions and purposes.
• They can impact a Web Hosting service via its domain name, or even the email service, as it is perfectly possible to have email addresses on a subdomain, for example.

What is a Domain?

A domain or domain name is the main entry point to your website. It is through this domain that your users will access your content. This main domain defines what will appear in the URL bar of your users' browsers.

Prerequisites

• You must own a domain.
• Have an Infomaniak web hosting plan.

Refer to the guide Create a new website on your web hosting.

What is a Subdomain?

A Subdomain is represented by an additional word that appears before your main domain name. This is very useful in several cases, for example:

• this can be used to display "exclusive" or targeted content, for example, by going to faq.infomaniak.com, you will access the knowledge base where all the guides are located.
• it can also be used (temporarily or permanently) when creating a new website or redesigning an existing one, for example by creating new.domain.xyz when the main website was previously domain.xyz.

Prerequisites

• You must own at least one domain.
• Have an Infomaniak Web Hosting plan.

Refer to the guide Add a subdomain to your Web Hosting.

What is an Alias?

An Alias or Domain Alias is a second domain name that points directly to your main website; whether accessed through the linked domain or the main domain, they share the same web pages. The alias is another access point to your website. For example, the main website of the Swiss Confederation is www.ch.ch and www.suisse.ch is its alias.

Prerequisites

• You must own several domain names.
• Have an Infomaniak web hosting plan.

Refer to the guide Add an alias to your web hosting.

The equivalent also exists for a Mail Service.

The benefit of an Alias is that it allows you to increase the visibility of your site among your target audience by providing them with more ways to access it.

This guide details the ranges of public IP addresses used by Infomaniak; this notably facilitates the configuration of security systems (firewall, filtering, whitelisting).

Preamble

• The addresses are indicated in CIDR format (example: 192.0.2.0/24), which groups several consecutive addresses.
• The format of the listing includes the IP ranges (ranges) used by the following products:
  • kuite: all kSuite products
  • vps: all VPS
  • public-cloud: all Public Cloud
  • all: covers all IP addresses in the Infomaniak network

IPv4 & IPv6 address ranges

The link to the JSON file listing the IPs is:

https://prefixes.infomaniak.com/json

This guide explains how to create and manage an OAuth2/OpenID Connect (OIDC) application to allow a third-party application to use your Infomaniak login ID to authenticate users and, with their permission, access the resources provided by the granted authorizations (scopes).

Introduction

• An OAuth2 application is used, in particular, to implement a single sign-on (Single Sign-On) mechanism or to allow software to access certain data without having to transmit the account password.

Manage Infomaniak OAuth2 Applications

To create a new OAuth2 application:

1. Click here to access the management of your OAuth2 applications in the Infomaniak Manager (need help?).
2. Click on the blue Create a new application button:
   
3. Choose the application type that corresponds to your project. This choice determines, in particular, the OAuth2 authentication flow used.
4. Give the application a name so you can easily identify it in the Manager.
5. Enter the application's URL according to its technical configuration (e.g., its public URL or its redirect URL, depending on the type of application).
6. Click on the button to create the application:
   
7. Keep the Client ID and Client secret in a safe place.
   • These credentials allow your application to authenticate with Infomaniak services.
   • For security reasons, the Client secret is only displayed once when it is created:
     
   • However, you can renew the secret phrase from the main page.

This guide explains how to delete a website from a Web Hosting account.

Introduction

• Once removed, the website will no longer be accessible on the internet at its previous URL.
• The number of websites allowed on your hosting plan will be increased by one.

Remove a website from a paid Web Hosting plan

To access the Web Hosting plans and remove a website:

1. Click here to access the management of your hosting on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the hosting in question:
   
3. Click on the action menu ⋮ to the right of the website in question in the table that appears.
4. Click on Remove website:
   

Unlinking a website from a free Starter hosting plan

A Starter hosting plan (basic webpage) contains only one website, which is specific to the domain name itself. Therefore, unlike paid plans, it is not possible to manage multiple websites or remove one website to add another.

You must therefore cancel the Starter hosting plan directly:

• This will cancel only your Starter web hosting product, i.e., the part concerning your website, without affecting other products such as email or domain name.
• You must confirm the cancellation request by email; otherwise, no data will be deleted.
• A cancellation confirmation is sent to any other administrators of the Organization.
• Backups will be permanently deleted upon cancellation, making any restoration impossible.

To cancel:

1. Click here to access your hosting management in the Infomaniak Manager (need help?).
2. Click on the action menu ⋮ located to the right of the hosting in question.
3. Select the Cancel option:
   
4. Follow the procedure until the end.

This guide explains how to add IP addresses to the whitelist of an Infomaniak website.

Preamble

• Allowing IPs on xmlrpc.php allows access to URLs that are blocked by default, as they are considered risky.
• This type of blocking is effective on all recent servers.
• Regarding WordPress, its XML-RPC feature is only available by default via Infomaniak services and JetPack for security reasons.

Add IP addresses to the xmlrpc.php whitelist

To access website management:

1. Click here to access your site management on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the site concerned:
   
3. Click on Manage advanced settings:
   
4. Click on the PHP / Apache tab:
   
5. Complete the relevant line.
6. Click on the Save button at the bottom of the page:
   

This guide introduces Groups, a user management system for your Organization, available on the Infomaniak Manager.

Preamble

• To facilitate access and the addition of a collaborator within the Infomaniak ecosystem, the Groups feature allows you to create teams of users and grant them access to the services they need with just a few clicks.
• Some examples:
  • You create a Group for a new department: immediately associate its mailboxes, its kDrive organization folders, and its dedicated kChat discussion channels; each new collaborator added to the team will automatically receive all these accesses.
  • You are a web agency and you want to give your webmaster teams access to all your web hostings: simply create a new group, choose all the hostings they will need access to, and invite them to join the Group.
  • You own a kDrive: authorize access to a folder for a Group and adjust the access based on users added to or removed from the team over time.
  • You use Streaming or Ticketing services and want to give your teams access: create a new Group that will have access to these two products or two separate Groups that will have access to the two products completely independently.
• It is entirely possible:
  • to associate resources (Mail, kDrive, kChat) upon creation of the Group to automate onboarding,
  • to adjust individual access levels: for kDrive, individual access takes precedence over Group access, while for Mail, access levels are cumulative.
  • to add the same user to multiple Groups,
  • to invite external users to your Organization to one of your Groups,
  • to add one or more users to a Group at once,
  • to designate a team leader to easily identify a project manager or the point of contact.

Manage your Groups

Group management now allows for complete centralization. No need to intervene in each tool separately: everything is controlled from the Infomaniak Manager for a smooth reorganization of your collaborators. Learn about the guides on this topic:

• Create a Group
• Modify a Group
• Delete a Group