This guide concerns the WordPress module "Infomaniak Connect for OpenID" which allows users to log in to your WordPress site (whether it is hosted by Infomaniak or not) using their Infomaniak credentials.

Preamble

• Allowing login via an Infomaniak account on your WordPress site allows your visitors to comment, register for courses, or access any member-only content with a single click, without having to create a new account.
• It saves them time and is a safer method for you, as you do not have to manage additional passwords.
• The operation of this external module is identical to the options "Log in with Google", "Log in with Facebook" or "Log in with Apple"; it uses the standard OAuth2 and OpenID Connect protocols to enable single sign-on (SSO).

A. Create an application with Auth Infomaniak

To do this:

1. Click here to access the management of your Auth product on the Infomaniak Manager (need help?).
2. Click the button to Create a new application:
   
3. Choose the type "Web Front-End".
4. Give a name to your application.
5. In the URL field, indicate the domain name corresponding to your WordPress site followed by /openid-connect-authorize (refer to the GitHub documentation if necessary).
6. Click the button to complete the app creation:
   
7. Carefully note the 2 pieces of information obtained when finalizing your OAuth2 application:
   

B. Configure the WordPress extension

To do this:

1. Search for the extension Infomaniak Connect for OpenID on the WordPress extensions platform from your site.
2. Install and activate the extension:
   
3. Configure the extension from the Settings menu:
   
4. The only fields to fill in are Client ID and Client Secret Key and come from the information obtained in point A above:
   
5. Do not forget to save the changes made to the extension settings.
6. An additional button for logging in with an Infomaniak identifier is now visible on your login page for users /wp-admin (/wp-login.php):
   

This guide helps to solve a problem on the Prestashop CMS and more specifically with its “Faceted Search” module that allows the management of filters in the product category pages.

The problem

This specific search module of Prestashop creates a cache in the database to speed up the search, however the corresponding table is never cleaned, which poses a problem for the hosting infrastructure.

First solution

The first solution is to disable the proposed caching.

To do this:

1. In the PrestaShop administration panel, go to Modules → Module Manager.
2. Select Modules and use the search field to find “facet”.
3. Click on Configure next to the module obtained in the result:
   
4. Disable the button for this:
   

Second solution

The second solution is to set up a cron job to clean the table, for example every night:

1. From the module settings, copy the existing URL on the Clear cache button:
   

Then from the Infomaniak Manager, create a webcron (refer to this other guide on this subject) to execute the URL copied in point 1 above, for example 1 time per day and per night.

This guide concerns the Typo3 module "t3ext-infomaniak-auth" which allows users to log in to your Typo3 site (whether it is hosted by Infomaniak or not) using their Infomaniak credentials.

Preamble

• Allowing login via an Infomaniak account on your Typo3 site enables your visitors to comment, register for courses, or access any member-only content with a single click, without having to create a new account.
• This saves them time and is a safer method for you, as you do not have to manage additional passwords.
• The operation of this external module is identical to the options "Sign in with Google", "Sign in with Facebook" or "Sign in with Apple"; it uses the standard protocols OAuth2 and OpenID Connect to enable single sign-on (SSO).

A. Create an application with Auth Infomaniak

To do this:

1. Click here to access the management of your Auth product on the Infomaniak Manager (need help?).
2. Click the button to Create a new application:
   
3. Choose the type "Web Front-End".
4. Give a name to your application.
5. In the URL field, enter the domain name corresponding to your Typo3 site followed by /openid-connect-authorize (refer to the GitHub documentation if necessary).
6. Click the button to complete the app creation:
   
7. Carefully note the 2 pieces of information obtained during the finalization of your OAuth2 application:
   

B. Configure the Typo3 extension

Via SSH, deploy Composer if necessary to retrieve the t3ext-infomaniak-auth extension. To do this:

• The SSH command for installing the extension is here:
  • https://packagist.org/packages/infomaniak/t3ext-infomaniak-auth 

Then, in Typo3:

1. Log in to your Typo3 admin interface.
   • Check if necessary that the Infomaniak extension is activated:
     
2. Click on Settings in the left sidebar menu.
3. Click on Configure extensions:
   
4. Click on the chevron ​ to the right of typo3-openid-main to expand the client tab.
5. The only fields to fill in are clientID and clientSecret and come from the information obtained in section A above.
6. Do not forget to save the changes made to the extension settings:
   
7. An additional button, for logging in with an Infomaniak identifier, is now visible on your user login page:
   

Infomaniak offers various Site Creator plans, free or paid, that cater to different needs. It is essential to understand the conditions associated with each type of offer before making your choice.

Understanding the different Site Creator plans

Site Creator is available…

• … either free with each paid web hosting:
  • In this case, 1 single Site Creator can be set up per Infomaniak web hosting.
  • To manage multiple sites created with Site Creator within the same Organization, it is therefore necessary to have multiple web hostings.
• … or independently (standalone in 3 versions) and does not require any other particular offer in this case:
  1. Site Creator Free
  2. Site Creator Lite
  3. Site Creator Pro

1. Site Creator Free

This offer is positioned as a test and discovery solution and is completely free. It is aimed at users who want to familiarize themselves with the tool or publish a very simple web page:

• It only allows one web page and offers limited disk space (5 Go).
• This offer does not allow connection to a custom domain name (it will be in the form *.infomaniak.site) and includes the mandatory display of Infomaniak's advertising notice.
• Important growth modules, such as full blog management, the use of Artificial Intelligence for text generation, or the 'Site Map' feature, are not included.

2. Site Creator Lite

The Lite plan is Infomaniak's entry-level paid offer. It is ideal for creating a showcase website or a simple personal blog, as it eliminates the main constraints of the free version and unlocks the modules necessary for a complete site:

• It allows the creation of a more substantial site with a limit set to 5 web pages and more comfortable disk space (15 Go).
• It includes the offer of a domain name for one year and, importantly, the removal of any Infomaniak advertising notice on the site.
• Unlike the Free offer, the Lite plan unlocks access to important features for navigation and organization, including the Blog Creation and Management module as well as the Site Map module.

3. Site Creator Pro

The Pro offer is the premium formula of Site Creator. It is exclusively dedicated to the most ambitious projects, such as launching a complete online store, thanks to the lifting of all content restrictions and the integration of advanced commerce and analysis tools:

• It removes any content limitation by offering unlimited web pages and a large disk space of 50 Go.
• It is the only offer that includes complete E-commerce management (orders, stock, discounts) and allows the integration of essential payment gateways (Stripe, PayPal, Mollie) for online commercial activity.
• The Pro plan is the only one to give access to crucial external analysis and performance tracking tools, such as Google Analytics, Hotjar, and tools like Google reCaptcha.

Commitment to paid offers

Unlike other Infomaniak products, some Site Creator offers include a free domain name. These offers require a firm commitment for a minimum duration of 12 months, with no possibility of refund, even partial, even if:

• you decide to stop using Site Creator before the end of the first year,
• you cancel your products,
• you close your user account or your Organization.

Evolution of offers and preservation of your site

It is possible to switch from a free offer to a more comprehensive paid offer:

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. Then click on the chevron Manage.
4. Click on Modify the offer:
   

It is also possible to switch to a higher offer (for example, from Lite to Pro).

If you wish to keep your site active, you must necessarily renew the same paid offer. It is not possible to switch to a free version of Site Creator, even if:

• you do not use any of the paid modules,
• your site contains only one page.

What to do if you want to return to the free offer?

In this case, you must:

• cancel your current site after manually copying all the information you wish to keep,
• activate a new free Site Creator offer,
• recreate your site by pasting the contents retrieved from the old one.

This guide details resource exhaustion errors that can occur when managing and visiting a website.

Preamble

• Resource limits are in place to maintain the integrity, stability, and performance of the shared server, while ensuring a fair experience for all users.
• If a website or application requires significantly higher resources, it may be necessary to switch to a Serveur Cloud or another type of virtual hosting where resources are allocated more flexibly.

Error origins

Fatal error: Maximum execution time of 30 seconds exceeded

This error occurs when the server sets a time limit for script execution, usually to avoid tasks that take too long. For example, if a script attempts to resize many large images in a single operation, it may exceed the allowed execution time limit. The server imposes this limit to ensure a quick response to user requests. The path often mentioned in the error can indicate a more precise origin (for example Fatal error: Maximum execution time of 30 seconds exceeded in /home/www/1234567abc/web/wp-includes/media.php on line 123)

memory limit exceeded

This error occurs when the script or application uses more memory than allocated. This can happen when a script processes a large volume of data or when there is a memory leak. For example, an image management script may consume more memory than allowed, resulting in this error.

Resolution paths

Some ways to resolve these errors:

• Check the scripts that make multiple connections to the server to display data.
• Optimize the script(s) in question so that they require fewer resources.
• Increase the limits of the concerned site to allow the script to complete its tasks and/or limit the number of simultaneous connections (especially on a Serveur Cloud where the limits (RAM, execution time, simultaneous connections) can be significantly increased).
• Migrate your hosting to Serveur Cloud.

Also, refer to this other guide.

This guide concerns the Drupal module "Infomaniak_Connect" which allows users to log in to your Drupal site (whether it is hosted by Infomaniak or not) using their Infomaniak credentials.

Preamble

• Allowing login via an Infomaniak account on your Drupal site allows your visitors to comment, register for courses, or access any member-only content with a single click, without having to create a new account.
• This saves them time and is a safer method for you, as you do not have to manage additional passwords.
• The operation of this external module is identical to the options "Log in with Google", "Log in with Facebook" or "Log in with Apple"; it uses the standard protocols OAuth2 and OpenID Connect to enable single sign-on (SSO).

A. Create an application with Auth Infomaniak

To do this:

1. Click here to access the management of your Auth product on the Infomaniak Manager (need help?).
2. Click the button to Create a new application:
   
3. Choose the type "Web Front-End".
4. Give a name to your application.
5. In the URL field, specify the domain name corresponding to your Drupal site followed by /openid-connect-authorize (refer to the GitHub documentation if necessary).
6. Click the button to complete the app creation:
   
7. Carefully note the 2 pieces of information obtained during the finalization of your OAuth2 application:
   

B. Configure the Drupal extension

Via SSH, deploy Composer if necessary to retrieve the openid_connect and infomaniak_connect extensions. To do this:

• You may need to edit the composer.json file as the version of openid_connect is not yet considered stable. Add:

• "minimum-stability": "dev",
  "prefer-stable": true

• The SSH commands for installing the 2 extensions are here:
  • https://www.drupal.org/project/openid_connect
  • https://www.drupal.org/project/infomaniak_connect

Then, on Drupal:

1. Search for the Infomaniak module among your pre-installed modules.
2. Select it.
3. Click the Install button:
   
4. The installation of the dependencies will proceed:
   
5. Under Configuration, click to set up the OpenID connection:
   
6. Click the edit button:
   
7. The only fields to fill in are Client ID and Client Secret and come from the information obtained in point A above:
    
8. Do not forget to save the changes made to the extension settings.
9. In the Settings tab, you can choose the display type for your login page; do not forget to save:
   
10. An additional button, for logging in with an Infomaniak identifier, is now visible on your login page for users:
     

This guide explains how to resolve an SSL certificate (Let's Encrypt or Sectigo) installation issue if you are using Cloudflare with strict security rules, such as country or IP filtering.

Adjust SSL / geoblocking settings

When an SSL certificate is requested via Infomaniak (free Let's Encrypt or Sectigo), the certification authority must verify that you are the owner of the domain. This verification can be done via HTTP (using special files placed on your site), DNS, or email:

• Let's Encrypt uses /.well-known/acme-challenge/.
• Sectigo usually uses /.well-known/pki-validation/ (or DNS / email depending on the option chosen).

If these verifications fail (for example, because Cloudflare blocks access), the certificate cannot be issued or renewed. However, Let's Encrypt no longer verifies from a single location. For some time (and even more since March 2024), it performs its verifications from multiple countries at the same time – including new ones like Sweden or Singapore. Result: if one of these countries is blocked by your Cloudflare settings, the certificate request may fail, even if everything else is correctly configured.

Even worse: even if you try to make an exception only for the challenge address (.well-known/acme-challenge), it may not work with some Cloudflare rules. Indeed, country or IP blocking rules are applied before any URL path-based exception.

Adjust SSL/TLS mode

In Cloudflare, use the Full or Full (strict) mode. These modes temporarily tolerate an expired or self-signed certificate, until the validation is complete:

Allow validation paths

Avoid blocking "IP Access Rules" and prefer "Custom Rules" that allow unrestricted paths:

• /.well-known/acme-challenge/ (Let's Encrypt)
• /.well-known/pki-validation/ (Sectigo)

Temporarily disable geoblocking

If necessary, temporarily disable geographic or IP blocking for the duration of the validation, then reactivate your protections after the certificate is issued or renewed.