Knowledge base

This guide details the security measures implemented as part of Infomaniak's email services to detect abusive and abnormal use of an email address.

Introduction

• For sending emails to a large number of recipients, the Newsletter tool is the most suitable.
• Upon written request, which must be justified and authenticated, it is possible to modify these security rules for a specific paid email address.
• These measures protect you from malicious use of your computer or account.
• Quota calculation (sliding window): the limits (below) are not reset at midnight but calculated in real time over a 24-hour window; each message sent "occupies" a slot in your quota and is automatically freed up 24 hours after it is sent.
  • If you send messages throughout the morning until you reach your limit at 11 a.m., your sending rights will gradually become available the next morning, as each message reaches its 24-hour age.
• 1 message sent to 2, 42, or 99 people in CC/BCC counts as 2, 42, and 99 messages, respectively.

Sending limits per 24 hours

Number of outgoing emails possible per 24 hours:

* The maximum number depends on the email plan to which the address belongs.

Other email limits

• Limits on the number of recipients per email
• Email size limits

This guide details Infomaniak's Managed Cloud Server offering and Infomaniak's VPS offering, which are intended for different uses.

Introduction

• Infomaniak offers two advanced hosting solutions:
  1. the Managed Cloud Server, which allows you to create multiple hosting accounts (FTP/SSH spaces) on which you can add your websites (Apache vhosts),
  2. and the VPS (Virtual Private Server), which offers complete administrative freedom and meets different needs.

Managed Cloud Server

The Cloud Server allows you to overcome the limitations of shared hosting. You can create and distribute your websites as you wish, define the root directory for each site, and adjust parameters such as memory_limit and max_execution_time.

Integrated tools are provided: cron jobs, Site Creator, simplified WordPress installation, and access and error logs. It is also possible to add specific Apache modules or install a caching system.

The software environment is managed by Infomaniak (FastCGI, PHP-FPM). You do not have complete freedom to configure the server (no arbitrary software installation), but some specific programs can be installed.

VPS (unmanaged)

The VPS gives you complete control over the server, but you are responsible for its management. Infomaniak manages the hardware and installs the version of Linux or Windows that you selected when placing your order. Infomaniak does not perform any software-related operations: you administer the system, install, and configure the software.

You can restart the server via the Infomaniak Manager. A snapshot system is available (except for the VPS Lite offer).

Video content and alternatives

If your project mainly involves a large volume of videos, it is often preferable to separate video streaming from the main hosting. Combined with shared hosting, the Infomaniak VOD/AOD service allows you to efficiently store and stream videos, handle traffic spikes, and obtain detailed viewing statistics.

Migration between Cloud Server and VPS

There is no automated migration solution between a managed Cloud Server and a VPS.To switch from one plan to another, you must cancel the product you no longer use and order the new plan. Infomaniak will refund any new server upon request if the cancellation occurs within 30 days of the order.

Jelastic Cloud Infomaniak is one of the most complete and flexible PaaS solutions on the market.

Preamble

• Node.js = official name of the language/environment.
• NodeJS = "technical" or simplified name in certain contexts (often for practical reasons, no real technical difference).

Supported languages

You will be able to deploy Java, PHP, Ruby, Node.js, Python and Go applications without having to adapt your code using Docker, Kubernetes, GIT, SVN or built-in extensions like Maven, Ant, Eclipse, NetBeans or IntelliJ IDEA.

Supported SQL and NoSQL databases

MariaDB, MongoDB, MySQL, Postgre, Redis, Neo4j, Cassandra, OrientDB, PerconaDB, CouchDB, Couchbase.

Supported application servers

Tomcat, TomEE, Jetty, GlassFish, Payara, Apache PHP, Apache Ruby, Apache Python, NGINX PHP, NGINX Ruby, NodeJS, JBoss, SmartFoxServer, SpringBoot, WildFly, Golang.

Supported load balancers

NGINX, Apache Balancer, HAProxy, Varnish.

This guide explains how to redirect a domain name directly to another, or how to automatically send visitors to your website to another page address (internal or external URL).

Introduction

• To redirect traffic, you will need to take action…
  • … either on the domain name itself (it must be hosted by Infomaniak and its DNS must also be Infomaniak's),
  • … or on the code present in your pages (e.g., .htaccess page, homepage, etc.) if you have a website.

Acting on the domain name

Via Web Redirection Tool

The tool available in the Manager allows you to easily manage your domain name (or subdomain) and redirect it to the internet address of your choice.

via DNS modifications or A record updates

Change the DNS of the domain name or modify its A/AAAA records to redirect web traffic to another provider.

Modify the page code…

… by inserting HTML code

Insert this line of code between the <head> and </head> tags of your homepage (usually named index.html):

<meta http-equiv="refresh" content="5;url=INSERT-HERE-NEW-URL">

Replace 5 with the desired wait time in seconds (0 for immediate execution).

The Google search engine indicates that it is preferable to use a 301 redirect on the server-side (see below). The W3C also advises against using it.

… via PHP code to be inserted

If the website page has a .php extension, insert this function call at the very top of the file:

header("refresh: 5; url=INSERT-HERE-NEW-PAGE-URL");
```
… via the .htaccess file

… via fichier .htaccess

To redirect all traffic to your site (regardless of the page being accessed) to another address, insert the following into the .htaccess file at the root of your site:

RewriteEngine On
RewriteRule ^(.*)$ INSERT-HERE-NEW-URL/$1 [R=301]

To target the page that should be redirected:

Redirect permanent /old_page.html insert destination URL here

Redirectpermanent, Redirect permanent, and Redirect 301 are equivalent commands.

The following is another example of redirecting a sub-section to the homepage (this directive has the advantage of working with "deep links" unlike a permanent redirect):

RewriteEngine on
RewriteRule "old/path/url" "/" [L]

Refer to this other guide for more information.

Thank you for choosing Infomaniak to create your PaaS!

This guide will help you quickly use the main features of your new Jelastic Cloud product.

Frequently Asked Questions

• Introduction to Jelastic
• Containers and nodes: how they work
• Jelastic billing and how Cloudlets work
• Technologies compatible with Jelastic Cloud
• Create a VPS with Jelastic Cloud
• Methods for deploying an application
• Differences between Jelastic Cloud and a VPS
• Resources available depending on the account type

Access the complete FAQ on Jelastic Cloud.

Technical Resources

Consult the official Jelastic documentation (in English) for more technical details:

• Deploying applications in a cluster (WordPress, Magento, etc.)
• Creating an environment
• Deploying applications or code
• Configuring servers (Java, PHP, Ruby, etc.)
• Linking a domain name
• Adding a public IP address
• Monitoring application statistics
• SSH access to your environment
• Managing resource consumption alerts
• Dynamic resizing: horizontal and vertical
• Install packages without root access using Yum Packages Installer

For any questions or difficulties, do not hesitate to contact Infomaniak support.

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

What is a 403 error?

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

When does this error occur?

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

The user is authenticated but does not have the necessary permissions: the server recognizes the user but does not allow them to access the requested resource due to permission or role restrictions. This cause of the 403 error may be due to incorrect permissions on a folder or file. For a folder, the error message is of the type "403 Forbidden", for a file, "failed to open stream: Permission denied". In this case, you should check that the permissions for your folders/files are correct, i.e., at least 644 for a file and 755 for a folder. See this other guide.

The user's IP address is blocked or restricted: the server may block access to a specific IP address for security reasons, to protect against attacks, etc. See this other guide.

The requested resource does not exist on the server: in this case, the server returns a 403 error instead of a 404 error to prevent the disclosure of confidential information. If you are trying to access your homepage or a part of your site by entering an address like www.domain.xyz or www.domain.xyz/folder/, make sure that there is indeed a homepage named "index.html, .htm, or .php" placed in the correct location (at the root of your FTP space, in the /web directory, or in the /folder/ directory). Refer to this other guide.

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

Script-related error: if you were running a script, filling out a form, or uploading a file and you receive this type of message:

Accès interdit!
Vous n'avez pas le droit d'accéder à l'objet demandé.
Soit celui-ci est protégé, soit il ne peut être lu par le serveur.
Si vous pensez qu'il s'agit d'une erreur du serveur, veuillez contacter le gestionnaire du site.
Error 403

the cause may be a filter that prevents the unwanted use of scripts by spammers. Indeed, the Infomaniak antivirus blocks file uploads via scripts or via FTP. This means that when a hacker sends a file identified as a virus via a form, an insecure script, or via FTP, its installation is directly blocked, the file is not uploaded to the server, and the upload generates a 403 error.

In the event of a false positive, contact Infomaniak support, providing the URL of the page where you are encountering this error message, in order to accurately diagnose the cause of the problem.

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

This guide provides important details regarding the launch and execution of command-line scripts (SSH) on various types of Infomaniak hosting.

Executing scripts via SSH and managing resources

Unlike scripts executed via a web browser, there is generally no strict time limit (timeout) for commands launched via SSH. Your script can therefore theoretically run as long as necessary.

Execution time and persistence

If your SSH session closes (loss of internet connection or terminal closure), the running script will be immediately interrupted.

To avoid this during long tasks, it is recommended to run your scripts in the background or, in the case of a VPS, use terminal multiplexing tools (such as screen, tmux, or the nohup utility). This allows the process to continue its work even after you disconnect.

Resource limits (RAM and CPU)

If time is not limited, hardware resources are.

The execution of your scripts remains subject to the capabilities of the machine and its configuration:

• Memory (RAM): if a process consumes more memory than the allowed limit (for example, the memory_limit of PHP or the available physical RAM), it will be killed by the system to preserve the stability of the server.
• Processor (CPU): excessive use of the processor over a long period can result in throttling or interruption of the process.

This guide explains what a web hosting provider like Infomaniak is, and specifies its role, scope, and the limits of its technical support.

Infomaniak, a hosting provider since 1996

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

Infomaniak also offers:

• … decades of experience in hosting and high-performance online solutions.
• … over a million users in Switzerland and Europe trusting us with the management of their critical data.
• … a company certified according to ISO 27001, 9001, 14001, 50001 standards and committed to sustainable digital practices.
• … 100% Swiss-made technological expertise with data hosted in Switzerland in its own data centers.
• … a comprehensive knowledge base and a customer support service available to assist you.

Responsibilities and scope of intervention

As a hosting provider, Infomaniak installs, secures, and keeps the server infrastructure up to dateis constantly improving its management interfaces (Manager) and helping its customers to make the most of the tools provided. Infomaniak strives to offer solutions that are accessible to everyone; however, human support for free products is inherently limited in order to guarantee the sustainability of these services.

Support is exclusively for Organization administrators. End customers or users with a contract through a Reseller Partner must first contact their administrator or dedicated service provider.

Scope of technical support

Technical support does not provide assistance for:

• Development and programming: debugging websites, correcting source code, personal scripts (PHP, JS, etc.)
• API usage and integration.
• Application maintenance and webmastering: troubleshooting, updates, or content management for third-party applications (e.g., CMS such as WordPress, email clients such as Outlook, etc.).
• On-site and customized support: remote access, configuration of your own hardware, complex manual installations or migrations.

However, our support team will be happy to assist you with:

• Infrastructure and Manager: resolving incidents related to the network, hardware, or Infomaniak management interfaces.
• Using Infomaniak services: clarifying configuration processes and providing assistance with using our native features.
• Documentation: we will guide you to the relevant resources and technical guides to help you become self-sufficient.

A Premium support service and a migration service are available for more specific needs.

Find external support

For assistance with the content of your website, its programming, or the advanced organization of your email accounts, use the Infomaniak bidding platform, which lists over 1000 verified professionals, or consult the directory.

This guide explains how to optimize a website hosted on a Web Hosting service to make it faster and provide a smooth navigation experience for all your visitors, regardless of their connection speed.

The role of the host

1. Your hosting server is functioning normally and has not encountered any incidents in the last 48 hours.
2. The network infrastructure has not experienced any disruptions during this same period.

The role of the site owner and the webmaster

Infomaniak does not intervene on the content of the servers or the development of the sites. The creation and maintenance of a site are distinct professions, although they use the tools and services provided by the host.

Analyze the cause of slowness

Here are the actions to take if you notice slowness on your site:

1. Apply the Google PageSpeed Insights recommendations. These points concern the design of the site and not the server configuration. Refer to this other guide if the test recommends enabling resource compression.
2. If slowness is noticed from abroad, activate DNS Fast Anycast.
3. Install a caching system to reduce redundant database accesses and speed up display.
4. Consider using a CDN.
5. Test the server response time or TTFB.
6. Scan your hosting to detect any potential viruses.
7. Purge your databases regularly by deleting unnecessary entries.
8. Use the latest PHP version compatible with your site or CMS.
9. Avoid images, counters, or media hosted on external servers: if they are unreachable, your site will appear slow.
10. Deactivate unnecessary or resource-intensive WordPress extensions.
11. Keep your CMS and web applications regularly updated.
12. Limit the impact of overly aggressive indexing robots by configuring a Crawl-delay.
13. Analyze the error-logs: correcting the errors generated by your site improves its performance.
14. Review the slowlogs to identify SQL queries taking more than 5 seconds to execute and optimize them (optimization examples).
15. Add a server cache engine like Memcached (available on Cloud servers only).
16. Increase the max_children value (only on Cloud servers).

If the problem persists

If you or your webmaster cannot find the source of the slowdowns, contact Infomaniak support in writing by providing the following information:

1. Name of the hosted site.
2. Exact dates and times of the slowdowns.
3. Name of the database or FTP account potentially involved.
4. Your public IP address during tests (visible on https://www.infomaniak.com/ip).
5. Type of slowdown (display, FTP transfers, etc.).
6. Indicate if you can normally access the Infomaniak site during these episodes.
7. Complete result of a traceroute to 84.16.66.66.
8. Result of a speed test on speedtest.net by selecting Infomaniak as the destination server.

If your needs evolve

If shared hosting is no longer sufficient, consider switching to a Managed Cloud Server. Your site can be easily migrated to take advantage of dedicated resources and advanced caching technologies.

This guide covers the database management features available with Infomaniak hosting.

MySQL, SQLite, MariaDB, PostgreSQL…

At the Database Management System, hosting supports…

1. … MySQL databases via PHP MySQL access or via Perl DBI+DBD::mysql
   • You can use MySQL as a database management system (DBMS) on Infomaniak servers.
   • You can access it either via PHP using the built-in MySQL database functions, or via Perl using the DBI and DBD::mysql modules
2. … MySQLI, the native MySQL access interface (PHP5)
   • MySQLI is a PHP extension that allows access to a MySQL database.
   • It is an improved and more recent version of the old MySQL extension of PHP, offering enhanced features and performance.
3. … SQLite 3.x
   • SQLite is a lightweight, standalone, and serverless SQL database engine.
   • Infomaniak servers support SQLite version 3.x, which means you can use SQLite to store data on these servers.
4. … MariaDB
   • MariaDB is a fork of MySQL and is often used as an alternative to MySQL
   • You can therefore use MariaDB as a database management system on Infomaniak servers
5. … the PGSQL module
   • PGSQL is a PHP module that allows you to connect to a PostgreSQL database
   • This specific feature allows you to connect to a REMOTE PostgreSQL database via PHP; this requires opening the appropriate port to the specific IP of the PostgreSQL database from the Infomaniak manager.

This guide covers installing PHP extensions on Infomaniak Web Hosting.

Using PHP Zend Extensions

Attention:

• Zend Guard Loader is a PHP extension that allows you to run PHP scripts encrypted via Zend Guard.
  • Zend Guard Loader is installed by default for PHP <= 5.6 on all web hosting plans and is not available for PHP versions >= 5.6.
• Since PHP 5.3.x, the Zend Optimizer module has been replaced by ZendGuardLoader.
• The ZendOPCache extension requires a Cloud Server configured with PHP 5.5 or later.

This guide explains how to modify the server configuration of a site on Web Hosting Infomaniak.

Preamble

• Apache is the HTTP server.
  • It is configured with a .htaccess file placed at the root of the website.
• PHP is a programming language used to create dynamic web pages via an HTTP server.
  • It is possible to customize PHP directives with a .user.ini file, which will be effective in the folders and subfolders of the location of the .user.ini file.
• Refer to this other guide regarding the creation of .htaccess & .user.ini files.

Modify the server configuration of a site…

… via the Manager

To modify the PHP configuration and most of the parameters (max_input_vars, allow_url_fopen, memory_limit, post_max_size + upload_max_filesize, etc.):

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 Manage advanced settings:
   
4. Click on the different tabs General, PHP / Apache and PHP Extensions to make the desired adjustments:
   
   • Refer to this other guide if you are looking for information about limit values and the possibilities of unlocking these.
   • If necessary, refer to this other guide regarding the fourth tab.

… via the .user.ini file

For PHP directives that are not present on the Manager side, it is necessary to define the desired values in the .user.ini file, for example:

max_file_uploads = 20

The list of existing directives can be found on the official PHP website but the elements with the indication PHP_INI_SYSTEM in the Modifiable column as well as max_input_time, memory_limit and mysqli.default_socket are not usable.

… in CLI

To customize PHP directives when executing scripts in command line (CLI) or in CRON tasks, it is necessary to specify the desired values in a .user.ini file.

Then, to apply these configurations, the PHP executable is used with the -c option followed by the path to the .user.ini file.

For example, to modify the memory limit available for PHP to 1024M, you can create or modify the .user.ini file using the following command:

echo 'memory_limit = 1024M' > .user.ini

This command writes the memory_limit directive with the value 1024M in the .user.ini file.

Then, when running a PHP script from the command line or in a CRON task, use the PHP command with the -c option to specify the .user.ini file containing the custom configurations.

The following example enables allow_url_fopen for the WP CLI tool (allows, among other things, retrieving extensions):

php -d allow_url_fopen=On ~/bin/wp package install trepmal/wp-revisions-cli

• php: the PHP executable
• -d allow_url_fopen=On: the -d option allows setting a PHP configuration directive (allow_url_fopen) with the value On
• ~/bin/wp: path to the WP CLI executable
• package install trepmal/wp-revisions-cli: the specific command to install the WP CLI package trepmal/wp-revisions-cli

This ensures that the allow_url_fopen option is enabled during the execution of the specified WP CLI command. Enabling allow_url_fopen may be necessary for certain operations that involve opening remote URLs, such as downloading extensions or packages. Make sure this option is enabled securely and in accordance with best security practices.

This guide explains how to specify a file that will be loaded before the desired page or at the beginning of each PHP script executed on your server, included as if it had been called with the function require(), but more globally using the PHP directive auto_prepend_file.

Preamble

• For example, to declare the headers of a website, you can create a file headers.php that contains PHP header() functions and that is prepended at the beginning of each PHP file…
  • … via a .user.ini file (specific to a folder),
  • … or via the site configuration in the Manager (global) as explained below.

Include a file globally from the Manager

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 Manage advanced settings:
   
4. Click on the PHP / Apache tab:
   
5. Complete the relevant line by entering the path of the file to include.
6. Click on the Save button at the bottom of the page:
   

After defining this directive, all PHP pages on your server will automatically include the specified file before executing their own code.

The headers defined in a .htaccess file are only valid for non-PHP (i.e., static) content.

Infomaniak uses php-fpm which receives the different headers via apache fast_cgi. In the RFC of cgi_www the header Strict-Transport-Security is not part of the headers passed via CGI and the Apache documentation confirms this. Refer to this other RFC.

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

Introduction

• 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 deprecated since 2021 and no longer allows you to install new packages or perform updates since 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, there is no need to install it manually.

Simple usage

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

composer

This command will automatically execute Composer version 2, which is compatible with the PHP version currently in use in your session.

Check the active version

You can check the available Composer version 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 PHP version, 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, which is useful for testing or deploying a project on a target PHP version.

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 explains how to enable or disable the set_time_limit PHP function for a Web Hosting service.

Introduction

• set_time_limit is a PHP function that sets the execution time limit for a script, in seconds; if this limit is reached, the script will stop and return a fatal error.
• set_time_limit cannot be used to set values exceeding the script execution time limit (max_execution_time) defined in the Manager.

Enable or disable the PHP set_time_limit function

To access the website management:

1. Click here to access the management of your website on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the website in question:
   
3. Click on Manage advanced settings:
   
4. Click on the PHP / Apache tab:
   
5. Click on the On/Off toggle button as desired:
   
6. Click the Save button at the bottom of the page to apply the changes.

This guide details the use of Crontab (crons via SSH), available only on Managed Cloud, by default (there is also a task scheduler for all hosting plans).

Prerequisites

• Script files called by cron must be executable (CHMOD).

Full path

Cron jobs do not have access to the absolute path. Calling PHP without specifying the full path to the executable makes it impossible to run the task. You must specify

/opt/phpX.X/bin/php

by replacing X.X with the desired PHP version (/opt/php8.1/bin/php for example).

Other operations

For example:

• List the cron jobs for the SSH user in question:

  crontab -l -u Username

• Edit the cron jobs:

  crontab -e -u Username

• Receive email notifications about the results of your cron jobs (add this to the beginning of the file):

  MAILTO=e-mail@domain.xyz

Restore a backup

Infomaniak backs up your cron jobs for the last 7 days (once a day). If you accidentally delete a cron job, contact Infomaniak support to request a restoration, specifying the time and date of the deletion.

This guide explains what the "MySQL Prefix" option is for in the parameters of a site and what its implications are for the operation of your web applications (CMS) and PHP scripts.

Preamble

• When the "MySQL Prefix" option is activated 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 activated by default in order to automatically maintain the connection of your web applications (WordPress, Joomla, Drupal, etc.) and PHP scripts with your MySQL databases.
  • In order to ensure the proper functioning of your sites in case of migration of your hosting to another server, it is strongly recommended to deactivate this function and make the adjustments it implies.

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 site on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the site concerned:
   
3. Click on Manage advanced settings:
   
4. Click on the PHP / Apache tab:
   
5. Activate or deactivate 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 deactivating the MySQL Prefix option for a site, some PHP scripts or CMS may no longer work.

In order to restore the connection to your databases, you will necessarily have to 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: dbname
  • after: wxyz_dbname
• The user of the MySQL database: you will need to add the prefix of your server
  • before: dbuser
  • after: wxyz_dbuser

This guide provides basic instructions for creating and using a .htaccess and .user.ini file with an Infomaniak Web Hosting account.

Introduction

• A .htaccess file is placed in the root directory of a website and allows you to configure the Apache HTTP server.
  • As a decentralized configuration file, it offers significant flexibility to adjust the server's behavior according to the specific needs of the site.
  • This file allows you to define URL rewrite rules, impose access restrictions, manage HTTP errors, and even customize security aspects such as disabling the display of files/folders.
  • It also facilitates the implementation of redirects and aliases, providing precise control over the organization and accessibility of the site.
• A .user.ini file allows you to customize the PHP directives for the folder (and its subfolders) in which it is located.
  • By acting at the PHP interpreter level, this file allows you to define specific configurations for a given folder and its subdirectories.
  • Thanks to its clear syntax, it offers the possibility of modifying various parameters such as memory limit, script execution time, error handling, and other PHP-related directives.
  • This granular approach allows developers to finely customize the behavior of PHP according to the specific requirements of each section of the site.

Create a file…

… .htaccess

1. Connect to your hosting account via FTP or SSH.
2. At the root of the website in question, create a new file and name it as follows: .htaccess.
3. Enter the desired directives in the file; refer to this other guide, for example.

… .user.ini

1. Connect to your hosting via FTP or SSH.
2. In the desired location, create a new file and name it as follows: .user.ini.
3. Enter the desired PHP configuration settings in the file.