Knowledge base

1000 FAQs, 500 tutorials and instructional videos. Here, there are only solutions!

Search

BIMI (Brand Indicators for Message Identification) is a standard that provides brand indicators for message identification) allows businesses to incorporate their logo into the emails they send.

 

Introduction

  • Infomaniak applications (and those of other companies worldwide - see the troubleshooting section below) are compatible with BIMI and will display logos next to received email messages.
  • Infomaniak Mail Services allow you to configure your email with your logo; the benefits are numerous:
    • increased trust: recipients can visually identify your emails, reducing the risk of phishing.
    • brand reinforcement: a clearly visible logo in inboxes strengthens brand awareness.
    • improved deliverability: emails that comply with DMARC are more likely to reach the main inbox.

 

1. Create a logo

Create a logo in SVG format (Scalable Vector Graphics). This format is required because it ensures optimal quality regardless of the device or display size.

To be imported into the Infomaniak interface (see below), it must not exceed 10 MB, but it can also be hosted on a secure server that is publicly accessible, and you will simply need to provide its URL for the BIMI DNS record.

 

2. Obtain the VMC certificate

A verified logo certificate (VMC) is required; it confirms that you are the legitimate owner of the logo. You can obtain this certification from recognized certification authorities such as DigiCert and Entrust.

When your VMC certificate is issued, you will receive a PEM file containing the entity's certificate. This PEM file includes your logo in SVG format as well as the VMC.

 

3. Add the logo to the Mail service

Prerequisites

  • All indicators Global Securityfor your Mail Service must be green (SPF + DKIM + DMARC)!

To access the Mail Service and define your company's logo:

  1. Click here to access the management of your Mail Service in the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the Mail Service in question.
  3. Click on Global Security in the left-hand menu.
  4. Click on the Create button (in the BIMI section):
  5. Fill in the requested information using the documents you received (see chapter 2 above) and don't forget to save.

 

In case of a problem

  • If the Create button in the BIMI box remains gray, carefully check the information messages: DMARC may exist but not be at the required rejection percentage, so adjust the settings according to the instructions.
  • When there are multiple domains linked to the Mail service, make sure you have a certificate on each linked domain if you want BIMI to be enabled on those domains.
  • Note that Apple Mail supports BIMI, unlike Microsoft Outlook, Thunderbird, and the Mail app from Samsung, which have not yet fully adopted it.

 

Disable BIMI

To disable BIMI, simply go to the domain name management page associated with the Mail service and delete the corresponding TXT record.


Has this FAQ been helpful?

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

 

Preamble

  • Some applications also allow changing the user password directly from their dedicated interface:
    • Example: WordPress (manage users, names, passwords, roles, etc.).

 

Change the password of a Web App

To change the password to access the administration panel of your web application, perform the following actions:

  1. Click here to access the management of your site on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the site concerned:
  3. Click on the action menu â‹® located to the right of the Web Application concerned.
  4. Click on Settings of the application:
  5. Click on Modify to the right of the Application:
  6. Under Password enter the new password (for the connection with the identifier indicated above).
  7. Click on the Save button at the bottom of the page:

Has this FAQ been helpful?

This guide explains what spamtrap email addresses are.

 

Introduction

  • A spamtrap, also known as a honeypot, is a tool used to detect and catch spammers.
  • It is essentially an email address or system that is created with the aim of attracting unwanted messages, such as spam.

 

How a Spamtrap Address Works

A spamtrap address works by attracting spam and identifying the senders of unwanted messages. Here's how this can happen:

  1. An email address is created specifically to act as a spam trap; it is generally configured in such a way that it does not receive legitimate communications.
  2. The spam trap address is hidden or obscured so that it is not visible to legitimate users, but only to spammers; this can be done by placing it on hidden web pages, in forums inaccessible to the public, or by making it invisible to humans (for example, by using white text on a white background).
  3. Spammers use automated techniques to extract email addresses from various sources, such as websites, forums, social networks, or stolen address lists; during this process, they may unintentionally or intentionally include spam traps in their lists.
  4. When a spammer sends a message to a spam trap address, it is captured and recorded; since the address is not used for legitimate communication, any email received is considered unwanted.
  5. When a spamtrap receives spam, it triggers an alert for email service providers like Infomaniak; these providers can then identify the spammer by examining the message headers or information related to the source IP address.
  6. Once a spammer has been identified through a spamtrap address, measures can be taken to block or filter their unwanted messages; Infomaniak can add the spammer's IP address to a blacklist, implement stricter anti-spam filters, or take other measures to protect its users.

Has this FAQ been helpful?

This guide details how to work on a WordPress site with a development environment.

 

Introduction

  • This process can be used at the beginning of a staging process, i.e., the creation of a new version of your website in a live environment, on a development or test environment:
    • This allows website owners to test features, security updates, plugins, themes, WordPress updates, and content changes without risking disruptions or problems on the live site.
    • Once the tests have been performed and the changes have been validated on the staging copy, it is possible to deploy them to production (on the live site) using automated deployment tools or by making the changes manually.

 

Simple method

To install and prepare a new WordPress site using the Infomaniak installer without overwriting your current website:

1. Install WordPress in a second location

Refer to this other guide to create the new website (in parallel with the existing website domain.xyz) by assigning it a domain name in the format new.domain.xyz, for example, and installing WordPress via Web Applications (Infomaniak WordPress installer).

At this stage, the main website (domain.xyz) remains unchanged, and you can work on the new website new.domain.xyz without any issues. Both websites will function in parallel.

2. Replace the old site with the new one

Once the new site is finished, you can delete the old site in order to reuse its domain name on the new site:

  1. Delete the old website to make the domain name available and allow you to reuse it.
  2. Add domain.xyz as an alias for new.domain.xyz.
  3. Reverse the alias with the main domain.
  4. Remove (unlink/delete) new.domain.xyz, which has become an alias.
  5. As a precaution, check the main URL of the WordPress site via the Web Applications dashboard in the Infomaniak Manager, to ensure that it corresponds to the new name and no longer to the subdomain you had chosen.

 

Advanced method

To work on an existing WordPress site without modifying its public version, it is recommended to proceed in 3 steps:

  1. Duplicate the existing site
  2. Then, work on your copy.
  3. Modify the target directory of the live site to the directory of the production environment, and update the URLs of the pre-production site based on the domain name of the live site, using a WordPress plugin or via phpMyAdmin.

1. Duplicate the website to a second location

  1. Refer to this other guide to create the new website (in parallel with the existing website domain.xyz) by assigning it a domain name in the format new.domain.xyz, for example, and installing WordPress using the Web Applications (Infomaniak WordPress installer).
  2. Copy your existing website and paste it onto the newly created second WordPress website, using a WordPress plugin.

2. Edit the duplicated website

  1. At this stage, the main site (domain.xyz) remains unchanged, and you can work on the new site new.domain.xyz without any issues. Both sites operate in parallel.
  2. It is recommended to install a WordPress extension (there are dozens available) dedicated to putting the second site into maintenance mode.
  3. If you modify the structure of your website and the URLs of your articles/pages change, you can use a free extension like Redirection to automatically create redirects. This will prevent your visitors from encountering 404 pages while search engines re-index your site or if external sites link to your site.

3. Replace the target

  1. Once you have finished redesigning your website, all you need to do is change the target directory of the site in production to the directory of the production environment and change the URLs of the pre-production site according to the domain name of the production site using a plugin.
  2. If you are using a caching plugin such as WP-Rocket, W3 Total Cache, or WP Super Cache, you will need to completely clear all the cache or disable and then reactivate the plugin.
  3. If you continued to make changes to your live site during the redesign, you will need to retrieve your changes (articles, media, pages, etc.).
  4. After performing the necessary checks (missing images, broken links, etc.), all that remains is to disable maintenance mode on your site and admire the result.

Has this FAQ been helpful?

This guide explains how to order a DNS zone from Infomaniak.

 

Introduction

  • Having your DNS zone with Infomaniak is useful if your domain name is registered elsewhere (with a third-party provider/registrar) and you want to easily link this domain to Infomaniak products.
  • Indeed, simply having a domain.xyz website with Infomaniak and specifying the 2 Infomaniak DNS addresses with the domain name registrar (if it is not Infomaniak) is not enough for the website to be displayed when you type domain.xyz in a browser.
  • You must add a DNS zone in the same location as your hosting to ensure your website functions correctly.
  • This will also be particularly useful if the provider managing your domain name does not offer DNS zone management.

 

Order a DNS zone

To do this:

  1. Click here to access the Infomaniak domain Shop.
  2. Start a search with the name of the domain registered elsewhere.
  3. Click on the action menu â‹® located to the right of the result.
  4. Select Order a DNS zone:
  5. Complete the purchase.
  6. Once added to your Manager, the zone can be edited.

Has this FAQ been helpful?

This guide details the software libraries that can be used to manipulate the PDF format and that are compatible with the various web hosting offers from Infomaniak.

 

Introduction

  • The PDF PHP extensions allow you, among other things, to generate a PDF from dynamic data, for example, to create custom invoices.

 

PDF and Cloud Server

On Cloud Server, you can install apps like PDFtk…

On shared hosting, ImageMagick is active and supports the EPDF, PDF, and PDFA formats.


Has this FAQ been helpful?

This guide explains how to view and download Apache logs for Web Hosting, which are useful for analyzing PHP errors or diagnosing certain application behaviors.

 

Introduction

  • Access and error logs are kept for at least 7 days.
  • Once the retention period has elapsed, older entries cannot be restored, even upon request.
  • You can also find these files directly on the server via SSH/FTP in the ik-logs folder at the root of your hosting.

 

Accessing access and error logs

To view these logs:

  1. Click here to access your website management in the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the site in question:
  3. Click on Advanced in the left-hand sidebar.
  4. Click on Logs in the left sidebar.
  5. Click on Errors or Access to view the error log or access log.
  6. Select a period if necessary.
  7. Click on the icon to view the details.
  8. Click on Send by email to immediately receive all entries by email at your user address.
  9. Click to export the data in .log format:

 

Identify the most active IP addresses in the access logs

To do this, connect to the server via SSH (need help?).

The command to execute via SSH is as follows:

cat ik-logs/access.log | awk '{ print $2}' | sort -n | uniq -c | sort -n | tail -n 20

Has this FAQ been helpful?

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.

Do not forget to save the changes at the bottom of the page.

 

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


Has this FAQ been helpful?

This guide explains how to install a new Infomaniak WordPress site included in the paid Web Hosting offers. You will find 2 different ways to create a WordPress site as well as explanations about uninstallation.

 

Create a WordPress site on an existing hosting

To access Web Hosting and add a new site by installing WordPress at the same time:

  1. Click here to access the management of your hosting on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the hosting in question:
  3. Click the button to add a site:
  4. Choose to install WordPress.
  5. Click the Next button:
  6. Click the button to use a domain name already present in your Organization (or on the other button if you need to order a new domain first).
  7. Select the domain name from your already acquired domains.
    1. The advanced options allow you to choose a custom location on the hosting server, and an older version of PHP.
  8. Click the Next button:
  9. Wait a few minutes for the site to be created on the hosting:
  10. Enter the requested information, it will be used to log in to the WordPress dashboard (it is possible to modify this information at any time after installation).
  11. Click the Next button:
  12. Enter the information related to your site (it is possible to modify this information at any time after installation).
  13. Click the Next button:
  14. Choose between the Divi theme and the official theme of the latest WordPress version (it is possible to modify this information at any time after installation).
  15. Click Next:
  16. Choose to install or not two Premium extensions offered with your subscription: Monarch and Bloom.
  17. Click on Next:
  18. Confirm the installation from the summary page:
  19. You can then log in to the WordPress dashboard or return to the Infomaniak site management:

 

Install WordPress on an existing blank site

To access the existing blank site on the hosting and install WordPress:

  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 the button to add an application:
  4. Choose to install WordPress:
  5. Click the Next button at the bottom of the page.
  6. Enter the requested information, it will be used to log in to the WordPress dashboard (it is possible to modify this information at any time after installation).
  7. Click the Next button:
  8. Continue as from point 12 of the previous chapter above.

 

Uninstall Infomaniak WordPress

You can delete a WordPress site:

  1. by completely removing the website from the hosting (and keeping or not the WordPress data, databases, etc.)
  2. by keeping the website on the hosting but removing the WordPress app…

 

Option 1

  1. Click here to access the management of your WordPress site on the Infomaniak Manager (need help?).
  2. Click on the action menu â‹® located to the right of the item concerned.
  3. Click on Unlink the site:
  4. Choose whether you want to delete everything or keep a trace of the WordPress data on the hosting server anyway:
     
    1. If you check the box, there will be nothing left in the Manager (except backups):

      and nothing left on the server:
    2. If you do not check the box, there will be nothing left in the Manager (except backups):

      but the WordPress files will still be accessible on the server:

      And you will get an error if you later try to reinstall a new WordPress site in the same place with the same domain name:
  5. Confirm the deletion.
  6. Click to delete and wait.

 

Option 2

  1. Click here to access the management of your WordPress site on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the site in question:
  3. Click on the action menu â‹® located to the right of the item concerned.
  4. Click on Delete the app:
  5. Confirm the deletion and wait, your hosting will still contain a site but without an installed application:

 

Learn more


Has this FAQ been helpful?

This guide explains how to disable all extensions installed on your WordPress on a Web Hosting.

 

Preamble

  • Disabling WordPress extensions allows you to quickly identify if one of them is causing an issue on your site, and thus draw the necessary conclusions to fix it.
  • If you encounter a problem with third-party software, contact its publisher or a Partner and consult the support policy as well as article 11.9 of the Infomaniak Terms of Service.

 

Quickly disable WP extensions

To disable all WordPress extensions:

  1. Connect to the server via FTP (need help?).
  2. Go to the site location (folder corresponding to your WordPress site).
  3. Rename /wp-content/plugins to /wp-content/_plugins for example.
    • To disable a specific extension, rename /wp-content/plugins/PluginName to /wp-content/plugins/_PluginName for example.

Has this FAQ been helpful?

This guide explains how to connect via SSH to a Web Hosting or a Cloud Server.

 

Connecting via SSH…

 

… via a web browser

  1. Click here to access the management of your web hosting on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the hosting in question:
  3. Click on FTP / SSH in the left-hand menu.
  4. Click on the SSH Console button:

 

… via the terminal or an application

To connect via SSH, use the following commands from a Terminal application (command-line interface, CLI) on your device, for example:

  • Terminal (an application already integrated into macOS and Linux)
  • PuTTY (Windows)
  • Windows 10 SSH client (help in French / in English)

Then, enter the following command:

ssh username@server
  • username is the username of the FTP account
  • server is the host server (e.g. xxxx.ftp.infomaniak.com)

 

To find out which command is available and to know the path to use, run the "whereis" command:

$ whereis mysql
mysql: /opt/mysql/bin/mysql

Has this FAQ been helpful?

This guide explains how to import a MySQL/MariaDB database to an Infomaniak Web Hosting account.

 

Importing a database

To import a database into Infomaniak:

  1. Click here to access the management interface for your product in the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the product in question:
  3. Click on the chevron ‍ to the right of the database menu in the left-hand sidebar.
  4. Click on Databases.
  5. Click on the “More actions” button/menu to access different options.
  6. Choose Import a database:
  7. You will then have the following options:
    1. upload your database directly (sql, gz, bz2, zip, 300 MB max) from your computer,
    2. select the file to import from your hosting account after uploading it to the server via FTP,
    3. choose a backup from those that are created automatically.
  8. you can also choose:
    1. import the data into a new database (creation),
    2. import into an existing database (replacement/overwrite).

Warning: a MySQL/MariaDB import following an export requires action on your part if you use TRIGGERS/VIEWS: please refer to this other guide!

 

Alternative method (SSH - for advanced users)

Prerequisites

To import via SSH:

  1. Upload the database to be imported via FTP to your hosting.
  2. Open an SSH terminal/console,
  3. From a Terminal-type application (command-line interface, CLI) on your device, for example the PuTTY application (to be downloaded and installed on Windows) or Terminal (installed by default on macOS), run and adapt the following command:
  4. ssh ftp-user@server-address
  5. Enter the password for the FTP + SSH account.
  6. Enter and adapt the following command:

    mysql --verbose -u db-user -p db-name -h db-host < path
    • replace db-user with the database username (e.g. abcd_user)
    • replace db-name with the database name (e.g. abcd_sample)
    • replace db-host with the MySQL server for your hosting
    • replace path with the path where you uploaded the database in step 1 of this procedure (if you have a single website stored in the default location, the path would be, for example, ~/web/test.sql)
  7. Wait for the import to complete (this may take several minutes depending on the size).

Has this FAQ been helpful?

This guide explains how to add a new domain name to a website on Infomaniak.

 

Introduction

  • When you add a new domain name to a website, it is referred to as a linked domain, but also as an alias.
  • In this case, a domain alias is an additional domain name that is also linked to an existing website.
    • For example, to make the website domain.xyz accessible with a completely different domain name like private.abc, you need to add private.abc as an alias to the website.
    • Second example, to make the website domain.xyz also accessible with www.domain.xyz, you need to add it as an alias to the domain domain.xyz. In this example, domain.xyz is the parent site of the alias www.domain.xyz. In general, the www alias is already added automatically and is present…

 

Add an alias to an existing website

Prerequisites

To add an additional domain that will be linked to your website:

  1. Click here to access the management of your website in the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the website in question:
  3. Then, click on the Add a domain button:
  4. Enter the domain name(s) to add, separating them with the Enter key.
  5. If the alias or its DNS zone is managed by Infomaniak, it is possible to automatically update the DNS entries. Otherwise, make any necessary changes with your registrar or transfer the domain name management to Infomaniak.
  6. If you have an SSL certificate, such as Let's Encrypt, you can request to update it here to include the new names.
  7. Click on Validate to complete the process:
  8. The domains linked to the website are updated:

To define the alias as the main domain, please refer to this other guide.


Has this FAQ been helpful?

This guide explains how multi-site web hosting works, both from a technical and administrative perspective.

Technical operation

A web hosting plan can group several websites:

  • In this case, the resources of this hosting plan (disk space, databases, memory, etc.) are shared among all the sites it contains.

With a Cloud Server, you have a larger infrastructure:

  • For example, a standard plan may include 5 hosting plans and allow you to create up to 20 websites. You are free to distribute these 20 websites across your 5 hosting plans as needed.

 

Access management

In the Infomaniak Manager, access rights apply to the hosting plan as a whole:

  • It is not possible to limit a user's access to a single website: if they are invited to a hosting plan, they will have access to all the sites it contains.

However, to restrict access to a single site, you can use these alternatives:

  • On the server: create an FTP user and limit their access to only the specific website folder.
  • On the website itself: manage rights and access directly from your website creation system (for example, with WordPress role management).


Has this FAQ been helpful?

This guide explains how to access MySQL/MariaDB backups and restore a specific database from an Infomaniak hosting.

 

Restore a specific database

To access Web hosting:

  1. Click here to access the management of your product in the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the corresponding product.
  3. Click on Restore in the left sidebar menu.
  4. Choose the type “Advanced Restore” which allows you to choose the databases to restore.
  5. Click the Next button:
  6. Choose the desired restore date and click the Next button:
  7. In the Databases section, choose the database(s) to restore (closest date indicated on the right) and click the Next button:
  8. Choose (if offered) how to re-import the content and click the Restore button:
  9. Confirm the re-import method and its implications:
  10. You will receive an email when the operation is complete.

Has this FAQ been helpful?

This guide explains how to redirect all visitors to a secure https version (SSL) of a website on Infomaniak's Web Hosting.

 

Introduction

  • This redirection is generally automatic with a standard configuration and installation.

 

Manual redirection via the .htaccess file

Prerequisites

  • You must have a valid and functional SSL certificate for the Infomaniak website.

Next, modify or add the following three lines to the .htaccess file of the website in question so that all its visitors automatically access its secure https version:

RewriteEngine on
RewriteCond %{HTTPS} off
RewriteRule (.*) {{URL_1}} [R=301,L]

Replace domain.xyz with your domain name and the appropriate extension (.com, .fr, .ch, etc.).

If you encounter any issues, replace the second line of the code above with RewriteCond %{HTTP:X-Forwarded-Proto} !https.

 

With a CMS

Most web applications, such as WordPress and Joomla, have extensions/plugins that automatically redirect visitors to a site's secure https version.

WordPress

If you are using a content management system (CMS) such as WordPress to create your website, it is recommended to install an extension to perform this redirection:

  1. Back up the website's files and database as a precaution.
  2. Install the Really Simple SSL extension or a similar one from the WordPress console and activate it.
  3. Visitors are now automatically redirected to the https version of the site.

Joomla

Replace domain.xyz with your domain name and the appropriate extension (.com, .fr, .ch, etc.).

  1. Find the line

    var $live_site ='';

    in the Joomla configuration file (configuration.php) on the server.

  2. Replace it with

    var $live_site = '{{URL_3}}';
  3. Add three lines to your .htaccess file on the server:

    RewriteEngine On
    RewriteCond %{HTTPS} OFF
    RewriteRule (.*) {{URL_4}}
  4. Open the Joomla administration panel under "System - Configuration".
  5. Click on the "Server" tab and, under "Force SSL", choose "Administration and site".
  6. Save, and visitors will now be automatically redirected to the https version of the site.

Prestashop

  1. Access the general settings in the Prestashop back-office to enable SSL:
    1. < v1.7 click on "Preferences" then on "General"
    2. > v1.7 click on "Shop Parameters" then on "General"
  2. Set the "Enable SSL" toggle switch to "YES".
  3. Click "Save".
  4. On the same page, set the "Enable SSL for the entire site" toggle switch to "YES".
  5. Click on "Save".

If a security padlock does not appear in the browser or a warning is displayed, the issue may lie with the template or modules, as they are sometimes not fully compatible with SSL. Your Prestashop may then load elements (images, .css or .js files, fonts, etc.) using "http" instead of "https", as it should.

Drupal

Read this article (in English) which explains how to migrate a Drupal website from http to https.

 

Alternative solutions

Replace domain.xyz with your domain name and the appropriate extension (.com, .fr, .ch, etc.).

In your .htaccess file, to force the site URL to be https:// but without www:

RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www. [NC]
RewriteRule (.*) {{URL_6}} [R=301,L]

In the case of a redirection loop, adapt the code above as follows:

RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https [OR]
RewriteCond %{HTTP_HOST} ^www. [NC]
RewriteRule (.*) {{URL_7}} [R=301,L]

In your .htaccess file, to force the redirection with www:

with subdomains:

RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www. [NC]
RewriteRule (.*) {{URL_8}} [R=301,L]

In the case of a redirection loop, adapt the code above as follows:

RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https [OR]
RewriteCond %{HTTP_HOST} !^www. [NC]
RewriteRule (.*) {{URL_9}} [R=301,L]

and without the subdomains:

RewriteEngine on
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^domain.xyz [NC]
RewriteRule (.*) {{URL_10}} [R=301,L]

In the case of a redirection loop, adapt the code above as follows:

RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https [OR]
RewriteCond %{HTTP_HOST} ^domain.xyz [NC]
RewriteRule (.*) {{URL_11}} [R=301,L]

 

Common errors after an HTTPS redirect

To resolve common issues that may arise after redirecting your website to its secure HTTPS version, please refer to this other guide.


Has this FAQ been helpful?

Supervisor is not offered directly because systemd is recommended, better integrated with Debian, and available in Fast installer.

If you still need to install it, contact Infomaniak support in writing.


Has this FAQ been helpful?

This guide explains how to install a new Web Application (Joomla, Drupal, Typo3, PrestaShop, etc.) in a few clicks on paid Web Hosting offers.

 

Prerequisites

 

Specific guides

Refer to these guides if you are concerned with the specific installation of:

Refer to this other guide regarding additional technologies that can be installed in a few clicks but on Cloud Server only.

 

Guides for any other Web Application

To access Web Hosting and install a Web Application:

  1. Click here to access the management of your product on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the product concerned.
  3. Click on the button Add an app:
  4. Choose the desired application (if necessary, filter and search).
  5. Click on Select:
  6. Click on Next at the bottom of the page:
  7. Enter a name.
  8. Leave the default location or choose to install the app in a new folder that you can create using an icon visible to the right of point 8 in the image.
  9. Optionally, choose to install an older version if necessary.
  10. Click on Next:
  11. Set up username and password.
  12. Specify certain advanced settings if necessary (backup type in particular).
  13. Read and accept the terms of use of the selected app.
  14. Click on Next:
  15. Confirm the installation of the application in the next step and wait:
    • Take note of any error messages on the screen if, for example, the selected installation folder is not empty or if the PHP version of the site on which you are attempting the installation is not compatible.

 

Uninstall a Web Application

To access Web Hosting and uninstall the previously installed application:

  1. Click here to access the management of your product on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the product concerned.
  3. Click on the action menu â‹® located to the right of the application to be uninstalled.
  4. Click on the trash can icon to delete the application:
  5. Confirm the deletion.

Conversely, you can also remove an entire site without deleting the application itself; simply do not check the following box when deleting the site:

 

Learn More


Has this FAQ been helpful?

This guide explains how to add a MySQL/MariaDB database, create or modify users, and how to find all the necessary parameters to configure your scripts and CMS on a Web Hosting.

 

Manage databases

To access the database management page of your hosting:

  1. Click here to access your hosting management on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the hosting concerned.
  3. Click on Databases (or MariaDB if necessary) in the left sidebar to access the Databases and Users menu:

 

Databases

Under the Databases tab you can:

  • Create a MySQL/MariaDB database by clicking on the Add a database button.
  • Import, export or restore a MySQL database by clicking on the dropdown ‍ to the right of the Add button.

 

Users

Under the Users tab you can:

  • Create a MySQL/MariaDB database user by clicking on the Add a user button.

 

Configuration information

This is also where you will find the required information to configure CMS or Web applications:

  • The name of a database (e.g. XXXX_dbname)
  • The username of a database (e.g. XXXX_username)
  • The password of the username of a database (the one you chose when creating the MySQL/MariaDB user to reset if you forgot it)
  • The MySQL/MariaDB server of the databases / the hostname (e.g. XXXX.myd.infomaniak.com) with its version (5.7 for example)

 

User rights, shared servers & Cloud

  • With read permissions: “SELECT”
  • With write permissions: “INSERT, UPDATE, DELETE, CREATE TEMPORARY TABLES, LOCK TABLES”
  • With admin permissions: “CREATE, DROP, INDEX, ALTER, CREATE VIEW, SHOW VIEW, REFERENCES”
    • + “CREATE ROUTINE, ALTER ROUTINE, EXECUTE, TRIGGER, EVENT” on Cloud Server only (see this other guide on this subject)
  • With no permissions: the user will not see the database appear in phpMyAdmin

 

Web application databases


Has this FAQ been helpful?

This guide explains how to manage the content of a Web hosting by accessing the server, particularly via the FTP protocol or through command line (CLI) securely using SSH.

 

Preamble

  • To easily and quickly manage the files of your Web hosting without having to install an application or enter FTP credentials, use Web FTP from your Infomaniak Manager (it allows, among other things, CHOWN and file compression/decompression zip).
  • When creating a website via Apache/PHP hosting, an FTP/SSH/SFTP user is automatically created; you can create additional FTP accounts.
  • However, in the case of a Node.js site, no SSH/SFTP user is automatically created; it is necessary to manually create a user with SSH/SFTP rights to access your Node.js environment.
  • Regarding the protocols supported by Infomaniak (FTP, SFTP, etc.) depending on your hosting offer (Starter, Node.js, etc.), refer to this other guide.

 

Create an FTP account

To access Websites to manage the FTP part:

  1. Click here to access the management of your hosting on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the hosting in question:
  3. Click on FTP / SSH in the left sidebar.
  4. Then either you click on the Add button to create a new FTP/SSH account…
  5. or you click on the action menu â‹® to the right of an existing account to change its password, or delete it:
  6. If you have a node.js site on your hosting, you need to choose the desired environment for creating a new FTP/SSH account:
  7. Then enter the desired information:
    1. An FTP + SSH account gives the user in question access to all the content of a hosting and allows them to manage it via FTP/SFTP and SSH.
    2. An FTP account allows you to restrict a user's access to a folder and its subfolders; if you manage multiple sites on the same hosting, this allows you to distribute site management among multiple webmasters, for example.
  8. Click the button at the bottom of the page to Confirm the creation of the account:

 

Configure an FTP software/client

Using an FTP software/client like Filezilla or CyberDuck, manage files actually via FTP without limit (possibilities of background work, resumption of transfers after disconnection, bandwidth limitation, etc.).

Refer to this other guide if you are looking for information about configuring an FTP software/client.


Has this FAQ been helpful?