This guide covers the configuration and management of ModSecurity on Infomaniak servers. By understanding its limitations, restrictions, and effectively managing errors, you can optimize the security of your site while maintaining its functionality.

Default configuration

ModSecurity (mod_secure) is available and enabled by default on Infomaniak servers. This means that all HTTP requests will be subject to the security rules defined by ModSecurity.

It is not possible to disable ModSecurity on Infomaniak servers. The setting is global to the server where your site is hosted, which means that all defined security rules will be applied to your site.

Error management

If the error message ModSecurity: Access denied with code 403 (phase 2). Operator EQ matched 0 at REQUEST_HEADERS. (...) appears regarding ModSecurity, you should check that a default language is correctly configured in your web browser. This error can sometimes be caused by incorrectly configured language settings in the browser.

This guide explains what a web host like Infomaniak is and specifies its role and limits of intervention.

Infomaniak, web host since 1996

According to Wikipedia, a web host is a company that provides Internet hosting for computer systems to individuals or entities who do not wish to do so by their own means.

Infomaniak is also…

• … decades of experience in hosting and online solutions
• … more than a million users in Switzerland and Europe (CHF 36.5 million in revenue in 2022)
• … company certified ISO 27001, ISO 9001, ISO 14001, ISO 50001 and committed to sustainable development
• … 100% of "Swiss made" technological know-how with data hosted in Switzerland
• … a rich knowledge base and a customer support available

Responsibilities and limits of intervention

As a host, Infomaniak installs, secures, and keeps servers up to date, updates its web interfaces (Manager) and assists its customers in using the services.

On the other hand, Infomaniak does not intervene on the content of the servers or the development of websites.

Limits of technical support

The technical support cannot help you to…

• … solve problems related to site development or its updates
• … implement solutions (migrations, complete installations)
• … manually install WordPress
• … take remote control of your computer

but can assist you for…

• … solve problems related to the infrastructure or the Manager
• … clarify certain processes

A Premium assistance and a migration service are available for more demanding needs.

Find external help

For help with the content of your site or the organization of your mailboxes, use the Infomaniak tender platform which lists over 1000 verified professionals, or consult the directory.

This guide explains how to change the PHP version used in the command line (PHP CLI) on an Infomaniak Web Hosting.

Preamble

• This guide is useful if you need to temporarily adjust settings for a specific script or for a PHP session executed in the command line (CLI).
• To modify the general PHP version used by your hosting on the web server (FPM/Apache) via the Infomaniak Manager, refer to this other guide.

Default PHP version in command line

When you run the php command (usually via /usr/bin/php), it is the default PHP version configured on the server that is used. This version may evolve over time according to the platform updates.

To find out the exact version currently active on your hosting, run:

php -v

To ensure the stability of your scripts, it is recommended to use an explicit version (php7.4, php8.0, php8.1, etc.) or to adjust your PATH variable to point to the directory of the desired version (for example /opt/php8.1/bin).

Modify the PHP version used in CLI

There are two main files that can be used to configure the PHP version automatically loaded in your SSH session:

1. Using ~/.bashrc (recommended)

The .bashrc file is read by Bash when opening an interactive shell (non-login), i.e., in the majority of cases when you open a normal SSH session or execute commands via deployment tools.

1. Create the ~/.bashrc file if it does not exist, then open it:

   touch ~/.bashrc
   nano ~/.bashrc

2. Add the following line to specify the desired PHP version (example: PHP 8.1):

   export PATH="/opt/php8.1/bin:$PATH"

3. Reload your environment:

   source ~/.bashrc

4. Check the currently used version:

   php -v
   which php

   You should see a path of the type /opt/php8.1/bin/php.

2. Using ~/.profile (alternative)

The .profile file is read only when the shell is launched in login mode (for example during an initial SSH connection). If your environment does not automatically load .bashrc, you can define the PHP version directly there.

1. Create the ~/.profile file if it does not exist, then open it:

   touch ~/.profile
   nano ~/.profile

2. Add the following line:

   export PATH="/opt/php8.1/bin:$PATH"

3. Reload your environment:

   source ~/.profile

3. Load .bashrc from other profiles

To ensure that the configuration is loaded in all types of sessions (login and non-login), it is recommended to include in your ~/.bash_profile and ~/.profile files the following line:

if [ -f ~/.bashrc ]; then . ~/.bashrc; fi

Thus, your PHP configuration defined in .bashrc will always be applied, regardless of how the SSH session is opened.

Run a specific version occasionally

If you want to run a script with a specific version of PHP without modifying your environment, you can call the corresponding binary directly:

/opt/php8.1/bin/php mon_script.php
/opt/php8.2/bin/php -v

After these steps, the chosen PHP version will be loaded automatically each time a new session is opened, and your CLI scripts will run with the desired version.

This guide concerns Redis, a PHP module for Infomaniak Cloud Server.

Preamble

• Redis is used with PHP to accelerate performance by serving as a cache for temporary data and to manage user sessions, thus improving the efficiency of web applications.
• Redis also allows the implementation of queue systems and the temporary storage of data for asynchronous tasks or statistics.

Install Redis

Redis is installed from Fast Installer, applications available in a few clicks on Cloud Server:

• After installation, Redis is accessible via the IP/port localhost:6379 or 127.0.0.1:6379
• The password for Redis must be between 15 and 99 characters (inclusive).

This guide explains how to access the configuration of an Infomaniak website to display technical information such as the PHP, Apache version, or the activated PHP extensions and modules.

View the website's technical information

To access the website management:

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 Manage button under Advanced settings:
   
4. Take note of the website information under the General, PHP / Apache and PHP Extensions tabs.
5. Click on Databases in the left sidebar to get the MySQL version of the web hosting:
   

This guide explains how to run the open source dependency manager Composer 2 using an SSH command.

Preamble

• Composer is an open source dependency manager for PHP that allows you to define, install, and update the libraries required for a PHP project.
• Composer 1 has been obsolete since 2021 and will no longer allow the installation of new packages or updates as of 2025.
• Only version 2 of Composer is now supported and available on all PHP versions from 7.2 to 8.3.

Run Composer 2

Composer 2 is already pre-installed and accessible via SSH. Therefore, it is not necessary to install it manually.

Simple usage

Log in to your hosting via SSH, then use the following command:

composer

This command will automatically run version 2 of Composer compatible with the PHP version currently in use in your session.

Check the active version

You can check the available version of Composer with:

composer --version

Example output: Composer version 2.5.0 2022-12-20 10:44:08

Force a specific PHP version

If you want to run Composer with a specific version of PHP, aliases are available. For example:

composer_php8.1 --version

or:

composer_php7.4

These aliases allow you to run Composer 2 with the specified PHP interpreter, useful for testing or deploying a project on a target PHP version.

This guide explains how to reset a VPS Cloud / VPS Lite.

Preamble

• This procedure erases all the content of the volume dedicated to the operating system (/dev/vda).
• In the case of a VPS Cloud, the volume dedicated to data storage (/dev/vdb) is not affected by the reset.
   

Reset of the VPS Cloud / VPS Lite OS

To access the VPS:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product concerned.
3. Click on the Reset button.
4. Follow the displayed instructions to complete the reset.

This guide explains how to access the VNC console with Infomaniak VPS Cloud / VPS Lite.

Preamble

• Initial access to the server is via SSH key; it is therefore necessary to assign a password to the root account or to create another user before you can authenticate with the VNC console.
• Warning: you must use the US keyboard layout to use VNC normally!

Open the VNC console

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 Open the VNC console under Quick Actions.

If a console display issue occurs, then from the VM:

In /etc/default/grub modify GRUB_CMDLINE_LINUX_DEFAULT, GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX (the latter variable is probably missing and needs to be added):

GRUB_CMDLINE_LINUX_DEFAULT="biosdevname=0 net.ifnames=0 console=tty0 console=ttyS0,115200
earlyprintk=ttyS0,115200 consoleblank=0 systemd.show_status=true video=VGA-1:1280x1024"
GRUB_GFXMODE=1280x1024x16
GRUB_GFXPAYLOAD_LINUX=keep

Then update grub and restart:

grub-mkconfig -o /boot/grub/grub.cfg

The resolution can be changed (1000x400 instead of 1280x1024 for example) to allow the VNC console to be displayed in the administration interface without opening a new tab.

This guide explains how to allow certain incoming and/or outgoing ports in the firewall (firewall) of a Web hosting or a Cloud Server.

Preamble

• On a shared Web hosting, it is only possible to open outgoing ports.
• On a Cloud Server, it is possible to open incoming and outgoing ports.
• Opening ports allows certain applications to function properly but can reduce the security of your hosting.

Access the tool and add a rule

To manage port opening from the Manager:

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 concerned.
3. Click on Security in the left sidebar.
4. Click on Port Opening in the left sidebar.
5. Click the Open a port button:
   

Open a port

It is only possible to set one port per rule, and only one IP / host per field:

By specifying an IP or a host, the connection will only be allowed in these cases:

• Incoming rule: if the connection comes from this IP or the specified host
• Outgoing rule: if the connection is made to this IP or this host

Same for the "Type" of connection, if the protocol used for the connection is not the one specified in the rule, the connection is not allowed.

Open the outgoing port 25 globally

You can open the outgoing port 25 from the manager if a destination host is specified.

With a Cloud Server, to open this port to the world, contact Infomaniak support and justify your request.

Default open ports

Once you have accessed the port opening tool, you will find the list of default open ports on the page.

With a Cloud Server, to exceptionally close some of the listed ports, contact Infomaniak support and justify your request.

The display may sometimes be spread over several pages:

MySQL ports

Regarding database ports, refer to these guides:

• Database access from another hosting
• Connect a Cloud Server to an external database

Check the activity of a port (Cloud Server)

On Cloud Server, to check if an application is listening on a particular port (1234 in the example below) and to know the name of the application in question, run in SSH:

netstat -anpe | grep "1234" | grep "LISTEN"

This guide explains how to move a shared web hosting to a Cloud Server while retrieving all its data, websites, databases, etc.

Preamble

• If you already have a Cloud Server, go directly to step 2 of this guide.
• To move a web hosting from one Cloud Server to another Cloud Server, refer to this other guide.
• To move a web hosting from a Cloud Server to a shared web hosting, refer to this other guide; note that this is a manual operation you will have to perform.
• Note:
  • Database names and database user names are preserved.
  • FTP accounts are preserved with the same names, but the host server changes to an address of type xxxx.ftp.infomaniak.com.
  • The IP addresses of the sites will change except for dedicated IPs.

1. Order a Cloud Server

To do this:

1. Click here to access the management of Cloud Servers on the Infomaniak Manager (need help?).
2. Click on Order, choose a managed Cloud Server and follow the wizard to complete the order:
   

2. Migrate the hosting to the Cloud Server

Once the Cloud Server is in service:

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. Click on Modify the offer:
   
4. Select the free transfer offer.
5. Select the Cloud Server to which to migrate your hosting:
   
6. Click on the Next button at the bottom of the page and complete the procedure entirely.
7. Wait for the hosting migration to complete, a service interruption will be felt during the process.

This guide provides information about the robots.txt file created by default for web hosting where this file is missing.

Preamble

• The robots.txt file acts as a guide for search engine crawler robots
• It is placed at the root of a website and contains specific instructions for these robots, indicating which directories or pages they are allowed to explore and which they should ignore
• However, note that robots may choose to ignore these directives, making the robots.txt a voluntary guide rather than a strict rule

File Content

If the robots.txt file is missing from an Infomaniak site, a file of the same name is automatically generated with the following directives:

User-agent: *
Crawl-delay: 10

These directives tell the robots to space out their requests by 10 seconds, which prevents unnecessarily overloading the servers.

Bypassing the Default robots.txt

It is possible to bypass the robots.txt by following these steps:

1. Create an empty robots.txt file (it will only serve as a placeholder so that the rules do not apply).
2. Manage the redirection of the URI (Uniform Resource Identifier) robots.txt to the file of your choice using a .htaccess file.

Example

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_URI} /robots.txt$
RewriteRule ^robots\.txt$ index.php [QSA,L]
</IfModule>

Explanations

• The mod_rewrite module of Apache is enabled to allow redirections.
• The condition RewriteCond %{REQUEST_URI} /robots.txt$ checks if the request concerns the robots.txt file.
• The rule RewriteRule ^robots\.txt$ index.php [QSA,L] redirects all requests to robots.txt to index.php, with the [QSA] option that preserves the query parameters.

It is recommended to place these instructions at the beginning of the .htaccess file.

This guide is about IP addresses, those…

• …assigned to sites/housing/servers, dynamic or static, shared or dedicated,
• …assigned by your Internet Service Provider (ISP) when establishing an Internet connection to your Infomaniak product.

Preamble

• A dedicated or static IP address for a website is a permanent IP address specifically assigned to it.
• Unlike a shared IP address, which is used by multiple websites, a dedicated IP address ensures that only this platform is associated with this address.
• Dedicated IP addresses for websites are often used in cases where stability, customization, and security are important, such as server hosting, firewall configuration, or activating SSL certificates (although it is possible to proceed without a dedicated IP address to install an SSL certificate).
• Here are the main advantages:
  • Configuring a PTR entry or reverse DNS on dedicated IPs is useful, especially for installing a mail server, as some email providers check the PTR record before accepting emails sent from a server.
  • Better connection stability.
  • Reduced risk of a bad reputation linked to websites sharing the same IP address.
  • Ease of configuring certain technical aspects.
  • A dedicated IP can improve a website's referencing (although there are differing opinions among SEO specialists).
• Attention: Infomaniak does not allow access to websites via HTTP(S) by IPs (dedicated) on managed servers; you must use a domain name that points to the IP (or use the preview URL).

Add a dedicated IP to the website

To add a dedicated IP to your website, refer to this guide.

If you encounter issues directing web traffic to a defined port, refer to this other guide.

Blocking the IP address (Internet connection)

If you can no longer access…

• … all your email addresses that you own with Infomaniak (which usually work well) and this with a software/email client from the same Internet network (i.e., from the same IP address provided by your ISP)…

… or if you unfortunately performed this type of operation:

• repeated unsuccessful connection attempts via FTP, SSH, or access points such as the WordPress login…
• requests returning too many errors such as mass 403 errors…

… your access to Infomaniak servers may be blocked following the banning of the IP address (banip / ipban) of your Internet connection.

To unblock the situation, contact Infomaniak support by email and specify the domain concerned and especially your public IP address concerned.

Permanent Unblocking (IP on Whitelist)

With a Cloud Server, you can request to permanently authorize the IP address in question so that the blocking never happens again, regardless of the situation. To do this, you must:

1. Have a dedicated IP associated with your Cloud Server.
2. Be aware that Infomaniak will no longer block any potential attacks from this IP; attacks or malicious access attempts from this address will no longer be automatically blocked by the security systems.
3. Confirm by email and from a contact address associated with the account (owner or administrator) that you understand and accept full responsibility in case of an attack from this IP.

This guide explains how to order, link or remove a dedicated IP from a website.

Manage dedicated IPs on a hosting plan

Order one or several first dedicated IP addresses

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 relevant product.
3. Click on Web in the left sidebar.
4. Click on Dedicated IPs in the left sidebar.
5. Click on the button to order one or more IP addresses:
   

Order one or several additional dedicated IP addresses

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 relevant product.
3. Click on Web in the left sidebar.
4. Click on Dedicated IPs in the left sidebar.
5. Click on Order :
   

Associate a dedicated IP address with a website on a hosting plan

Once the IP has been ordered and paid for, familiarize yourself with the prerequisites below, as switching to a dedicated IP address for a website may cause a temporary interruption, especially in the presence of a certificat SSL Let’s Encrypt. To limit the impact:

• Start by reducing the TTL of the DNS records A and AAAA (for @ and www) to 5 minutes.
• Wait for the previous TTL duration before making any changes.
• The change below should be made during a period of low traffic to limit the inconvenience caused by the inevitable interruption.
• At the end of the procedure, you will need to wait for the new TTL to propagate the new configuration and for the SSL certificate to be regenerated, then check the accessibility of the site in HTTPS to ensure that everything is working correctly.

To switch to a dedicated IP address:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on Web in the left sidebar.
4. Click on Dedicated IPs in the left sidebar.
5. Click on the button to dedicate the IP to a site on your hosting:
   
6. Select the site to assign the new IP address to.
7. Check the box after reviewing the warnings.
8. Click on the Associate button:
   

Remove a dedicated IP address from a website

Once the IP is installed, to uninstall it:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on Web in the left sidebar.
4. Click on Dedicated IPs in the left sidebar.
5. Click on the action menu ⋮ located to the right of the relevant item.
6. Choose Unbind:
   
7. Take note of the warnings and confirm the deletion to complete the IP uninstallation procedure.

This guide explains how to migrate a Web Hosting from MySQL to MariaDB.

Preamble

• MariaDB is an enhanced version of MySQL, featuring numerous powerful built-in features and many improvements in terms of usage, security, and performance:
  • MariaDB has a larger connection pool supporting up to 200,000 connections, whereas MySQL has a smaller connection pool.
  • When comparing the performance of MariaDB and MySQL, replication is faster in MariaDB and slower in MySQL; MariaDB is faster than MySQL overall.
  • MariaDB is Open Source, whereas MySQL uses proprietary code in its Enterprise edition.

Using MariaDB as a replacement for MySQL

To migrate a Web Hosting to MariaDB:

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 Databases in the left sidebar.
4. Click on the link Migrate to MariaDB.

To migrate a Cloud Server, refer to this other guide regarding the migration to a new generation of Cloud Server.

This guide explains how to order a Web Hosting at Infomaniak.

Order a new Infomaniak Web Hosting

To order your first Web Hosting:

1. If necessary, create a user account.
2. Click here to access the Infomaniak Manager.
3. Click on Hosting (Web & Domain universe):
   
4. Click to order a new hosting:
   
5. Once in the Shop, check that you are ordering in the desired Organization (select another from the list if necessary or create a new one at point 6 below):
   
6. Confirm your choice by clicking the blue button at the bottom of the page (or first create a new Organization if necessary using the dedicated blue link):
   
7. At the top, enter the domain name of your hosting and click Search (even if you already manage it with another registrar):
   
8. Two scenarios are then possible:
   1. You do not yet own the domain name: check the information and options on the screen, then click the Next button:
      
   2. You own and manage your domain names with another registrar: click the action menu ⋮ to the right of the domain name to Order hosting only:
      
9. Choose the hosting that suits you.
10. Click on Next.
11. Complete the order.

Already a customer, you already have a hosting

To order an additional hosting:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on the supermarket cart icon:
   

This guide explains how to update a Let's Encrypt SSL certificate for a website hosted by Infomaniak.

Preamble

• It may be necessary, following the addition or removal of aliases to a website, to regenerate a certificate to include the new domain names linked to the website.
• The dashboard will clearly indicate that one of the domains linked to the site is not included in the current SSL certificate:
  
  

Update a Let's Encrypt certificate

To access certificate management:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question:
   
3. Click on the action menu ⋮.
4. Click on Change the certificate:
   
5. Select the type of certificate to update.
6. Click on the Next button:
   
7. Check or select the relevant domains.
8. Click on the button Install:
   

This guide explains how to customize the limits of a site hosted on a Web Hosting or a Cloud Server.

Unlock or adjust the limits of a site

To access the website management:

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 Manage under Advanced settings:
   
4. Click on the PHP / Apache tab.

You can, for example...

• ... unlock for 60 minutes the memory limit (memory_limit = 1280 MB) and the maximum script execution time (max_execution_time = 60 minutes):
  
  • This unlock is possible up to 10 times per year.
• ... customize the limits of:
  • max_execution_time (in seconds)
  • memory_limit (in MB)
  • post_max_size & upload_max_filesize (maximum file size for upload, in MB)
  • Cloud Server only: Max children (see this other guide)
  • Cloud Server only: Max input time

Maximum values by hosting type

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

Preamble

• Operations in brief:
  1. We start with a site created and accessible via the main domain URL dev.domain.xyz.
  2. We add an alias domain.xyz to it.
  3. We reverse the 2 types (the main domain becomes an alias and the alias becomes the main domain).
  4. We remove the old name dev.domain.xyz.
• Note that the site's location remains in the original folder on the server; the name of this location may be of the form /sites/dev.domain.xyz but this has absolutely no impact on the production site.
• Also refer to the last chapter of this other guide.

Reverse a linked domain

Here are the detailed operations to go from a site with a subdomain type address to a direct address (here dev.domaine-exemple.ch becomes domaine-exemple.ch):

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. Then click on the chevron to expand the Domains section of this site:
4. Click on the Add a domain button:
   
5. Add the desired new name (if the domain name to be added is under the same Organization, it will be suggested in the list, otherwise enter its spelling):
   
6. Enable or disable the checkboxes:
   • If the added domain is not in the form of a subdomain, it is possible to request to automatically add the www version of the domain.
   • Automatically update (if possible) the DNS records of the added domains.
   • Automatically update the related SSL certificates (if possible).
7. Click the button to Confirm and wait:
   
8. Once the addition is complete, click on the action menu ⋮ located to the right of the domain that has just been added and that you wish to set as the main domain:
9. Choose to set the item as the main domain:
   
10. Confirm the operation to proceed with the domain reversal:
    

This guide concerns the task scheduler, a feature that allows you to run scripts on Web Hosting at the time and frequency of your choice to automate repetitive tasks.

Access the task scheduler (webcron)

To access the task scheduling tool:

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 Web in the left sidebar.
4. Click on Task Scheduler in the left sidebar:
   
5. Click on Tasks in the left sidebar.
6. Existing crons and running tasks are displayed under the 2 tabs of the page.
7. Click the Schedule a Task button to create a scheduled task by specifying, among other things, whether the URL of the script to be executed is password-protected, whether you want to receive notifications, and of course the desired interval (see below), etc.:
   
8. Do not forget to activate the task with the toggle switch:
   

Minimum intervals

In the next step, you can schedule the cron according to…

• [ a ]… predefined intervals such as once a week…
• [ b ]… or customization to a minimum interval of:
  • 15 minutes with a shared hosting
  • 1 minute on Cloud Server

Notifications & analysis

In the next step, you can activate notification emails:

The next step allows you to activate an analysis of the task:

Run the task manually 1 time

Once the task is created, click on the action menu ⋮ located to the right of the item concerned to access the quick management of your task and its execution log:

At the top of the page, you can click the button to manually run the task 1 time:

This guide explains what the “MySQL Prefix” option in a site’s settings is for and what its implications are for the operation of your Web applications (CMS) and PHP scripts.

Preamble

• When the “MySQL Prefix” option is enabled for a site, it is no longer necessary to add the prefix “wxyz_” before the name and users of your MySQL databases.
• A PHP script can thus connect to MySQL with the user “monuser” and a database “mabase” and access will be automatically made with the user “wxyz_monuser” and the database “wxyz_mabase”.
• ⚠ If you are migrating from an old Infomaniak offer:
  • After migrating a site from the old console, the “MySQL Prefix” option is enabled by default in order to automatically maintain the connection of your Web applications (WordPress, Joomla, Drupal, etc.) and PHP scripts with your MySQL databases.
  • To ensure the proper functioning of your sites in case of migration of your hosting to another server, it is strongly recommended to disable this function and make the necessary adjustments.

Manage the MySQL Prefix option

Go further with environment variables

It is possible to configure environment variables directly from the Manager for your entire website:

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 Manage under Advanced Settings:
   
4. Click on the PHP / Apache tab.
5. Enable or disable the toggle switch MySQL Prefix:
   
6. Click on the Save button at the bottom of the page.
7. Make the necessary adjustments in the configuration files of your Web applications and PHP scripts…

Implications and adjustments to be made

After disabling the MySQL Prefix option for a site, some PHP scripts or CMS may no longer work. To restore the connection to your databases, you must update the following information in the configuration file(s) of the scripts concerned:

• The name of the MySQL database: you will need to add the prefix of your server
  • before: mabase
  • after: wxyz_mabase
• The user of the MySQL database: you will need to add the prefix of your server
  • before: monuser
  • after: wxyz_monuser