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

If necessary, you should consider changing your plan to a Cloud Server if you are currently on a shared web hosting plan. This can be done transparently: refer to this other guide on the subject.

This guide explains how to increase the max_children value on Cloud Server to increase the number of simultaneous PHP processes that can be used by your site. This will be very useful for resolving infinite page loading issues on your site.

Preamble

• By default on all hosting, the max_children limit is set to 20.
  • Although it is possible to increase this value from the Infomaniak Manager, the max_children limit is automatically adjusted based on the configuration of your Cloud Server.
  • To increase this limit on shared hosting, migrate to Cloud Server.
• To understand how to accurately calculate the necessary max_children, refer to this article on the subject.

Increase the max_children value

Prerequisites

• Ensure that you have the necessary resources on the Cloud Server.
• Ensure that all resources of the Cloud Server are not being used; if it turns out that they are fully used, increasing the max_children value will have no effect (Modify the resources of the Cloud Server).
• Monitor the resources of your server, in case the resources of your server are reached, it will be necessary to check the optimization of the processes and your site before considering increasing the value max_children.
• Consult the PHP error reports from the /ik-logs folder (master process php logs - file name: php-fpm.log) to verify if the "max_children" limit has been exceeded... example of error: [05-Jul-2024 09:08:58] WARNING: [pool www.infomaniak.ch] server reached max_children setting (20), consider raising it

To access the management of PHP / Apache parameters of the site for which you need to increase the max_children value on Cloud Server, refer to this other guide.

You will be able to...

• … choose a new max_children value:
  

Limits depending on the server

Limit of max_children depending on the resources of the Cloud Server:

This guide is for you if you wish to perform vulnerability tests on your site / server hosted by Infomaniak.

Tolerated and restricted

You are free to perform vulnerability tests (SQL injection, XSS, etc.), intrusion, or penetration testing (pentest) on your Infomaniak hosting only under the following conditions:

• ... between 9 AM and 5 PM CET
• ... from Monday to Friday
• ... with the minimum number of attack packets regardless of the software used (AppScan for example)
• ... without ever performing a single DoS or DDoS (Denial of Service) attack
• ... by respecting the Infomaniak Terms of Service, in particular the shared framework of the services

This guide details the use of Perl or Python scripts on Infomaniak hosting and the management of their modules.

Preamble

To run Python or Perl scripts via Apache on a Cloud Server, the interpretation of files with the extensions .py and .pl is not active by default.

Using your FTP software/client or the FTP Manager, add and adapt the following directive in the .htaccess file located in the folder containing your scripts:

AddHandler cgi-script .pl .cgi .py
Options +ExecCGI

Installation of additional modules

On a Cloud Server, you have the possibility to install third-party libraries that are not present by default.

Python

• The installation is done via PIP, which is a package manager used to install and manage packages written in Python.
• Infomaniak offers PIP and PIP3 via the Fast Installer tool.
• Once PIP is installed, you will be able to install Python modules by specifying --user during the command. For example:

• pip3 install mysql-connector-python --user

Perl

• The addition of Perl modules is also done via SSH (console). It is necessary to install them in the user directory and to define the full path within the scripts.

Important technical information

• Path of the interpreter (Path): /usr/bin/python
• Extensions: Scripts must have the extension .pl, .cgi or .py.
• Limitations: The mod_python module is not supported.

Error Resolution (CGIWrap)

If you encounter the following error when loading an image:

CGIWrap Error: Execution of this script not permitted
Request Data:Extra Path Info: /dossier/.../image.PL.12.34.gif

The server interprets the file as a script because it contains ".PL" (or .PY) in its name.
Solution: Simply rename the file to remove this mention (example: image-12-34.gif).

This guide will help you if, for example, you want to deploy a package like pymysql and it requires a version of python higher than the one offered on your hosting.

Preamble

• Anaconda is a free and open-source distribution of the Python programming language. This distribution aims to simplify package management and deployment.
• It is recommended to use conda delivered with a recent version of python and that installs in the user space, so that there is no conflict with the python system (as in a virtual environment, which always requires a system installation of the desired version).
• Refer to the official documentation.
• For additional help contact a partner or launch a free tender — also discover the role of the host.

Download the installer

uid165116@od-12345:~$ wget https://repo.anaconda.com/miniconda/Miniconda3-py37_4.10.3-Linux-x86_64.sh
--2021-07-28 18:21:10--  https://repo.anaconda.com/miniconda/Miniconda3-py37_4.10.3-Linux-x86_64.sh
Resolving repo.anaconda.com (repo.anaconda.com)... 2606:4700::6810:8303, 2606:4700::6810:8203, 104.16.131.3, ...
Connecting to repo.anaconda.com (repo.anaconda.com)|2606:4700::6810:8303|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 89026327 (85M) [application/x-sh]
Saving to: ‘Miniconda3-py37_4.10.3-Linux-x86_64.sh’

Miniconda3-py37_4.10.3-Linux-x86_64.sh          100% [==============================================>]  84.90M   203MB/s   in 0.4s   

18:21:11 (100 MB/s) - ‘Miniconda3-py37_4.10.3-Linux-x86_64.sh’ saved [89026327/89026327]

Check the hash

uid165116@od-12345:~$ test $(md5sum Miniconda3-py37_4.10.3-Linux-x86_64.sh | awk '{print $1}') == "9f186c1d86c266acc47dbc1603f0e2ed" && echo "OK" 
OK

Start the installation

uid165116@od-12345:~$ bash Miniconda3-py37_4.10.3-Linux-x86_64.sh -b
PREFIX=/home/clients/fc84cbbf6dcbd6dd76b15d3e56c1789f/miniconda3
Unpacking payload ...
Collecting package metadata (current_repodata.json): done                                                                                           
Solving environment: done

## Package Plan ##

environment location: /home/clients/fc84cbbf6dcbd6dd76b15d3e56c1789f/miniconda3

added / updated specs:
    - _libgcc_mutex==0.1=main
    - _openmp_mutex==4.5=1_gnu
    - brotlipy==0.7.0=py37h27cfd23_1003
    - ca-certificates==2021.7.5=h06a4308_1
    - certifi==2021.5.30=py37h06a4308_0
    - cffi==1.14.6=py37h400218f_0
    - chardet==4.0.0=py37h06a4308_1003
    - conda-package-handling==1.7.3=py37h27cfd23_1
    - conda==4.10.3=py37h06a4308_0
    - cryptography==3.4.7=py37hd23ed53_0
    - idna==2.10=pyhd3eb1b0_0
    - ld_impl_linux-64==2.35.1=h7274673_9
    - libffi==3.3=he6710b0_2
    - libgcc-ng==9.3.0=h5101ec6_17
    - libgomp==9.3.0=h5101ec6_17
    - libstdcxx-ng==9.3.0=hd4cf53a_17
    - ncurses==6.2=he6710b0_1
    - openssl==1.1.1k=h27cfd23_0
    - pip==21.1.3=py37h06a4308_0
    - pycosat==0.6.3=py37h27cfd23_0
    - pycparser==2.20=py_2
    - pyopenssl==20.0.1=pyhd3eb1b0_1
    - pysocks==1.7.1=py37_1
    - python==3.7.10=h12debd9_4
    - readline==8.1=h27cfd23_0
    - requests==2.25.1=pyhd3eb1b0_0
    - ruamel_yaml==0.15.100=py37h27cfd23_0
    - setuptools==52.0.0=py37h06a4308_0
    - six==1.16.0=pyhd3eb1b0_0
    - sqlite==3.36.0=hc218d9a_0
    - tk==8.6.10=hbc83047_0
    - tqdm==4.61.2=pyhd3eb1b0_1
    - urllib3==1.26.6=pyhd3eb1b0_1
    - wheel==0.36.2=pyhd3eb1b0_0
    - xz==5.2.5=h7b6447c_0
    - yaml==0.2.5=h7b6447c_0
    - zlib==1.2.11=h7b6447c_3

The following NEW packages will be INSTALLED:

  _libgcc_mutex      pkgs/main/linux-64::_libgcc_mutex-0.1-main
  _openmp_mutex      pkgs/main/linux-64::_openmp_mutex-4.5-1_gnu
  brotlipy           pkgs/main/linux-64::brotlipy-0.7.0-py37h27cfd23_1003
  ca-certificates    pkgs/main/linux-64::ca-certificates-2021.7.5-h06a4308_1
  certifi            pkgs/main/linux-64::certifi-2021.5.30-py37h06a4308_0
  cffi               pkgs/main/linux-64::cffi-1.14.6-py37h400218f_0
  chardet            pkgs/main/linux-64::chardet-4.0.0-py37h06a4308_1003
  conda              pkgs/main/linux-64::conda-4.10.3-py37h06a4308_0
  conda-package-han~ pkgs/main/linux-64::conda-package-handling-1.7.3-py37h27cfd23_1
  cryptography       pkgs/main/linux-64::cryptography-3.4.7-py37hd23ed53_0
  idna               pkgs/main/noarch::idna-2.10-pyhd3eb1b0_0
  ld_impl_linux-64   pkgs/main/linux-64::ld_impl_linux-64-2.35.1-h7274673_9
  libffi             pkgs/main/linux-64::libffi-3.3-he6710b0_2
  libgcc-ng          pkgs/main/linux-64::libgcc-ng-9.3.0-h5101ec6_17
  libgomp            pkgs/main/linux-64::libgomp-9.3.0-h5101ec6_17
  libstdcxx-ng       pkgs/main/linux-64::libstdcxx-ng-9.3.0-hd4cf53a_17
  ncurses            pkgs/main/linux-64::ncurses-6.2-he6710b0_1
  openssl            pkgs/main/linux-64::openssl-1.1.1k-h27cfd23_0
  pip                pkgs/main/linux-64::pip-21.1.3-py37h06a4308_0
  pycosat            pkgs/main/linux-64::pycosat-0.6.3-py37h27cfd23_0
  pycparser          pkgs/main/noarch::pycparser-2.20-py_2
  pyopenssl          pkgs/main/noarch::pyopenssl-20.0.1-pyhd3eb1b0_1
  pysocks            pkgs/main/linux-64::pysocks-1.7.1-py37_1
  python             pkgs/main/linux-64::python-3.7.10-h12debd9_4
  readline           pkgs/main/linux-64::readline-8.1-h27cfd23_0
  requests           pkgs/main/noarch::requests-2.25.1-pyhd3eb1b0_0
  ruamel_yaml        pkgs/main/linux-64::ruamel_yaml-0.15.100-py37h27cfd23_0
  setuptools         pkgs/main/linux-64::setuptools-52.0.0-py37h06a4308_0
  six                pkgs/main/noarch::six-1.16.0-pyhd3eb1b0_0
  sqlite             pkgs/main/linux-64::sqlite-3.36.0-hc218d9a_0
  tk                 pkgs/main/linux-64::tk-8.6.10-hbc83047_0
  tqdm               pkgs/main/noarch::tqdm-4.61.2-pyhd3eb1b0_1
  urllib3            pkgs/main/noarch::urllib3-1.26.6-pyhd3eb1b0_1
  wheel              pkgs/main/noarch::wheel-0.36.2-pyhd3eb1b0_0
  xz                 pkgs/main/linux-64::xz-5.2.5-h7b6447c_0
  yaml               pkgs/main/linux-64::yaml-0.2.5-h7b6447c_0
  zlib               pkgs/main/linux-64::zlib-1.2.11-h7b6447c_3

Preparing transaction: done
Executing transaction: done
installation finished.

Launch conda

uid165116@od-12345:~$ source <(~/miniconda3/bin/conda shell.bash hook)

Install pymysql (for example)

(base) uid165116@od-12345:~$ python3 -V
Python 3.7.10

(base) uid165116@od-12345:~$ pip3 install pymysql --user
Collecting pymysql
  Downloading PyMySQL-1.0.2-py3-none-any.whl (43 kB)
     |████████████████████████████████| 43 kB 892 kB/s 
Installing collected packages: pymysql
Successfully installed pymysql-1.0.2

This guide covers the support of secure hash functions (including SHA-256) by Infomaniak servers, as well as the emphasis on the security of SSL/TLS certificates using CSRs generated with SHA-256.

SHA-256 hashing algorithm

The cryptographic hash function SHA-1 is compatible and Infomaniak servers also support the SHA-256 function, which is useful for PayPal and SaferPay (SIX).

The CSRs (certificate signing requests) are in SHA-256 and not in SHA-1.

This guide explains how to back up a Cloud VPS in the form of a snapshot.

Preamble

• A snapshot is like a photo of your Cloud VPS at a given moment, containing everything on your server, including your operating system, your applications, your data, etc.
• Snapshots can be used, among other things, for…
  • … protect your Cloud VPS in case of a problem: if you encounter a problem with your Cloud VPS, you can restore a snapshot to return to a previous state.
  • … test modifications without risk: before making significant changes to your Cloud VPS, you can create a snapshot to be able to revert if necessary.
• You benefit from a free snapshot to back up your entire server in a dedicated space. If necessary, it is possible to order additional spaces or delete a snapshot to create a new one.
• Two types of backups are possible:
  1. Snapshot of data: allows you to create an image of the volume containing your data (not available for Windows distributions).
  2. Snapshot of the operating system: allows you to create an image of the volume containing your operating system. This type of backup involves a brief interruption of your applications and websites.
• It is recommended to create snapshots regularly, e.g., once a week or month; this will allow you to have a history of your Cloud VPS and to be able to revert in case of a problem.
• It is obviously possible to restore the state of the Cloud VPS thanks to the previously created snapshot.

Create a snapshot

To do this:

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 Snapshot in the left sidebar.
4. Click the blue button Create a snapshot:
   
5. Choose the type of snapshot to create (data or operating system).
6. Click the blue button to start creating the snapshot:
   
7. An email is sent when the snapshot is generated.

Delete a snapshot

To do this:

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 Snapshot in the left sidebar.
4. Click on the action menu ⋮ to the right of the object concerned in the table that appears.
5. Click on Delete:
   

Order additional snapshots

To do this:

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 Snapshot in the left sidebar.
4. Click on the shopping cart icon:
   
5. Follow the instructions to complete the order.

It is not possible to order an additional snapshot if a snapshot is in progress.

This guide explains how to display the IP address of a site on your Web Hosting.

Preamble

• The IPv4 address is generally the same for each of the sites on the hosting (unless you have acquired a dedicated IP).

Display the IP address of your site

The IP address is specified on the hosting management page (Starter or containing multiple sites):

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 product concerned.
3. Then click on the chevron to expand the Information section of this hosting.
4. The IPv4 address is displayed on the page:
   
5. The IPv6 address is also displayed in the case of paid hosting:
   

This guide details the "502 Bad Gateway" errors that can be encountered when visiting a website.

Preamble

• The 502 Bad Gateway error occurs when the server acting as a gateway between the browser and the origin web server receives an invalid response.
• This error can be caused by an overloaded web server, communication issues between a CDN and the hosting web server, or a misconfigured proxy server.
• Sometimes, the error can be caused by a bad entry in the DNS server.

Troubleshooting steps

To resolve the 502 Bad Gateway error, you often need to proceed by elimination:

• Check if the server is temporarily overloaded: simply reload the page after a few minutes for the error to disappear.
• Clear the browser cache.
• Try from another browser.

This guide explains what you need to determine as a website visitor if you encounter a 403 error to resolve this 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 what 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 them to access the requested resource due to permission or role restrictions. This cause of 403 error may be an incorrect permission issue on a folder or 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 verify that the permissions of your folders/files are correct, i.e., a minimum of 644 for a file and 755 for a folder. Refer to this other guide.

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... Refer to this other guide.

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 simply trying to access your homepage or a part of your site by indicating an address of type www.domain.xyz or www.domain.xyz/folder/ 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 /folder/ directory). Refer to this other guide.

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

Script-related error: if you were running a script, filling out a form, uploading a file online, and you get 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 insecure 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 and for very diverse reasons (PHP, perl, mod_security, .htaccess scripts, ...).

This guide helps resolve issues with special characters (accents, emojis, etc.) that do not display correctly or appear as symbols like ??, often due to incorrect encoding when connecting to MySQL.

Preamble

• By default, MySQL uses UTF-8.
• Recent MySQL servers are generally configured to use UTF-8 or UTF-8MB4 by default.
  • This is suitable for most cases, especially for international languages and emojis.
• Also, refer to this other guide to learn how to avoid encoding issues with non-European characters and emojis in your developments.

Set the default MySQL / MariaDB charset (Cloud Server)

With an Infomaniak Cloud Server, you can set the default charset (utf8 or utf8mb4):

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 MariaDB in the left sidebar.
4. Choose the default charset:
   
   • If you have not yet migrated to MariaDB, the principle is the same.
5. Save your changes at the bottom of the page.

Force a specific encoding (latin1 for example)

If you need to work with a database in latin1 (ISO-8859-1), you must explicitly align the encoding when connecting, depending on your environment.

On current offers, place the following code in a user.ini file located at the root of your hosting:

mysql.connect_charset = "latin1"
mysqli.connect_charset = "latin1"
pdo_mysql.connect_charset = "latin1"

or in PHP (MySQL API):

mysql_query("SET CHARACTER SET latin1");

On older hosting plans, force the MySQL connection to latin1 via the .htaccess file located at the root of your hosting:

php_value mysql.connect_charset latin1
php_value mysqli.connect_charset latin1
php_value pdo_mysql.connect_charset latin1

This guide concerns MySQL/MariaDB and more specifically index analyses and queries with Web Hosting.

Slowlog for long queries

The MySQL slowlog is enabled on all MySQL servers and groups queries that take more than 5 seconds* to execute. If your queries are well constructed, you will never see these files. Otherwise, check regularly to correct any potential issues and ensure the proper functioning of your site.

Contact Infomaniak support in writing to obtain them (except for old v1 hosting directly viewable from the FTP Manager file manager one level above /web in the /logs directory).

And the logs?

No MySQL log is created (except for slowlogs) as MySQL servers would not support the load of millions of simultaneous logs to record. If necessary, Infomaniak can enable this MySQL log for 5 minutes to allow you to analyze them with EXPLAIN and determine useful indexes, for example. To do this, contact Infomaniak support in writing.

* elapsed time. And regarding locks, the documentation provides the following clarification: "The time to acquire the initial locks is not counted as execution time"

This guide details the Managed Cloud Server offer from Infomaniak and the VPS offer from Infomaniak, 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 provides 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 order. 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. Combined 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 need to 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.

This guide explains how to view and modify the configuration settings MySQL / MariaDB of a Cloud Server. These settings allow you to adjust the behavior, performance, and some features of the service, including resource limits.

Preamble

• MySQL is installed on a Dedicated Cloud Server: resources are not shared with other customers.
• Only one instance of MySQL or MariaDB is present per Cloud Server.
• The number and size of databases depend solely on the available disk space and resources.
• For very large volumes of non-relational data, MongoDB is recommended.

Configurable MySQL / MariaDB settings

The following list presents the main variables that you can customize in your MySQL / MariaDB instance:

Modify MySQL / MariaDB parameters

To modify the configuration of your instance:

1. Click here to access the management of your product in the Infomaniak Manager (need help?).
2. Select the name of the Cloud Server concerned.
3. Click on MySQL / MariaDB in the sidebar menu.
4. Edit the desired parameters and then validate your changes.

This guide explains how to change the WordPress management password or any other Web application (Joomla, Drupal, Typo3, PrestaShop, ownCloud, etc.) installed via Infomaniak tools included in the offersWeb hosting paid.

Preamble

• Some applications also allow a change of user password directly from their dedicated interface:
  • Example: WordPress (manage users, names, passwords, roles, etc.).

Change the password of a Web app

To change the password to the administration panel of your web application, perform the following actions:

1. Click here in order to access the management of your product on the Manager Infomaniak (Need help?).
2. Click directly on the nameallocated to the product concerned:
   
3. Click on the action menu ⋮ located to the right of the relevant Web Application.
4. Click on Parameters of the application:
   
5. Click on Edit to the right of the Application:
   
6. Under Password Enter the new password (for connection to the identifier indicated above):
   
7. Click on the button Save at the bottom of the page.

The user and the process "cloud base - ini" are used as part of the VPS Cloud / VPS Lite infrastructure of Infomaniak (in the case, for example, where the instance is rebuilt). Learn more

This guide explains how to view and download Apache logs from Web Hosting, which are useful for analyzing PHP errors or diagnosing certain application behaviors.

Preamble

• The access and error logs are kept for at least 7 days.
• Once the retention period has expired, older entries cannot be restored, even upon request.
• You can also find these files directly on the server via SSH/FTP in the ik-logs folder at the root of your hosting.

Accessing access and error logs

To display these logs:

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 Advanced in the left sidebar.
4. Click on Logs in the left sidebar.
5. Click on Errors or Access to display the error log or access log.
6. Choose a period if necessary.
7. Click on the icon to view the details.
8. Click on Send by email to receive all entries immediately by email to your user address.
9. Click to export the data in .log format:
   

Identify the most active IP addresses in the access logs

To do this, connect to the server via SSH (need help?).

The line to execute in SSH is as follows:

cat ik-logs/access.log | awk '{ print $2}' | sort -n | uniq -c | sort -n | tail -n 20

This guide lists the supported operating systems (Linux distributions) that can be installed when ordering a VPS Cloud / VPS Lite.

Prerequisites

• Create a password for your user after logging in for the first time with the private key, especially to troubleshoot your server by connecting via the VNC console in case of a problem.

Natively supported Linux distributions
 

Debian

If you come from the Debian community, then a server of this type would be an excellent choice, an alternative to CentOS offered below. The Debian editions are very stable, especially since "Buster" or more recently "Bookworm" (Debian 12). Learn more

Ubuntu

If you are familiar with Ubuntu desktop version, you might want to have it on your server. Learn more

FreeBSD

The base code of FreeBSD has been developed, improved, and optimized continuously for over thirty years. It is developed and maintained by a large team of people. FreeBSD offers advanced network features, enhanced security, and high performance. Learn more

openSUSE

This distribution is ideal for beginners, experienced users, and ultra-geeks, in short, it is suitable for everyone! Learn more

CentOS

CentOS is the most popular distribution for a web server and therefore has great support, whether on the community forum or anywhere on the web. CentOS editions are very stable in the long term. Learn more

Other Linux distributions

Infomaniak regularly adds new Linux distributions:

• Fedora
• rancherOS
• ArchLinux
• AlmaLinux
• RockyLinux

Specific distribution / disk image

Only official images can be installed and Infomaniak does not install any operating system from an ISO disk image. If you wish to install a specific distribution, you can do so by importing the image to Public Cloud.

This guide explains how to connect via SSH to a Web Hosting or a Cloud Server.

Connect via SSH…

… via a web browser

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 FTP / SSH in the left sidebar menu.
4. Click on the Web SSH button:
   

… via the terminal or an application

To connect via SSH, use the following commands from a Terminal type application (command line interface, CLI / Command Line Interface) on your device, for example:

• Terminal (application already integrated with macOS and Linux)
• PuTTY (Windows)
• Windows 10 SSH client (help in French / in English)

Then enter the following command:

ssh username@server

• username being the username of the FTP account
• server being the host server (e.g. xxxx.ftp.infomaniak.com)

To know which command is available and know the path to use, run the command "whereis":

$ whereis mysql
mysql: /opt/mysql/bin/mysql

This guide explains how to add a new domain name to a Web site Infomaniak.

Preamble

• When you add a new domain name to a Web site, it is referred to as a linked domain but also as an alias.
• In this case, an alias domain is an additional domain name, also linked to an existing site.
  • For the Web site domain.xyz to be reachable with a completely different domain name such as private.abc for example, you need to add private.abc as an alias to the Web site.
  • Second example, for the site domain.xyz to also be reachable with www.domain.xyz, you need to add it as an alias to the domain domain.xyz. In this example, domain.xyz is the parent site of the alias www.domain.xyz. Generally, the alias www is already added automatically and present…

Adding an alias to an existing site

Prerequisites

• If the domain name (intended to become an alias) or its DNS zone is managed by Infomaniak, everything is OK. If not:
  • The A record of the domain name must point to Infomaniak.
  • To simplify, you can delegate the management of the domain to Infomaniak.
• It is also necessary that the future alias is not already one, in which case it will be necessary to detach it from the current site beforehand (same if synonym).

To add an additional domain that will be linked to your Web site:

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. Then click on the chevron ‍ to expand the Domains section of this site.
4. Click on the Add a domain button:
   
5. Enter the domain name(s) to be added, separated by the Enter.
6. If the alias or its DNS zone is managed by Infomaniak, it is possible to automatically update the DNS entries. Otherwise, make any necessary changes with your registrar or transfer the management of the domain name to Infomaniak.
7. If you have an SSL certificate like Let's Encrypt, for example, you can request to update it here to include the new names.
8. Click on Validate to complete the procedure:
   

To set the alias as the main domain, refer to this other guide.