This guide details the use of DELIMITER to create MySQL functions on Infomaniak Cloud Server.

Preamble

• When creating functions or stored procedures in MySQL, it is crucial to understand the role of delimiters.
• The correct use of delimiters is essential to avoid syntax errors that can occur due to the presence of multiple SQL statements in a single function or procedure definition.

Understanding the Delimiter

A delimiter is a character or sequence of characters used to separate SQL statements in a script. By default, MySQL uses the semicolon (;) as a delimiter. However, when creating functions, stored procedures, or triggers that contain multiple SQL statements, it is necessary to temporarily change the delimiter to avoid syntax errors.

When you create a function, procedure, or trigger, you often need to use multiple SQL statements within the BEGIN...END block. Since the semicolon (;) is also used to terminate these internal statements, MySQL might interpret the first semicolon as the end of the function definition, resulting in a syntax error. To work around this issue, you must change the delimiter during the function definition.

Creating a Simple Function Using Custom Delimiters

Before defining the function, you must tell MySQL that you will be using a different delimiter. In the example below, $$ is used as the new delimiter:

DELIMITER $$

With the new delimiter in place, you can now define your function. The CREATE FUNCTION includes the function body, where you can use internal SQL statements separated by semicolons without any issues:

CREATE FUNCTION hello_world()
RETURNS TEXT
LANGUAGE SQL
BEGIN
RETURN 'Hello World';
END;
$$

In this example:

• CREATE FUNCTION hello_world() : declares the start of the definition of the function hello_world.
• RETURNS TEXT : specifies the data type that the function returns.
• LANGUAGE SQL : indicates that the language used for the function is SQL.
• BEGIN ... END : encapsulates the function code. Inside, the semicolon is used to separate SQL statements.
• RETURN 'Hello World'; : SQL statement that returns the string Hello World.

After defining the function, reset the delimiter to its default state (the semicolon). This allows you to continue executing regular SQL statements in your subsequent scripts:

DELIMITER ;

This guide explains how to view file activity on your Infomaniak hosting server.

FTP space activity logs

To know the activity of exchanges on your FTP space, contact Infomaniak support to request FTP logs by first authenticating with the credentials corresponding to the management of your web hosting.

Help reading logs: http://www.castaglia.org/proftpd/doc/xferlog.html

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 Managed 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 Managed Cloud Server.
  • To increase this limit on shared hosting, migrate to Managed Cloud Server.
• To understand how to calculate the max_children needed as accurately as possible, refer to this article on the subject.

Increase the max_children value

Prerequisites

• Ensure that you have the necessary resources on the Managed Cloud Server.
• Ensure that all resources of the Managed 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 Managed Cloud Server resources).
• Monitor the resources of your server, in case the resources of your server are reached, it will be necessary to check the optimization of processes and your site before considering increasing the max_children value.
• Consult the PHP error reports from the /ik-logs folder (master process php logs - file name: php-fpm.log) to check 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 Managed 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 Managed Cloud Server:

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

Allowed and restricted

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

• between 9 AM and 5 PM CET
• from Monday to Friday
• with the minimum attack package, regardless of the software used (e.g. AppScan)
• without ever launching any DoS or DDoS attacks (Denial of Service)
• by respecting the Infomaniak Terms of Service, in particular the shared service framework

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

Prerequisites

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

Using your FTP software/client or the Web FTP, 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 through 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

• 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 Python version higher than the default one provided on your hosting.

Preamble

• Anaconda is a free and open-source distribution of the programming languages Python and R; it aims to simplify package management and deployment.
• It is recommended to use Miniconda (a lightweight version of conda); it installs in your user space, avoiding any conflict with the system Python and not requiring administrator rights.
• Refer to the official documentation.

1. Download the installer

 For example, the 64-bit Linux version for Python 3.11.

user@server:~$ wget https://repo.anaconda.com/miniconda/Miniconda3-py311_23.10.0-1-Linux-x86_64.sh
--2024-03-10 12:00:00--  https://repo.anaconda.com/miniconda/Miniconda3-py311_23.10.0-1-Linux-x86_64.sh
Resolving repo.anaconda.com... 104.16.131.3, 104.16.130.3
Connecting to repo.anaconda.com|104.16.131.3|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 72787200 (69M) [application/x-sh]
Saving to: ‘Miniconda3-py311_23.10.0-1-Linux-x86_64.sh’

Miniconda3-py311_23.10.0-1-Linux-x86_64.sh  100% [===================>]  69.42M  --.-KB/s    in 0.3s

2. Check the integrity (SHA256 Hash)

user@server:~$ sha256sum Miniconda3-py311_23.10.0-1-Linux-x86_64.sh
6c714a33ea348303f909194246990422e698889417d74b9714856b3e9a7e6c3a  Miniconda3-py311_23.10.0-1-Linux-x86_64.sh

3. Run the installation

The -b argument allows for a silent installation. By default, Miniconda will install in ~/miniconda3.

user@server:~$ bash Miniconda3-py311_23.10.0-1-Linux-x86_64.sh -b
PREFIX=/home/clients/your_client_hash/miniconda3
Unpacking payload ...
Collecting package metadata (current_repodata.json): done
Solving environment: done
Executing transaction: done
installation finished.

4. Initialize and activate Conda

To use conda immediately and with each SSH connection:

user@server:~$ ~/miniconda3/bin/conda init bash
no change     /home/clients/your_client_hash/miniconda3/condabin/conda
...
modified      /home/clients/your_client_hash/.bashrc

user@server:~$ source ~/.bashrc

5. Install a package (example: pymysql)

Once activated, the (base) prefix appears before your command prompt. You can then install your tools without sudo or --user.

(base) user@server:~$ python -V
Python 3.11.5

(base) user@server:~$ pip install pymysql
Collecting pymysql
  Downloading PyMySQL-1.1.0-py3-none-any.whl (44 kB)
Installing collected packages: pymysql
Successfully installed pymysql-1.1.0

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.

Introduction

• A snapshot is like a picture of your Cloud VPS at a specific point in time, containing everything on your server, including your operating system, applications, data, etc.
• Snapshots can be used, in particular, to…
  • … 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 changes without risk: before making significant changes to your Cloud VPS, you can create a snapshot so that you can revert if necessary.
• You benefit from one free snapshot to back up your entire server in a dedicated space; if needed, it is possible to order additional space or delete a snapshot to create a new one.
• Two types of backup are possible:
  1. Snapshot of the data: allows you to create an image of the volume that contains your data (not available for Windows distributions).
  2. Snapshot of the operating system: allows you to create an image of the volume that contains your operating system. This type of backup involves a brief interruption of a few minutes for your applications and websites.
• It is recommended to create snapshots regularly, for example once a week or once a 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 Cloud VPS to its previous state using the snapshot created earlier.

Create a snapshot

To do this:

1. Click here to access the management of your product in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Snapshot in the left-hand menu.
4. Click on the blue Create a snapshot button:
   
5. Choose the type of snapshot to create (data or operating system).
6. Click on 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 in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Snapshot in the left-hand menu.
4. Click on the action menu ⋮ to the right of the item in question 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-hand menu.
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 currently in progress.

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

Preamble

• The IPv4 address is usually 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 details the specifics related to managing MongoDB on your Managed Cloud Server, particularly regarding the version lifecycle.

Preamble

• Any new installation of the application deploys MongoDB version 7.0 (or higher) by default.

Upgrading from version 6 to 7

It is not possible to perform an automatic update (upgrade) from version 6 to version 7 directly from your interface.

Two solutions are available to you:

1. Order a new Cloud Server: it will natively have version 7, and you can then migrate your data to it.
2. Reinstall the application: uninstall and then reinstall MongoDB on the current server.

Backups and responsibility

As an administrator, the management and integrity of your data are entirely your responsibility.

Before any manipulation (especially reinstallation):

• Perform your own backups and exports (dump) of your databases.
• Plan for the manual import of your data once the new version is active.

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

What is a 403 error?

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

When does this error occur?

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

The user is authenticated but does not have the necessary permissions: the server recognizes the user but does not allow them to access the requested resource due to permission or role restrictions. This cause of the 403 error may be due to incorrect permissions on a folder or file. For a folder, the error message is of the type "403 Forbidden", for a file, "failed to open stream: Permission denied". In this case, you should check that the permissions for your folders/files are correct, i.e., at least 644 for a file and 755 for a folder. See 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, to protect against attacks, etc. See 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 prevent the disclosure of confidential information. If you are trying to access your homepage or a part of your site by entering an address like www.domain.xyz or www.domain.xyz/folder/, make sure that there is indeed a homepage named "index.html, .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.

Also, check that there are no uppercase letters in the file name; all file and folder names 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 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 file uploads via scripts or via FTP. This 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 the event of a false positive, contact Infomaniak support, providing the URL of the page where you are encountering this error message, in order to accurately diagnose the cause of the problem.

However, there are many other cases in which you may receive a "403 forbidden" message for a variety of reasons (PHP, perl scripts, mod_security, .htaccess, ...).

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

Introduction

• 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 causing encoding issues with non-European characters and emojis in your developments.

Define the default MySQL / MariaDB charset (Cloud Server)

With an Infomaniak Cloud Server, it is possible to define 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 in question.
3. Click on MariaDB in the left-hand menu.
4. Choose the default character set:
   
   • 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 (e.g., latin1)

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.

For current offers, place the following code in a user.ini file located in the root directory 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");

For older hosting plans, force the MySQL connection to use latin1 via the .htaccess file located in the root directory of your hosting:

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

This guide explains how to access automatic backups and restore a specific file from a website on an Infomaniak hosting.

Restore specific files or folders

To do this:

1. Access the FTP server via Web FTP (need help?).
2. Go to the /backups folder.
3. Select the files and/or folders to restore.
4. Click the Copy button:
   
5. Select the location to which to copy/restore the data (existing data will be replaced by the selected data).

This guide concerns MySQL/MariaDB and, more specifically, index and query analysis 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-structured, you will never see these files. Otherwise, check them regularly to correct any issues and ensure your site functions properly.

Contact Infomaniak support in writing to obtain them (except for older v1 hosting plans - old formula), which can be directly accessed from the Web FTP, one level above /web in the /logs directory.

What about logs?

No MySQL log is created (apart from slowlogs) because the MySQL servers could not handle the load of millions of logs being recorded simultaneously. If needed, Infomaniak can activate this MySQL log for 5 minutes to allow you to analyze it with EXPLAIN and determine useful indexes, for example. To do this, contact Infomaniak support in writing.

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

This guide explains how to completely cancel a VPS Cloud / VPS Lite.

Preamble

• For most products, confirm the cancellation request by email otherwise no data will be deleted.
• Outstanding and out-of-package fees remain due.
• A cancellation confirmation is sent to any other administrators of the Organization.
• Backups will be irrevocably deleted upon cancellation, making any restoration impossible.

Cancel a server

To access the cancellation of products:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on the action menu ⋮ located to the right of the item concerned.
3. Choose Cancel:
   
4. Follow the procedure to the end.

This guide details the Infomaniak Managed Cloud Server offer and the Infomaniak VPS offer 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 exceed 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 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 load increases, 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 for MySQL / MariaDB on a Managed Cloud Server. These settings allow you to adjust the behavior, performance, and certain features of the service, including resource limits.

Introduction

• MySQL is installed on a Dedicated Managed 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 Parameters

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

Modify MySQL / MariaDB parameters

To modify your instance configuration:

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

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

Preamble

• Some applications also allow changing the 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 access the administration panel of your web application, perform the following actions:

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 the action menu ⋮ located to the right of the Web Application concerned.
4. Click on Settings of the application:
   
5. Click on Modify to the right of the Application:
   
6. Under Password enter the new password (for the connection with the identifier indicated above).
7. Click on the Save button at the bottom of the page: