Knowledge base

This guide details the restrictions on the number of simultaneous connections allowed on MySQL databases for Web Hosting.

Simultaneous MySQL Connection Thresholds

To maintain server stability, security, and responsiveness for all users, the system enforces limits on simultaneous connections.

This quota prevents the saturation of shared resources. If this threshold is exceeded, access is temporarily blocked, and errors such as User has already more than 'max_user_connections' active connections or Too many connections may appear.

In practice, this threshold is rarely reached. If necessary, it is entirely possible to distribute the load by creating distinct MySQL users for the various scripts or services of your site.

No hourly connection quota

Infomaniak imposes no restrictions on the volume of queries per hour. Parameters such as MAX_QUERIES_PER_HOUR or MAX_CONNECTIONS_PER_HOUR are not enabled.

Unlike some competing offers, you will not encounter resource exhaustion errors of type SQL Error : 1226 related to hourly activity volume.

Learn more

• Adjust MySQL Limits (Cloud Server)
• Manage site configuration limits

This technical guide details the resource limits on Infomaniak's Web Hosting services; it is essential to distinguish between real time (clock) and processing time (CPU) to understand the origin of script interruptions.

1. MySQL Connection Time (I/O)

Limit: 30 real seconds

This limit corresponds to the absolute time elapsed "clock in hand." It concerns the communication between PHP and the database server (MySQL/MariaDB).

As soon as a connection is opened, the database server allocates a maximum of 30 seconds to receive the request, execute it, and return the results. If this deadline is exceeded (often due to a poorly optimized SQL query), the MySQL server abruptly cuts the connection. This usually generates the error MySQL server has gone away.

2. PHP Processing Time (CPU)

Limit: 10 CPU seconds

This limit exclusively concerns the computing power consumed by the web server to execute the PHP code.

It is crucial to note that waiting time does not count. When PHP waits for a response from the database, it is paused and consumes virtually no CPU time. Therefore, a script will be interrupted by the web server only if it performs intensive calculations (complex loops, cryptography, file processing) for more than 10 cumulative seconds.

Interaction of the two limits

To ensure the stability of the application, each operation must simultaneously respect these two distinct constraints:

• The application has 30 seconds of total time to interact with the database (network latency + SQL execution).
• The application has 10 seconds of pure computing time to process the received data.

Example of valid operation: a script that waits 25 seconds for a complex response from MySQL (I/O) and then processes the result for 2 seconds (CPU) will work perfectly, as it has not exceeded either of the two individual quotas, even if the total time is 27 seconds.

This guide explains how to redirect traffic from an alias (synonym) domain name to your main domain, or force the display of the main domain in the browser's address bar.

Prevent duplicate content

Let's imagine that your website is hosted under the main domain example.com and that you have configured an alias domain such as example-alias.com.

By default, when a visitor enters one or the other of these addresses in their browser, the typed URL remains displayed. This can generate duplicate content, which harms natural search engine optimization (SEO).

To prevent this, you can force a redirect: if a visitor types example-alias.com, they will be automatically redirected to example.com.

This configuration is done in the .htaccess file located at the root of your hosting (usually in the /web folder via your FTP access). If this file does not yet exist, you must create it.

Then, insert the following directives into the file:

RewriteEngine On

# Force HTTPS and canonical domain redirection
RewriteCond %{HTTP:X-Forwarded-Proto} !https [OR]
RewriteCond %{HTTP_HOST} !^example\.com$ [NC]
RewriteRule ^(.*)$ https://example.com/$1 [R=301,L]

Adapt the code above to your needs:

• Replace example.com with your main domain name and its extension (.com, .org, .ch, etc.). Add www. before your domain if you prefer to force the display of the www subdomain.
• If a redirection loop occurs, you can replace the protocol condition with RewriteCond %{HTTPS} off (especially if your hosting does not use a reverse proxy).

For more information, see the documentation on automatic redirects to HTTPS.

This guide concerns the synchronization of servers via the NTP (Network Time Protocol) and the configuration of the timezone on Infomaniak servers.

Precise server synchronization via NTP

Infomaniak servers are all synchronized via the NTP protocol. The company provides its own public-accessible stratum-1 NTP servers for flexible use.

To integrate these servers into your settings, use the following entry: pool.ntp.infomaniak.ch.

The default timezone configuration is in UTC. However, PHP functions are designed to take into account different timezones depending on specific needs.

To adjust the timezone in your PHP scripts, use the function date_default_timezone_set('UTC').

MySQL: temporal specifics

The Infomaniak infrastructure supports features for working with temporal data accurately and efficiently, taking into account timezones, which is crucial for many modern applications:

• MySQL uses a timezone database to store and manage timezone information.
• The mysql.time_zone table contains timezone data, including time offset information, timezone names, etc.
• The CONVERT_TZ function is used to convert a time from one timezone to another in MySQL with the following syntax: CONVERT_TZ(dt, from_tz, to_tz), where:
  • dt is the date/time to convert.
  • from_tz is the source timezone.
  • to_tz is the target timezone.
• Example: CONVERT_TZ('2024-05-14 12:00:00', 'UTC', 'America/New_York') will convert the time 12:00:00 UTC to local time in New York.

This guide helps you resolve an error of the type "Invalid query: MySQL server has gone away".

Introduction

• This type of error often occurs when a MySQL connection is kept open without submitting any queries for a period of time exceeding the connection timeout: http://dev.mysql.com/doc/refman/5.7/en/gone-away.html
• The wait_timeout and interactive_timeout variables, which control this disconnection, are set to 30 seconds: http://dev.mysql.com/doc/refman/5.0/en/communication-errors.html

Solutions

To avoid the "MySQL server has gone away" error, here are several possible approaches:

Automatic Verification and Reconnection

Before executing a query, it is recommended to test whether the MySQL connection is still active. If the connection has been closed, you can automatically re-establish it before proceeding with your query. Here is an example in PHP:

if (!mysqli_ping($connexion)) {
mysqli_close($connexion);
$connexion = mysqli_connect($host, $user, $password, $database);
}

The mysqli_ping() function checks if the connection is still valid. If it is not, the script closes the connection and opens a new one.

Regular "Ping" Sending

Another method is to run a script that regularly sends a "ping" to the database to keep the connection active. For example, you could create a scheduled task (cron job) that sends a lightweight request, such as SELECT 1;, at regular intervals.

Adjusting MySQL parameters (Cloud Server)

With a Cloud Server, you can increase the values of the wait_timeout and interactive_timeout variables from the MySQL menu of your server to extend the connection duration before it is closed.

This guide explains the role of the browscap.ini file, which is used by PHP to identify certain characteristics of a web browser (name, version, operating system, and capabilities) based on its HTTP User-Agent header.

Using with the get_browser() function

The native PHP get_browser() function requires access to an up-to-date browscap.ini file in order to identify the characteristics of the browser that made the request.

On Infomaniak Web Hosting, this file is generally available at the following location:

/opt/php/lib/php/browscap.ini

If necessary, you can check its content using the following script:

<?php
header('Content-Type: text/plain');

$file = '/opt/php/lib/php/browscap.ini';

if (file_exists($file)) {
    echo file_get_contents($file);
} else {
    echo 'File not found.';
}

Due to its size and the cost of loading it, using browscap.ini can impact the performance of applications that rely on get_browser().

Recommended alternatives

For new projects, it is generally preferable to use solutions that are better suited to current web development practices:

• PHP libraries installed with Composer, such as matomo/device-detector or whichbrowser/parser, which offer regularly updated and more comprehensive browser and device detection.
• User-Agent Client Hints (UA-CH), when supported by the browser, to obtain structured information via the mechanisms provided by current HTTP standards.
• Feature Detection, by directly checking the availability of a feature (e.g., in JavaScript or with the CSS rule @supports) rather than inferring behavior based on the browser used.

This guide concerns Django, an open-source web development framework in Python, particularly renowned for its robustness and rapid development capabilities.

Installing Django

Prerequisites

• Suitable hosting:
  • Deploying a Python application requires an application server running continuously; standard shared web hosting is not suitable.
  • Full server access via SSH is required.
• Technical environment:
  • Python 3 installed on the server, as well as the pip package manager.
• Basic knowledge:
  • Familiarity with the command-line interface (CLI) under Linux and the management of Python virtual environments (such as venv).

Here are the general steps to initialize your environment on your server:

It is necessary to install Django on web offers guaranteeing full control over the execution environment, such as Cloud VPS / VPS Lite: discover the different web hosting options from Infomaniak.

1. Connect to your VPS server via SSH.
2. Create and activate a virtual environment dedicated to your project to isolate your dependencies (e.g., python3 -m venv my_environment then source my_environment/bin/activate).
3. Install the framework using the package manager: pip install django.
4. Initialize your new project with the command: django-admin startproject name_of_project.

Deployment

Please note that the development server integrated into Django (launched via runserver) is not designed for a production environment. To securely expose your site on the internet on your Infomaniak VPS, you will need to configure an application server (such as Gunicorn or uWSGI) behind a reverse proxy (such as Nginx or Apache).

This guide will help you find the public IP address of your device, which can be useful when requesting support.

Display the public IP address on the connected device

Click here to obtain the public IP address of your device in IPv4 and IPv6 format.

Alternative methods

Visit ipinfo.io or ifconfig.me.

… on macOS

1. From a Terminal application (command-line interface, CLI) on your device, run the command curl ifconfig.me and press Enter.
2. The address displayed is the public IP address of the computer.

To automate the search for the public IP address, use commands or scripts that query services such as api.ipify.org...

This guide explains how to use PHPMailer with Infomaniak Web Hosting to send emails from a website.

⚠ WARNING ⚠

Infomaniak guarantees that its services comply with standard protocols (IMAP, S3, etc.), but does not provide additional support for external services or software, as their configuration may change depending on the provider or publisherThis guide is therefore provided for informational purposes only, and its implementation remains your responsibility (see: Support Policy / Art. 11.9 of the Terms of Service). If needed, a qualified professional can assist you.

Introduction

• PHPMailer is a PHP library that allows you to create and send emails from a website, particularly via SMTP.
• It allows you to send messages in HTML format, add an alternative text version, manage attachments, and use SMTP authentication.
• For authenticated sending via SMTP, the PHP environment used by the website must be compatible with a recent encrypted connection, specifically TLS 1.2 or higher.
  • An outdated version of PHP or the OpenSSL library used by PHP may cause a connection or authentication error, even if the email address and password are correct.
  • Do not use PHP 5.3/5.4 for this type of sending; use a recent and supported version of PHP.
• With authenticated SMTP sending, the address used as the sender must match the email address used for SMTP authentication.

Install PHPMailer

To use PHPMailer, install the library in your website's files.

1. Download PHPMailer from its official repository or install it with Composer if your project uses it.
2. Copy the PHPMailer files into a directory on your website via FTP.

3. Upload the necessary files to your PHP script, adapting the path according to the chosen location:

   use PHPMailer\PHPMailer\PHPMailer;
   use PHPMailer\PHPMailer\Exception;
   
   require **DIR** . '/PHPMailer/src/Exception.php';
   require **DIR** . '/PHPMailer/src/PHPMailer.php';
   require **DIR** . '/PHPMailer/src/SMTP.php';

Configure SMTP sending with Infomaniak

Use the following authenticated SMTP settings:

• SMTP server: mail.infomaniak.com
• Port: 465
• Encryption: SMTPS / SSL-TLS
• Authentication: required
• Username: the complete email address
• Password: the password for the email address used

Example of a complete configuration:

<?php

use PHPMailer\PHPMailer\PHPMailer;
use PHPMailer\PHPMailer\Exception;

require **DIR** . '/PHPMailer/src/Exception.php';
require **DIR** . '/PHPMailer/src/PHPMailer.php';
require **DIR** . '/PHPMailer/src/SMTP.php';

$mail = new PHPMailer(true);

try {
// Configuration SMTP
$mail->isSMTP();
$mail->Host       = 'mail.infomaniak.com';
$mail->SMTPAuth   = true;
$mail->Username   = '[sender@domain.xyz](mailto:sender@domain.xyz)';
$mail->Password   = 'mot_de_passe_de_l_adresse_mail';
$mail->SMTPSecure = PHPMailer::ENCRYPTION_SMTPS;
$mail->Port       = 465;
$mail->CharSet    = 'UTF-8';

```
// Expéditeur
// L'adresse doit correspondre à celle utilisée pour l'authentification SMTP.
$mail->setFrom('sender@domain.xyz', 'Nom du site');

// Destinataire
$mail->addAddress('recipient@example.com');

// Adresse de réponse facultative
$mail->addReplyTo('sender@domain.xyz', 'Nom du site');

// Contenu du message
$mail->isHTML(true);
$mail->Subject = 'Message envoyé depuis le site';
$mail->Body    = '<p>Contenu HTML du message.</p>';
$mail->AltBody = 'Contenu texte du message.';

$mail->send();
echo 'Message envoyé';
```

} catch (Exception $e) {
echo 'Le message n'a pas pu être envoyé. Erreur: ' . htmlspecialchars($mail->ErrorInfo);
}

If your application requires the use of port 587, use STARTTLS:

$mail->SMTPSecure = PHPMailer::ENCRYPTION_STARTTLS;
$mail->Port       = 587;

Check the PHP version and TLS compatibility

Authenticated SMTP sending requires a recent encrypted connection. If the site uses an outdated version of PHP, for example PHP 5.3, or an outdated OpenSSL library, PHPMailer may fail before or during authentication. The errors may then be misleading, for example:

• SMTP connect() failed
• Could not authenticate
• stream_socket_enable_crypto()
• an authentication error even though the password is correct

In this case, check the following:

1. the PHP version used by the website;
2. the OpenSSL version used by PHP;
3. the version of PHPMailer used by your project;
4. the correspondence between the SMTP port and the chosen encryption method.

For reliable configuration, use a recent version of PHP that is compatible with TLS 1.2 or higher, as well as a current version of PHPMailer. If necessary, refer to these guides:

• Change the PHP version of a website
• Troubleshoot a PHP issue related to an outdated version
• Display the website's technical information

Resolving a Sender Mismatch Error

The error Sender mismatch SMTP code: 550 Additional SMTP info: 5.7.1 can occur when the address used as the sender does not match the email address used for SMTP authentication. Here is an example to avoid:

$mail->Username = 'sender@domain.xyz';
$mail->setFrom('another-address@domain.xyz', 'Nom du site');

In this example, the script authenticates with sender@domain.xyz, but attempts to send the message using a different sender address.

Use the same email address for SMTP authentication and for the sender:

$mail->Username = 'sender@domain.xyz';
$mail->setFrom('sender@domain.xyz', 'Nom du site');

The sender name can be customized, but the email address must remain consistent with the SMTP account used.

In the case of a contact form

If a visitor enters their email address in a form, do not use it as the sender's address for the message. Use the authenticated email address as the sender, and then add the visitor's address as the reply-to address.

Example:

$mail->Username = 'sender@domain.xyz';
$mail->setFrom('sender@domain.xyz', 'Formulaire du site');
$mail->addReplyTo($email_visiteur);

This configuration allows you to respond to visitors from your email software without sending the message with an unauthorized sender address.

Temporarily enable debug mode

In case of an error, temporarily enable PHPMailer's debug mode to obtain more details about the SMTP connection:

$mail->SMTPDebug = 2;
$mail->Debugoutput = 'html';

Disable this mode after your tests to avoid displaying technical information to website visitors.

Learn more

• Authenticated Mail (SMTP) from a Website
• Unauthenticated mail via PHP mail()
• Official PHPMailer documentation

This guide concerns the use of Java technology, which, particularly in terms of RAM consumption, is incompatible with the constraints of Infomaniak's shared hosting offers. Java applications are often resource-intensive, which can affect the performance and stability of servers shared among multiple users.

Limited support for client-side applets

Only client-side Java applets, i.e., those executed in the user's web browser, are supported by shared servers. These applets do not require significant server resources and therefore do not pose the same problems as server-side Java applications. Consequently, no product using server-side Java technology is supported.

Unsupported products and technologies

Here is a non-exhaustive list of specific products and technologies that are not supported on shared servers:

• Apache OFBiz
• Greenstone
• Opentaps
• Compiere (which requires Tomcat)
• Play!
• Solr
• Resin
• JBoss
• Scala
• jftp
• Jakarta EE (formerly Java 2 Platform, Enterprise Edition, or J2EE, then Java Platform, Enterprise Edition, or Java EE)

This policy ensures optimal performance and fair use of resources for all users of shared servers.

This guide explains how to enable the MultiViews option via an .htaccess file on websites hosted by Infomaniak.

Introduction

• In some cases, the MultiViews option must be enabled to manage redirection and URL rewriting issues.
• This option allows the server to guess which file the user is looking for. Example:
  • If the configuration folder and the configuration.php file are located in the root directory of your site and you try to access the address domain.xyz/configuration, the MultiViews option must be enabled so that the server can guess that you want to access the configuration.php file.
• The MultiViews option can sometimes conflict with more complex URL rewriting rules defined by mod_rewrite (used by many CMS).

Enable the MultiViews option

To do this:

1. Open or create the .htaccess file, which is located in the root directory of the website in question.

2. Add the following directive:

   Options +MultiViews

3. Save the changes.

This guide covers the execution of the C# language and the .NET framework via the Mono implementation on Infomaniak hosting.

Technologies for software development

To use the C# language and the .NET framework with the Mono implementation, in order to develop software applications that can be deployed and executed on multiple platforms, outside of the Windows environment, it is recommended to opt for solutions such as:

• Cloud VPS / VPS Lite
• Jelastic Cloud
• Public Cloud

The flexibility and portability offered by these multi-platform environments mean that shared web hosting does not allow execution projects based on C#, .NET or Mono.

This guide explains how to modify an existing Web Hosting offer to, for example, host additional websites if the maximum site quota is reached, or to obtain a more recent hosting solution to benefit from the latest versions of PHP & MySQL.

Modify the web hosting offer to…

… order additional sites, disk space, or IPs

To access the web hosting configurator:

1. Click here to access your hosting management on the Infomaniak Manager (need help?).
2. Click on the action menu ⋮ located to the right of the hosting concerned.
3. Click on Modify the offer:
   
4. Increase the values you wish to modify.
5. Click on the Next button to proceed to the payment of the modifications made to the hosting:
   

… switch to a more recent server

To obtain a hosting solution on a more recent server and thus benefit from, among other things, the latest versions of PHP & MySQL, you can either…

• … refer to this other guide by following the procedure indicated to the end:
  
• … refer to this other guide by following the procedure indicated up to point 4 then click on the button to update:
  

This guide details the integration of the ASP / ASP.NET environment within the Infomaniak ecosystem.

Compatibility & Infrastructure

Web Hosting and Managed Cloud Server solutions are optimized for Linux/Apache environments. Therefore, the Apache::ASP module is not natively supported on these shared offers.

Alternatives & Cloud solutions

To deploy your ASP applications smoothly, several options are available to you:

• VPS Cloud: install and configure your own ASP/IIS stack or use Mono/Core on a distribution of your choice.
• Jelastic Cloud (PaaS) : deploy your ASP.NET Core applications via Docker containers in a few clicks with automatic horizontal scaling.
• Public Cloud: for high-availability infrastructures using OpenStack, ideal for microservices architectures.

This guide explains how to limit hotlinking on files hosted by your Infomaniak Web Hosting.

Introduction

• Hotlinking is when a third-party website displays images, videos, or other files hosted on your server directly, using their public URL, without hosting them itself.
• This practice uses your hosting's resources (bandwidth, HTTP connections, and server resources) without your authorization. It can also infringe on your copyrights or your control over the distribution of your content.
• Although current network capabilities make the impact on bandwidth generally less critical than before, it is still recommended to limit hotlinking to avoid unnecessary consumption of your hosting resources.

Prevent hotlinking with an .htaccess file

If your website uses the Apache web server and the mod_rewrite module, you can restrict direct access to certain files by adding rules to the .htaccess file located in the root directory of your website.

The example below protects the main image formats, including the modern WebP and AVIF formats:

RewriteEngine On

# Allow requests without a Referer header
RewriteCond %{HTTP_REFERER} !^$

# Allow requests from your own domain (replace with your domain)
RewriteCond %{HTTP_REFERER} !^https?://(www\.)?votre-domaine\.com [NC]

# Allow major search engines
RewriteCond %{HTTP_REFERER} !^https?://(www\.)?google\. [NC]
RewriteCond %{HTTP_REFERER} !^https?://(www\.)?bing\. [NC]
RewriteCond %{HTTP_REFERER} !^https?://(www\.)?yahoo\. [NC]

# Block hotlinking for image files
RewriteRule \.(jpg|jpeg|png|gif|svg|webp|avif)$ - [F,NC,L]

Adapt before use:

• Replace your-domain.com with your own domain name.
• Requests that do not contain an HTTP Referer header are allowed in order to maintain compatibility with certain browsers, applications, or privacy protection mechanisms that do not transmit this header.
• The rules allowing major search engines to access images enable their robots to index them. Deleting them will prevent these images from being indexed.
• The rule uses the [F] option, which returns an HTTP 403 Forbidden response. This method immediately blocks the request without serving any additional content, which limits the consumption of server resources.

This guide presents commands that can be executed to test a connection or network and thus further identify the possible source of the error.

Perform a Telnet…

TELNET allows you to test the connection to a server without taking into account all the additional settings of a mail or FTP application, in order to determine the source of a problem. For example, if the connection fails on an SMTP server, you will need to check whether your firewall is blocking port 587 or 465.

… on macOS

1. Search for Network Utility.
2. Go to the Ping, Lookup, or Traceroute tab, depending on what you want to test.
3. You can also use a Terminal application (command-line interface, CLI) on your device and, depending on what you want to test, enter:
   traceroute [server]
nc [server] [port]
   Replace [server] with the server name or its IP address, and do the same for [port]…

… on Windows

Enable Telnet beforehand if necessary.

1. Use a Terminal application (command-line interface, CLI) on your device, for example by typing Run then cmd.
2. In the window that opens, depending on what you want to test, type:
   tracert [server]
telnet [server] [port]
   Example: telnet mail.infomaniak.com 587(this allows you to test the SMTP port if your software/email client does not allow you to send emails)…

… on Android

1. Use the Simple Telnet Client app, which allows you to easily test by filling in two fields (for example, mail.infomaniak.com and port 143 or 993)…

Perform a PING

PING allows you to determine if a machine is accessible via the Internet. You can also use this tool to verify that you are connecting to the correct machine, for example, after a DNS change, by checking the IP address obtained. It is possible to perform a ping on a domain name, a hostname, or an IP address.

This guide details the steps to take if you don't see any difference on your website after making a change, compared to its version before the change. These tips are also relevant if you encounter issues while using the Infomaniak product interface.

Introduction

• While you browse, a web browser saves the data you view in a dedicated space. This is done to avoid repeatedly requesting the same data from the server, saving time and resources.
• Your cache can contain a large amount of data, and sometimes the browser gets confused. As a result, websites may not display correctly or may display an outdated version.
• Clearing the cache ensures that you are viewing the latest version of the page or folder.

Clear your web browser's cache…

… on Safari

Choose your macOS version to view the corresponding Apple support.

… regarding Google tools (Chrome, Android, etc.)

Please refer to the Google help.

… on Firefox

Please refer to the Mozilla help.

… on Edge / Internet Explorer

Refer to the Microsoft help.

This guide details the features available for managing relational databases on Infomaniak hosting plans.

Using Views, Triggers, Stored Procedures, and Routines

Regarding the management of relational databases, the functionality of views is available by default, allowing users to create views to simplify data management and presentation.

However, some advanced features that enable finer and more complex data manipulation, such as…

• “triggers”
• stored procedures
• routines
• and the creation of functions

… are only available on Cloud Servers.

This restriction is mainly due to the potential risks to the stability of the infrastructure. Incorrect configuration or excessive use of these features could create infinite loops or significant overloads, affecting not only the performance of the server in question but also the experience of all customers hosted on the same infrastructure.

Troubleshooting MySQL/MariaDB dump import issues

When exporting and then re-importing a MySQL or MariaDB database via the Infomaniak hosting interface, the operation may fail due to errors related to the DEFINER of triggers or views. This occurs when the database objects were created with a specific user (called the definer) who no longer exists at the time of import.

Specifically, the export and import process uses a temporary user, which is used only during these operations. After this user is deleted, the views or triggers defined with this account as the DEFINER become invalid, causing errors such as:

General error: 1449 The user specified as a definer ('xxxx_temp_1'@'%') does not exist

To avoid this issue, you can correct the backup file (dump.sql or dump.sql.gz) before importing it by replacing the definer definitions with CURRENT_USER. This will automatically associate the triggers and views with the current user at the time of import.

Here is an example of a command to modify the dump before importing it:

sed -E 's/DEFINER=`[^`][^`]*`@`[^`][^`][^`]*`/DEFINER=CURRENT_USER/g' dump.sql > dump-corrected.sql

Once this replacement is done, the corrected file can be imported normally via the Infomaniak Manager. This behavior is known and related to the way temporary users function during the dump/restore process. No changes to the export/import process are planned in the short term, but the issue is still being evaluated on the infrastructure side.

For more information on the CURRENT_USER variable, please refer to the official documentation of:

• MySQL
• MariaDB

This guide explains how to change the password of a MySQL / MariaDB database from a Web Hosting.

Preamble

• Refer to this other guide if you are looking for information about updating connection information (scripts, sites...) related to a database password change.
• A database user created following the installation of a Web Application (offered by Infomaniak) cannot be modified (a lock icon appears next to it, see point 5 below).
• To access the database to which it is attached, you must create a new database user with the password of your choice and then assign rights to the desired database.

Change MySQL MariaDB password etc.

To do this, you need to intervene on the user attached to the database in question and change the password (without having to provide the old one) from the Infomaniak Manager:

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 Databases in the left sidebar.
4. Click on the Users tab.
5. Click on the action menu ⋮ located to the right of the item in question.
6. Click on Modify:
   
7. Click on Change password.
8. Enter the desired new password.
9. Click on the Save button:
   
10. If necessary, you can configure the new possible rights (read/write/administration) of the user for access to existing databases on the hosting.