This guide explains how to modify the automatic backup configuration for Infomaniak Web Applications (Joomla, Drupal, Typo3, PrestaShop, ownCloud, etc.) included in the paid Web Hosting offers.

Preamble

• This does not apply to WordPress, which can be backed up and then restored via:
  • the automatic backup of hosting,
  • extensions allowing you to manually back up everything, including an easy reinstallation file.

Set up backups

To manage the backups of the Apps:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product:
   
3. Click on the action menu ⋮ located to the right of the relevant Web Application.
4. Click on Settings for the application:
   
5. Click on Edit to the right of the Application:
   
6. Under the Configuration tab, click the box to access advanced configuration:
   
7. Choose the desired update and backup modes:
   • 7 recent backups are kept, as well as those from 15 and 30 days ago.
8. Save the changes using the button at the bottom right.

Learn more

• Install or uninstall a Web Application
• Change the domain name associated with the Web Application
• Restore a Web Application

This guide explains how to launch a content analysis of a Web Hosting to detect and clean files containing viruses and other malicious scripts that could threaten the security of websites.

Start an antivirus scan of the sites

To analyze potentially infected content:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on Security in the left sidebar.
4. Click on Antivirus in the left sidebar.
5. Click the blue button Analyze:
   
6. Select the site(s) to analyze.
7. Click on the blue button Start the analysis.

Also consider the vulnerability detection tool to monitor potential vulnerabilities that are automatically fixed on your websites.

This guide explains how to restore backups of previous versions of your files and other web data from your Infomaniak hosting, and how to implement an effective backup policy if the backups automatically and freely provided no longer meet your availability or security needs.

Web Hosting (Starter, Shared, Cloud Server)

Check out these guides to restore automatic backups:

• of an entire hosting (FTP + MySQL),
• of specific files on the hosting
• of specific databases,
• of a Web Application (Wordpress & Apps),
• the SSH crons of Serveur Cloud.

Check out these guides to backup and restore:

• a hosting with Swiss Backup and Acronis (simple),
• a hosting with Swiss Backup and Restic (advanced),
• WordPress with Swiss Backup,
• WordPress with an extension.

Also, refer to https://faq.infomaniak.com/snapshot.

Hostings v1 (old 60 Go offer)

• View and/or download the automatic backup (versioning) of your data on your FTP space under /backups and /backup_mysql at the root of the domain (above /web).
• Restore this data.

Mail

• Restore messages from automatic Infomaniak backups.
• Restore contacts or calendar events.
• Save the current content of an email account:
  • by downloading the current content locally,
  • by duplicating all current content to a backup mailbox,
  • by copying future emails as they arrive to a backup box.

Domains / DNS Zones

• Restore deleted DNS records from automatic Infomaniak backups.
• Restore an expired domain in redemption period.

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

Preamble

• On a shared Web hosting, it is only possible to open ports for outgoing traffic.
• On a Cloud Server, it is possible to open ports for inbound and outbound traffic.
• Opening ports ensures the proper functioning of certain applications but may decrease the security of your hosting.

Access the tool and add a rule

To manage port opening from the Manager:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on Security in the left sidebar.
4. Click on Port Opening in the left sidebar.
5. Click on the Open a port button:
   

It is only possible to enter one IP address or host per line, and one port per rule.

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

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

Same goes for the Typeof connection, if the protocol used for the connection is not the one indicated in the rule, the connection is not allowed.

Open outbound port 25 globally

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

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

Default open ports

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

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

The display may sometimes span multiple pages:

MySQL Ports

Regarding database ports, refer to these guides:

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

Check the activity of a port (Cloud Server)

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

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

This guide explains how to optimize the site you manage on a Web Hosting to make it faster and allow all visitors to browse it from the Internet without difficulty, regardless of their connection speed.

The role of the hoster

1. … your hosting server is functioning normally and has not encountered any issues in the last 48 hours.
2. … the network infrastructure has not experienced any disruptions in the last 48 hours.

The role of the site owner and the webmaster

Infomaniak does not intervene in the content of the servers or the development of websites. The creation or maintenance of a site is a different job, although it is related to its activities since the tools and services that a webmaster uses to create websites are offered.

Analyzing the cause of slowdowns

Here is what you should do if you notice slowness with your site:

1. Follow the Google PageSpeed Insights recommendations to optimize your website... The points highlighted concern the design of the website and not the server configuration; refer to this other guide if the test result suggests enabling resource compression on your site.
2. In case of slowness from abroad, consider activating DNS Fast Anycast.
3. Install and configure a cache system on your site to avoid redundant access to databases and speed up the display of your site.
4. Consider a CDN.
5. Test the server's response speed (TTFB).
6. Scan your hosting for viruses.
7. Purge the databases regularly and delete unnecessary entries.
8. Use the latest PHP version compatible with your site/CMS/Web application.
9. Avoid using images, counters, CGI, or media hosted by external providers, as if they are unreachable, your site will seem slow.
10. Disable any unnecessary WordPress extensions that consume a lot of resources in your CMS.
11. Keep your CMS/Web applications up to date regularly.
12. Implement a crawl delay for indexing bots, as some have a very "aggressive" operation; it is possible to limit their impact by implementing a Crawl-delay.
13. Check the possible error-logs which group all the errors generated by your site; by correcting these errors, your site will be more performant.
14. Check the slowlogs: they group the queries that take more than 5 seconds to execute; it is important to correct the queries listed in this file (SQL optimization examples).
15. Add a server cache system like Memcached (Cloud server only).
16. Increase the max_children value (Cloud server only).

If a problem persists...

As a site owner, if you are a webmaster or have hired a webmaster who also cannot find the cause of the slowness, contact Infomaniak support in writing only after obtaining the following information:

1. Hosted site name.
2. Dates and times when slowness was encountered.
3. Name of the database potentially involved / same for FTP account.
4. Your public IP address at the time of the tests (visible for example on https://www.infomaniak.com/ip).
5. Type of slowness observed (site display, FTP transfers...).
6. Issues (such as slowness) accessing the Infomaniak site intermittently?
7. Result of a traceroute to 84.16.66.66 and copy-paste the complete results (screenshot if necessary).
8. Result of a speedtest by choosing Infomaniak as the destination (speedtest.net — click on Change Server to select Infomaniak).

If your needs skyrocket…

If shared hosting no longer suits your site, you should consider moving to a Serveur Cloud. Your site can be easily moved to this type of server where it will be alone and on which you can install a cache engine, for example.

This guide explains why a website may be "broken" or stop displaying anything, following a password change at the level of a Web Hosting.

Broken link with the database

When your website, and more specifically a script (CMS, WordPress, Prestashop or any other application using MySQL databases), can no longer connect to the MySQL MariaDB or other database, an error message may display, such as:

• Erreur lors de la connexion à la base de données
• Database Error: Unable to connect to the database:Could not connect to MySQL
• Link to database cannot be established

Remember your last action…

In case an error occurs on your site, you should always examine the recent history. In this case, has there been…

1. … an action on your part regarding the configuration file of the script in question? Has it been altered, modified, or moved?
   
   Sometimes, the unintentional insertion of a space before or after a word can sever the connection between the web server and the database server. Go back and review your file modifications.
   If necessary, restore an older version of the files that you recently modified.
    
2. … an action regarding the database password in the Infomaniak Manager?
   
   If you change the password of your database via the Infomaniak Manager, then your script, which retrieves its information from the databases, will no longer display anything.Changing something in the Infomaniak Manager means you have to change it everywhere else. This change that you made in the Manager, you also need to report / reflect it in the configuration file of the script by connecting via FTP and going to modify the appropriate file, usually "wp-config.php", "configuration.php" or similar.
    
3. … a server move announced by Infomaniak?
   
   If this error follows a server move or another operation announced by email and related to the product in question, do not hesitate to contact Infomaniak support.

Infomaniak's Node.js sites allow you to run Node.js applications in a flexible, ready-to-use environment, without having to manage server infrastructure.

Preamble

• Offering the flexibility of a server without the complexity of its administration, this type of hosting is particularly suitable for API REST projects, for deploying the CMS Ghost, Strapi or frameworks like Express.js, NestJS or socket.io, next.js, business tools or prototypes for:
  • developers wanting to deploy Node.js applications without managing infrastructure.
  • webmasters looking to experiment with or learn Node.js.
  • agencies and freelancers working on multiple client projects.
  • students, teachers and schools needing a simple environment to test code.
• Package managers NPM and Yarn are supported.
• If you install Node.js on a Web hosting within a Server Cloud, your site will not work with the guaranteed resources of the managed Server Cloud.
  • Refer to this other guide to use Fast Installer and deploy NVM.
• Node.js = official name of the language/environment; NodeJS = technical or simplified name in certain contexts (often for practical reasons, no real technical difference).

Create a Node.js site

To access a web hosting plan and add a Node.js site:

1. Click here to access the management of your products in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on the blue Add button:
   
4. Choose a project with advanced technologies.
5. Click on Next:
   
6. Choose Node.js.
7. Select another version if necessary.
8. Click on Next:
   
9. Choose the domain type to assign to this new site:
   1. an already acquired domain name
   2. a subdomain created from an already acquired domain name
   3. an available domain name and to order
10. Enter the domain name or subdomain.
11. Choose the advanced options if applicable.
12. Click on Next:
    
13. Choose one of the two possible approaches:
    
    1. Quick method:
       1. A pre-configured example project is automatically installed.
       2. This approach is ideal for discovering Node.js or quickly starting a functional base.
    2. Custom method:
       1. The source code can be imported via Git, ZIP archive, SSH or SFTP.
       2. You define the scripts, entry points, listening port, and necessary build commands yourself.
14. Each site has a dedicated control panel to manage the application (start, stop, restart), view the execution console, manage Node.js versions, configure domains and activate SSL certificates:
    

To go further in the configuration of your Node.js site, refer to this other guide.

This guide helps you understand the error "Your Connection Is Not Private" when you try to access a website, whether you are the site owner or a simple visitor.

Understand the error

The error "Your Connection Is Not Private" sometimes appears in your browser when it has trouble establishing a secure connection with the site you are trying to visit. This usually happens when the website does not have a valid security certificate and does not use the SSL/TLS protocol to protect communication between the site and your web browser.

In fact, this is a security measure aimed at protecting your data. Websites with invalid SSL certificates may have security issues, making them less reliable. They can also expose your personal information to hackers if you enter sensitive data, such as your login credentials or payment information.

If you are a visitor

This may be due to configuration errors, such as an insecure Wi-Fi connection, incorrect date and time on your computer, or even an SSL/HTTPS analysis by your antivirus software.

If you own an Infomaniak website

Have you installed an SSL certificate?

Learn about the different certificates available on the Infomaniak site.

And if you already have an SSL certificate for your site, have you updated it to include any potential site aliases?

Check the SSL certificate expiration date

Certificates are renewed automatically. To check the expiration date:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Check the column containing the expiration dates:
   

Check the installation

If you think you have activated SSL on your site, check a few points in this other guide.

Infomaniak takes pride in securing data through a comprehensive and diverse approach to security. For whistleblowers, the company has implemented an internal system that allows irregularities to be reported safely and anonymously, without fear of reprisals. This protection mechanism is known and accessible to all employees, thereby strengthening transparency and accountability within the organization.

Infomaniak demonstrates its commitment with concrete and effective measures to protect those who report anomalies.

This guide explains why it is dangerous to use a PHP version that is no longer officially maintained and how to use a more recent PHP version with a website hosted by Infomaniak.

Is an outdated version of PHP dangerous?

When you use a (soon to be) vulnerable version of PHP on one or more of your sites, a warning message appears in the dashboard of the affected hosting services.

The PHP language evolves regularly and when you use a PHP version that is no longer updated, you expose your website to security risks. Malicious individuals could, for example, exploit known security vulnerabilities to gain access to your site and alter its content. It is therefore strongly recommended to always use a recent version of PHP.

Three statuses are possible:

• The PHP version is fully supported‍: no action is required
• The PHP version only receives security updates‍: it is recommended to use a more recent version of PHP
• The PHP version is no longer updated‍: it is strongly recommended to use a more recent version of PHP

Learn more: http://php.net/supported-versions.php

Using a more recent version

The latest versions of PHP are more performant and speed up website loading.

Before using a more recent version of PHP, it is necessary to take the following precautions:

• If your site runs on a CMS or a web application (WordPress, Joomla, Drupal, etc.), it is recommended to check that its current version is compatible with the PHP version you plan to use
• If your site was developed manually, it is necessary to consult the official PHP documentation to learn about modified functions and potential incompatibilities

If you encounter issues after migrating a site to a newer version of PHP, it may be possible to revert to a previous version of PHP if it is still supported.