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 force the display of the web hosting name in the browser address bar to one of the domain names installed as an alias/synonym or how to display the main domain in the address bar instead of the alias.

Limit the 'duplicate content' or duplicate content

Imagine you have the hosting your-domain.com at Infomaniak and as a synonym domain name you have installed www.synodomain.xyz.

By default, when you type one or the other of the domain names (your-domain.com or synodomain.xyz) in the address bar of your browser, it is the one you typed that will be displayed in the address bar.

You therefore have the possibility to force the display of a different address than the one that was typed. Thus, if someone types synodomain.xyz, then it is your-domain.com that will automatically be displayed in the address bar.

A code must be entered in a file called .htaccess which must be located at the root of your hosting (in the /web folder of your FTP). If this file does not exist yet, you must create it on the server.

Insert these directives into the file:

RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule (.*) https://votre-domaine.com/$1 [R=301,L]

Adapt the code above according to these indications:

• Replace your-domain.com with your domain name with the appropriate extension (.com, .fr, .ch, etc.) that you want to see displayed in the visitor's browser address bar. Add www. before your-domain.com if necessary.
• Replace the second line of the code above with "RewriteCond %{HTTPS} off‍" if a loop error occurs, this means that HTTP/2 is active for this site

Also refer to the automatic redirections 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 resolve an error of type "Invalid query: MySQL server has gone away".

Preamble

• This type of error often originates from keeping a MySQL connection open without submitting requests for a period of time beyond which the connection is closed: http://dev.mysql.com/doc/refman/5.7/en/gone-away.html
• The variables wait_timeout and interactive_timeout that 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:

Verification and automatic reconnection

Before executing a query, it is recommended to test if 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 function mysqli_ping() 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 light query, such as SELECT 1; at regular intervals.

Adjusting MySQL parameters (Cloud Server)

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

This guide covers "browscap.ini", a legacy configuration file used by PHP to identify web browser characteristics (name, version, capabilities, OS) from their User-Agent string.

Information about the file and legacy usage

For the native PHP function get_browser() to work, it must point to an up-to-date browscap.ini file. The default path on servers is usually:

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

Although not recommended for production due to the file size (several MB to load into memory), you can view its content via this script:

<?php
header("Content-type: text/plain");
if (file_exists("/opt/php/lib/php/browscap.ini")) {
    echo file_get_contents("/opt/php/lib/php/browscap.ini");
} else {
    echo "Fichier introuvable.";
}
?>

Recommended modern alternatives

For current projects, developers prefer the following solutions:

1. Libraries via Composer: tools like matomo/device-detector or whichbrowser/parser are more accurate, faster, and easily updated via project dependencies.
2. User-Agent Client Hints (UA-CH): the new HTTP standard for obtaining structured and reliable information directly from the browser.
3. Feature Detection: use JavaScript (or @supports queries in CSS) to check if a feature exists, rather than guessing the browser name.

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...

Este guia explica como usar o PHPMailer com as soluções de hospedagem web da Infomaniak para enviar e-mails a partir de um site.

⚠ ATENÇÃO ⚠

A Infomaniak garante a conformidade de seus serviços com os protocolos padrão (IMAP, S3, etc.), mas não oferece suporte adicional para serviços ou softwares externos, pois a configuração deles pode mudar dependendo do provedor ou do desenvolvedor. Portanto, este guia é fornecido apenas como referência, e a sua implementação é de sua responsabilidade (consulte: Política de suporte / Art. 11.9 dos Termos de Uso). Se necessário, um profissional qualificado pode ajudá-lo.

Introdução

• O PHPMailer é uma biblioteca PHP que permite criar e enviar e-mails a partir de um site, principalmente via SMTP.
• Ele permite, em particular, enviar mensagens no formato HTML, adicionar uma versão de texto alternativa, gerenciar anexos e usar a autenticação SMTP.
• Para envio autenticado via SMTP, o ambiente PHP usado pelo site deve ser compatível com uma conexão criptografada recente, principalmente TLS 1.2 ou superior.
  • Uma versão muito antiga do PHP ou da biblioteca OpenSSL usada pelo PHP pode causar um erro de conexão ou autenticação, mesmo que o endereço de e-mail e a senha estejam corretos.
  • Não use o PHP 5.3/5.4 para este tipo de envio; use uma versão recente e atualizada do PHP.
• Com o envio SMTP autenticado, o endereço usado como remetente deve corresponder ao endereço de e-mail usado para a autenticação SMTP.

Instalar o PHPMailer

Para usar o PHPMailer, instale a biblioteca nos arquivos do seu site.

1. Baixe o PHPMailer do seu repositório oficial ou instale-o com o Composer, se o seu projeto o utilizar.
2. Copie os arquivos do PHPMailer para um diretório do seu site via FTP.

3. Carregue os arquivos necessários no seu script PHP, adaptando o caminho de acordo com o local escolhido:

   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';

Configurar o envio SMTP com a Infomaniak

Use as seguintes configurações SMTP autenticadas:

• Servidor SMTP: mail.infomaniak.com
• Porta: 465
• Criptografia: SMTPS / SSL-TLS
• Autenticação: obrigatória
• Nome de usuário: o endereço de e-mail completo
• Senha: a senha do endereço de e-mail usado

Exemplo de configuração completa:

<?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);
}

Se a sua aplicação exigir o uso da porta 587, use STARTTLS:

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

Verificar a versão do PHP e a compatibilidade TLS

O envio SMTP autenticado requer uma conexão criptografada recente. Se o site usar uma versão muito antiga do PHP, por exemplo, PHP 5.3, ou uma biblioteca OpenSSL muito antiga, o PHPMailer pode falhar antes ou durante a autenticação. Os erros podem então ser enganosos, por exemplo:

• SMTP connect() failed
• Could not authenticate
• stream_socket_enable_crypto()
• um erro de autenticação, mesmo que a senha esteja correta

Nesse caso, verifique os seguintes pontos:

1. a versão do PHP utilizada pelo site;
2. a versão do OpenSSL utilizada pelo PHP;
3. a versão do PHPMailer utilizada pelo seu projeto;
4. a correspondência entre a porta SMTP e a criptografia escolhida.

Para uma configuração confiável, utilize uma versão recente do PHP, compatível com TLS 1.2 ou superior, e uma versão atual do PHPMailer. Consulte estes guias, se necessário:

• Alterar a versão do PHP de um site
• Resolver um problema PHP relacionado a uma versão desatualizada
• Exibir as informações técnicas do site

Resolver um erro de incompatibilidade de remetente

O erro Sender mismatch SMTP code: 550 Additional SMTP info: 5.7.1 pode ocorrer quando o endereço usado como remetente não corresponde ao endereço de e-mail usado para a autenticação SMTP. Exemplo a ser evitado:

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

Neste exemplo, o script se autentica com sender@domain.xyz, mas tenta enviar a mensagem com outro endereço de remetente.

Use o mesmo endereço de e-mail para a autenticação SMTP e para o remetente:

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

O nome do remetente pode ser personalizado, mas o endereço de e-mail deve permanecer consistente com a conta SMTP utilizada.

Caso de um formulário de contato

Se um visitante preencher seu endereço de e-mail em um formulário, não o utilize como endereço de remetente da mensagem. Utilize o endereço de e-mail autenticado como remetente e adicione o endereço do visitante como endereço de resposta.

Exemplo:

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

Essa configuração permite responder ao visitante a partir do seu software de e-mail sem enviar a mensagem com um endereço de remetente não autorizado.

Ativar o modo de depuração temporariamente

Em caso de erro, ative temporariamente o modo de depuração do PHPMailer para obter mais detalhes sobre a conexão SMTP:

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

Desative este modo após os seus testes para não exibir informações técnicas aos visitantes do site.

Saiba mais

• E-mail autenticado (SMTP) a partir de um site
• E-mail não autenticado via PHP mail()
• Documentação oficial do PHPMailer

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 a .htaccess file on sites hosted by Infomaniak.

Preamble

• 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 at the root of your site and you try to access the address domain.xyz/configuration, the MultiViews option must be enabled for the server to 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 located at the root of the affected site.

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 the Windows environment, it is recommended to opt for solutions such as:

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

The flexibility and portability offered by these multi-platform environments mean that a shared web hosting does not allow the execution of 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 helps you protect your resources against hotlinking on your Infomaniak Web Hosting.

Preamble

• Hotlinking occurs when a third-party site displays your images, videos, or music by directly using the URL of your server; the remote site uses your resources and server power at your expense, often without citing the source.
• Although bandwidth is more generous today, hotlinking remains a problem for protecting your copyrights and avoiding unnecessary overloading of your server.

Prevent hotlinking via .htaccess

You can block these unauthorized accesses by adding rules to the .htaccess file at the root of your site. Here is an optimized version including modern image formats (WebP, AVIF):

RewriteEngine on

# 1. Autoriser les requêtes avec un Referer vide (certains navigateurs pour la vie privée)
RewriteCond %{HTTP_REFERER} !^$

# 2. Autoriser votre propre site (remplacez par votre domaine)
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?votre-domaine\.com [NC]

# 3. AUTORISER LES MOTEURS DE RECHERCHE (Indispensable pour votre SEO)
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?google\. [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?bing\. [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?yahoo\. [NC]

# 4. Bloquer le hotlinking (renvoie une erreur 403 Forbidden)
RewriteRule \.(jpg|jpeg|png|gif|svg|webp|avif)$ - [F,NC,L]

Recommendations:

• Replace: change your-domain\.com with your actual domain name.
• SEO: only remove the Google/Bing lines if you intentionally want your images to never appear in search results.
• Alternative 403: the rule above uses [F] (Forbidden). This is more ecological and performant than loading a replacement image that still consumes bandwidth.

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

Perform a Telnet...

TELNET allows you to test the connection to a server without considering all the additional settings of a mail or FTP application in order to determine the origin of a problem. If the connection does not go through on an SMTP server, for example, you will need to check if your firewall is not 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 type application (command line interface, CLI / Command Line Interface) 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, same for [port]...

... on Windows

Enable Telnet if necessary.

1. Use a Terminal type application (command line interface, CLI / Command Line Interface) 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 (allows you to test the SMTP port if your software/email client does not allow sending emails)...

... on Android

1. Use the application Simple Telnet Client which allows you to test very simply via 2 fields to fill in (for example mail.infomaniak.com and port 143 or 993)...

Perform a PING

PING allows you to know if a machine is accessible via the Internet. You can also check with this tool if you are addressing the correct machine, for example during a DNS change, by looking at 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 priority actions to take if you do not see any difference between your website after a change you made to it, and its previous version before the change. These tips are also valid if you encounter issues while using the Infomaniak product interface.

Preamble

• During your browsing, a web browser saves the data consulted in a reserved space, in order to avoid requesting the data already consulted from the server again, to save time and resources.
• Your cache can contain a lot of data and sometimes the browser gets confused. Sites can then display incorrectly or display an outdated version.
• Clearing the cache ensures that you have the very latest version of the page or folder consulted.

Clearing the web browser cache …

… on Safari

Choose your macOS version to view the corresponding Apple help.

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

View the Google help.

… on Firefox

View the Mozilla help.

… on Edge / Internet Explorer

View the Microsoft help.

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

Use of Views, Triggers, Stored Procedures, and Routines

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

However, some advanced features that allow for more precise and complex data manipulation, such as…

• “triggers (triggers)
• stored procedures ("stored procedures")
• routines
• and the creation of functions

… are only available on Managed Cloud Servers.

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

Resolving a MySQL/MariaDB dump import issue

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

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

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

To avoid this problem, it is possible to correct the backup file (dump.sql or dump.sql.gz) before importing it by replacing the definer definitions with CURRENT_USER. This automatically attaches the triggers and views to the current user at the time of import.

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

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 operation of temporary users during dump/restore. No changes to the export/import process are planned in the short term, but the subject remains under evaluation on the infrastructure side.

For more information about the CURRENT_USER variable, 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.