Este guia detalha a compatibilidade dos serviços de hospedagem web da Infomaniak com IPv4 e IPv6.

Introdução

• A Infomaniak oferece suporte tanto a IPv4 quanto a IPv6, permitindo uma conectividade ideal para todos os usuários.
• Apenas os serviços de hospedagem Starter (gratuitos) e os planos de hospedagem mais antigos não são compatíveis: faça o upgrade para um Servidor Cloud ou hospedagem compartilhada.
• A compatibilidade com IPv4 e IPv6 significa que o serviço de hospedagem da Infomaniak permite que os sites sejam acessíveis tanto por usuários que utilizam endereços IPv4 quanto IPv6.
• Isso garante que seu site possa ser acessado por todos os tipos de dispositivos e redes, oferecendo uma experiência ideal para seus usuários, independentemente do protocolo que eles utilizem para se conectar à Internet.

IPv4, ou Internet Protocol versão 4

Esta é a primeira versão do protocolo de Internet amplamente utilizada desde a década de 1980. Ele utiliza endereços IP de 32 bits, o que permite identificar e localizar os dispositivos conectados à Internet. No entanto, com o esgotamento dos endereços IPv4, tornou-se necessário desenvolver uma nova versão (leia mais abaixo):

• Exemplo de endereço IPv4: 192.168.0.1
• Neste exemplo, o endereço IPv4 é composto por quatro grupos de números separados por pontos…
  • Cada grupo pode conter um número de 0 a 255.
  • O endereço 192.168.0.1 é frequentemente usado para representar um endereço IP local em uma rede privada.
• Descubra o IP do seu site: consulte este outro guia…
• Obtenha o IP público da sua conexão de Internet atual: https://chk.me/ip

IPv6, ou Internet Protocol versão 6

É a versão mais recente do protocolo de Internet, introduzida para resolver o problema do esgotamento dos endereços IPv4. O IPv6 utiliza endereços IP de 128 bits, oferecendo um espaço de endereçamento praticamente ilimitado. Também oferece funcionalidades aprimoradas, como segurança, qualidade de serviço e configuração automática de endereço:

• Exemplo de endereço IPv6: 2001:0db8:85a3:0000:0000:8a2e:0370:7334
• Neste exemplo, o endereço IPv6 é composto por oito grupos de números e letras separados por dois pontos…
  • Cada grupo pode conter um número hexadecimal de 0 a FFFF.
  • O endereço IPv6 é muito mais longo do que o endereço IPv4, oferecendo, assim, um espaço de endereçamento muito maior.

This guide explains how to set up a WordPress multisite network to manage multiple sites from a single WordPress installation by Infomaniak, with URLs such as site1.domain.xyz, site2.domain.xyz, or even domain1.com, domain2.com, etc.

WordPress multisite installation

To get started:

1. Install WordPress via Infomaniak on your hosting space with a main domain name:
   
   • This first WordPress site must be reachable and functioning correctly:
     
2. Connect via FTP.
3. Edit the wp-config.php file of this first WordPress site.
4. Above the line "/* That's all, stop editing! Happy blogging. */" (#94) copy-paste the code define('WP_ALLOW_MULTISITE', true);: 
   
   
    
5. Save your changes.
6. Then log in to the administration of your WordPress site.
7. Temporarily deactivate all WordPress plugins:
   
8. Go to the TOOLS menu to create a Network: 
   
9. Choose the method for creating your different WordPress sites (on subdomains)…
10. Click the installation button:
    
11. Add the instructions displayed on the screen to the wp-config.php and .htaccess on the server.
12. After reconnecting to your WordPress, you will get a new "My Sites" menu where you can add and manage your different sites in the same network: 
    
13. Reactivate your deactivated plugins.
14. On the Manager, add an alias to your site in the form *.your-domain-here (the asterisk allows you to create a wildcard alias) with DNS update so that the correct CNAME is automatically added to the zone: 
    
15. Install or update your SSL certificates:
    
16. When you create a new site within the network, for example by naming it home2, it will then be accessible via home2.domain.xyz and so on: 
    

This guide covers the support of secure hash functions (including SHA-256) by Infomaniak servers, as well as the emphasis on the security of SSL/TLS certificates using CSRs generated with SHA-256.

SHA-256 hashing algorithm

The cryptographic hash function SHA-1 is compatible and Infomaniak servers also support the SHA-256 function, which is useful for PayPal and SaferPay (SIX).

The CSRs (certificate signing requests) are in SHA-256 and not in SHA-1.

This guide explains how to display the IP address of a site on your Web Hosting.

Preamble

• The IPv4 address is usually the same for each of the sites on the hosting (unless you have acquired a dedicated IP).

Display the IP address of your site

The IP address is specified on the hosting management page (Starter or containing multiple sites):

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 product concerned.
3. Then click on the chevron to expand the Information section of this hosting.
4. The IPv4 address is displayed on the page:
   
5. The IPv6 address is also displayed in the case of paid hosting:
   

This guide details the "502 Bad Gateway" errors that can be encountered when visiting a website.

Preamble

• The 502 Bad Gateway error occurs when the server acting as a gateway between the browser and the origin web server receives an invalid response.
• This error can be caused by an overloaded web server, communication issues between a CDN and the hosting web server, or a misconfigured proxy server.
• Sometimes, the error can be caused by a bad entry in the DNS server.

Troubleshooting steps

To resolve the 502 Bad Gateway error, you often need to proceed by elimination:

• Check if the server is temporarily overloaded: simply reload the page after a few minutes for the error to disappear.
• Clear the browser cache.
• Try from another browser.

This guide explains how to change the URL of your website from the Joomla app installed on your Web Hosting Infomaniak (only in the case where you have installed Joomla via the dedicated tools offered by Infomaniak).

Prerequisites

• The domain name you wish to use must first be added as an alias to the main domain on the site in question.

Change the Joomla domain name

To change the address of the site created with Joomla to another domain name that already appears in the same Organization:

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 product in question:
   
3. Click on the action menu ⋮ located to the right of the Web Application in question.
4. Click on Settings of the application:
   
5. Click on Modify to the right of the Joomla:
   
6. Under Site URL, select the desired web address from the drop-down menu:
   1. If you have not followed the prerequisites above, the desired domain will not appear even if it is registered in the same Organization.
   2. If you have added the domain as an alias to the site, the desired domain will appear and you will be able to select it to replace the previous domain.
7. Click on the Save button:
   

“…preview.infomaniak.website” domain?

Among the URLs present in the drop-down menu, the preview URL allows you to access your Joomla site in case the site's domain name is not yet correctly configured to point to your app:

Change the address or location of Joomla

Prerequisites

• Create an FTP account (need help?).
• Connect via FTP (need help?).

To modify the Joomla installation if it was done in a subfolder…

… and if the latter is visible in the site address on each consultation…

… here is how to proceed:

1. On the FTP, move (to bring them back to the root in the target folder of the website) all the files of your Joomla currently installed in a subfolder (folder /presentation in the example below):
   
2. Delete the now empty subfolder:
   
3. Modify the .htaccess file located at the root of your Joomla directory.
4. Replace RewriteBase /presentation with RewriteBase /:
   
5. Save the changes.
6. Do not uninstall the Joomla Web Application but simply stop using it and log in directly to the management interface of your Joomla via the URL /administrator:
   

This guide details the resolution of incidents related to the automatic recovery of media with the VOD/AOD extension for WordPress, particularly when synchronization fails despite an established connection between the extension and the VOD space.

Preamble

• If the VOD plugin of your CMS can no longer automatically retrieve the videos from your VOD space, it is likely that the MySQL user of the database on which the CMS is installed does not have administrator rights.
• This situation can cause a problem during the installation of the VOD plugin on your CMS.

Repair automatic video recovery

To be done on your web hosting

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 concerned.
3. Click on Databases in the left sidebar menu.
4. Click on Users in the left sidebar menu.
5. Click on the action menu ⋮ located to the right of the user who manages the database of your CMS.
6. Click on Modify:
   
7. If necessary, add the ADMIN right to the user on the line of the database concerned:
   
8. Click on the button to Confirm at the bottom of the page.

To be done on WordPress

1. Uninstall the VOD plugin
2. Reinstall and activate the VOD plugin (refer to this other guide)
3. Reconfigure the plugin connection to the Infomaniak VOD account
4. Request the linking of video files again

Once the configuration is restored, the administrator privileges of the MySQL user can be revoked if necessary.

If an imported video shows a "conversion in progress" status that persists even though it is finalized on the Manager, there is likely a conflict with access restriction extensions (such as Members Only).

In case of abnormal behavior, temporarily disable your third-party extensions to identify any potential software incompatibility.

To force the refresh of a video stuck in the conversion state, use the Synchronize function available in the settings of the VOD extension under WordPress.

To be done on the Infomaniak Manager

Although the extension periodically synchronizes with your account, the appearance of new items (Players, folders, or playlists) may be delayed on your CMS.

For an immediate update, go to the VOD Management > Configuration section of your Manager and enable Quick Synchronization.

If new media does not appear in the CMS list, check the accessibility of the callback URL. This address, used by the encoding system to notify your site of a video's availability, must be public. Refer to the VOD Management > Configuration page for more details.

This guide explains how to manage interactions between your Infomaniak VOD/AOD space and any of your WordPress sites, using an extension developed by Infomaniak

Preamble

• This WordPress extension allows you to retrieve and manage all your videos present on an Infomaniak VOD/AOD space, with automatic updates when new videos are added.
• It manages the automatic retrieval of existing Players and playlist management.
• You will be able to search for your videos when writing an article or page or import media directly from the CMS administration.
• Possible incompatibilities:
  • The plugin is not compatible with Elementor.
    • Test if the problem persists after installing another editor.
  • The plugin is not compatible with WordPress Multisite.
  • The plugin is not compatible with Really Simple Security (Really Simple SSL).
    • Test if the problem persists by activating or deactivating this setting of the Really Simple Security extension:
      
    • Test if the problem persists after using another similar module.
    • If problems persist, refer to this other guide.

Get the Infomaniak VOD extension

Go to your VOD space to obtain the information necessary for the external WordPress module:

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 CMS Extensions/API in the left sidebar menu.
4. Click on CMS Extensions in the left sidebar menu.
5. Download the WordPress extension.
6. Configure the extension using the provided instructions:
   
   • It is recommended to create a new user in your Organization with only technical rights on the VOD/AOD product and then create the application password from this dedicated account.

You can also download the extension directly from the WordPress extension library:

A similar feature exists for Typo3 with the dedicated extension that you can find and install from its extension library:

This guide details the specifics related to managing MongoDB on your Managed Cloud Server, particularly regarding the version lifecycle.

Preamble

• Any new installation of the application deploys MongoDB version 7.0 (or higher) by default.

Upgrading from version 6 to 7

It is not possible to perform an automatic update (upgrade) from version 6 to version 7 directly from your interface.

Two solutions are available to you:

1. Order a new Cloud Server: it will natively have version 7, and you can then migrate your data to it.
2. Reinstall the application: uninstall and then reinstall MongoDB on the current server.

Backups and responsibility

As an administrator, the management and integrity of your data are entirely your responsibility.

Before any manipulation (especially reinstallation):

• Perform your own backups and exports (dump) of your databases.
• Plan for the manual import of your data once the new version is active.

Este guia explica como publicar uma aplicação criada com Lovable, utilizando um site do tipo Node.js na Infomaniak.

Pré-requisitos

• Um projeto Lovable numa oferta Lovable paga, sincronizado com um repositório GitHub.
• Um site do tipo Node.js.
• Um nome de domínio ou subdomínio destinado à aplicação.

1. Sincronizar o projeto Lovable com o GitHub

Para isso:

1. Abra o projeto no Lovable.
2. Abra as configurações do projeto.
3. Aceda à secção Git > GitHub:
   
4. Conecte o projeto a uma conta GitHub.
5. Aguarde que o repositório GitHub seja criado e que a sincronização seja concluída.

2. Descarregar o arquivo ZIP do GitHub

Para isso:

1. Abra o repositório GitHub associado ao projeto Lovable.
2. No GitHub, clique em Code.
3. Clique em Download ZIP:
   
4. Guarde o arquivo ZIP descarregado.

3. Criar o site Node.js na Infomaniak

Para isso:

1. Aceda à hospedagem web em questão no Manager Infomaniak.
2. Clique no botão para adicionar um site.
3. Selecione um projeto com tecnologias avançadas.
4. Escolha Node.js.
5. Associe o nome de domínio ou o subdomínio destinado à aplicação.
6. Selecione o método personalizado:
   
7. Escolha a importação por arquivo ZIP.
8. Importe o arquivo ZIP baixado do GitHub:
   

Em seguida, preencha os seguintes campos:

• Comando de construção:

  npm install && npm run build

• Comando de execução:

  npm start

Salve a configuração.

Seu site foi publicado.

This guide details the essential measures to protect your WordPress site against spam and automated malicious content.

Preamble

• A site without protection is an easy target for spambots (robots) that use comments to spread fraudulent links.
• Without protection, every form (contact, booking, voting) can be hijacked to send mass emails from your server.
• Spam degrades your user experience, harms the reputation of your domain (email blacklisting) and can saturate the resources of your hosting.

1. Master the comment system

By default, WordPress is configured to allow comments. To limit abuse, refer to the WordPress codex.

If you want to keep interactions, you can restrict comments to logged-in users only via the discussion settings page.

2. Use automatic protection tools

To block robots without harming the experience of your visitors, two main technologies exist: the captcha (visual test) and the honeypot (invisible trap for humans but detected by robots).

Solution included with Infomaniak

If you have installed WordPress via Infomaniak's automatic installation tool, the WP Armour – Honeypot Anti Spam extension is already activated. It natively protects the most common forms:

• WP Comments & WP Registration
• Contact Form 7, Elementor Forms, Divi Contact Form
• WooCommerce Reviews, BBPress, Gravity Forms

Recommended alternatives

• Akismet Anti-Spam: Developed by Automattic, it is a very effective reference, although paid for commercial sites.
• The Anti-Spam Sentinel: A complete extension and very well rated by the French-speaking community.
• Contact Form 7 Honeypot: A specific module if you only use the Contact Form 7 extension.

The role of the host

Beyond the security of your site, Infomaniak deploys protections at the server level. To learn more, refer to the article on combating malicious emails as well as the FAQ on the security tools provided.

Este guia explica como denunciar um spam ou declarar um falso positivo caso mensagens do tipo spam passem despercebidas no Serviço de Email Infomaniak, ou, inversamente, se um email válido for classificado como spam inadvertidamente; você pode intervir em poucos cliques.

Denunciar um spam

Pré-requisitos

• Verifique se o filtro de spam está ativo.

Em seguida, para mover automaticamente para a pasta Spam um email da sua caixa de entrada que tenha escapado ao filtro anti-spam:

1. Clique aqui para acessar o aplicativo web Email Infomaniak (serviço online ksuite.infomaniak.com/mail).
2. Selecione a mensagem na caixa de entrada e clique no ícone Spam na barra de ferramentas:
   
3. Você também pode abri-lo e declará-lo como Spam posteriormente:
   
4. Outra possibilidade: abri-lo e clicar no menu de ação ⋮ à direita:
   

Assim que você clicar em Denunciar como spam:

• o email será movido para a pasta Spam (ou para a pasta definida manualmente)
• o endereço do remetente é adicionado à lista de utilizadores bloqueados
• o filtro é aperfeiçoado para um melhor desempenho ao longo do tempo.

Reportar um falso positivo

Por outro lado, se você agir em um e-mail que foi incorretamente classificado como spam (falso positivo) clicando no ícone "Isto não é spam":

• O e-mail é movido para a caixa de entrada…
• O endereço do remetente é adicionado à lista de utilizadores autorizados…
• Isso também afeta o filtro e seus critérios.

This guide details the specific rules to follow when using a password containing the “dollar” character $ to send an email via the Infomaniak SMTP in a script (PowerShell, Python, etc.).

Preamble

• If you encounter an authentication error (e.g., auth failed, invalid login or password) when sending an email via SMTP, even though the password is correct and works in software like Outlook, the issue may be due to the handling of the $ character in your script or configuration file.
• To ensure reliable execution of your SMTP scripts, it is strongly recommended to avoid any special characters with syntactic significance, particularly $, in passwords used in scripts and configuration files.
• The problem may also occur when connecting to databases.

Rules to follow

The character $ is a special symbol in many languages and environments. When used in a password in a script or configuration file, it may be mistakenly interpreted as a variable or control character.

Here are common cases where you should not use the character $ in a password:

• PowerShell: $ is used to declare variables. A password containing $ can cause syntax errors or be truncated.
• Bash / Shell (Linux): $ is also a variable prefix. It can trigger unexpected substitutions.
• YAML files (e.g., Home Assistant, GitHub Actions, Docker Compose): $ can be interpreted as an environment variable.
• Files .env, .ini, or other configuration files: tools that read these files may attempt to interpret the variables.
• Commands or URLs with authentication: a password containing $ may be incorrectly encoded or fail during parsing.

To correct or prevent this type of error:

• Avoid using the character $ in passwords intended for use in scripts or automated systems.
• If you must use it, always properly enclose the password string according to the language:
  • In PowerShell: use single quotes 'password$Test' if possible.
  • In Python: ensure the string is properly enclosed in single or double quotes, without interpretation.
  • In Bash: escape the $ with a backslash \$.

Este guia explica o que você precisa verificar como visitante de um site se você receber um erro do tipo 403 para resolver esse problema.

O que é o erro 403?

O código de erro HTTP 403 geralmente significa que o acesso a um recurso é negado ao cliente pelo servidor.

Em que casos esse erro ocorre?

O usuário não está autenticado: o servidor exige que o usuário se identifique para acessar o recurso. Isso pode acontecer em páginas privadas que exigem autenticação, por exemplo.

O usuário está autenticado, mas não tem as permissões necessárias: o servidor reconhece o usuário, mas não permite que ele acesse o recurso solicitado devido a restrições de permissões ou funções. Essa causa do erro 403 pode ser um problema de permissão incorreta em uma pasta ou arquivo. Para uma pasta, a mensagem de erro é do tipo "403 Forbidden", para um arquivo, "failed to open stream: Permission denied". Nesse caso, você deve verificar se as permissões de suas pastas/arquivos estão corretas, ou seja, no mínimo 644 para um arquivo e 755 para uma pasta. Consulte este outro guia.

O endereço IP do usuário está bloqueado ou restrito: o servidor pode bloquear o acesso a um endereço IP específico por motivos de segurança, proteção contra ataques, etc. Consulte este outro guia.

O recurso solicitado não existe no servidor: neste caso, o servidor retorna um erro 403 em vez de um erro 404 para evitar a divulgação de informações confidenciais. Se você estiver tentando acessar sua página inicial ou uma parte do seu site, digitando um endereço como www.domínio.xyz ou www.domínio.xyz/pasta/, certifique-se de que exista uma página inicial chamada "index.html ou .htm ou .php" localizada no local correto (na raiz do seu espaço FTP, no diretório /web ou no diretório /pasta/). Consulte este outro guia.

Além disso, verifique se não há letras maiúsculas no nome do arquivo; todos os nomes de arquivos ou pastas devem estar em minúsculas, sem acentos ou espaços.

Erro relacionado ao script: se você estava executando um script, preenchendo um formulário ou fazendo um upload de arquivo e receber este tipo de mensagem:

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

a causa pode ser um filtro que impede o uso não autorizado de scripts por spammers. De fato, o antivírus Infomaniak bloqueia o upload de arquivos via scripts ou via FTP. Isso significa, na prática, que quando um hacker envia um arquivo identificado como vírus via um formulário, um script não seguro ou via FTP, sua instalação é bloqueada diretamente, o arquivo não é carregado no servidor e o upload gera um erro 403.

Em caso de falso positivo, entre em contato com o suporte da Infomaniak, fornecendo a URL da página onde você está encontrando esta mensagem de erro, para diagnosticar precisamente a origem do problema.

No entanto, existem muitos outros casos em que você pode receber uma mensagem "403 forbidden" e por razões muito diversas (scripts PHP, perl, mod_security, .htaccess, ...).

This guide helps resolve issues with special characters (accents, emojis, etc.) that do not display correctly or appear as symbols like ??, often due to incorrect encoding when connecting to MySQL.

Preamble

• By default, MySQL uses UTF-8.
• Recent MySQL servers are generally configured to use UTF-8 or UTF-8MB4 by default.
  • This is suitable for most cases, especially for international languages and emojis.
• Also, refer to this other guide to learn how to avoid encoding issues with non-European characters and emojis in your developments.

Set the default MySQL / MariaDB charset (Cloud Server)

With an Infomaniak Cloud Server, you can set the default charset (utf8 or utf8mb4):

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 MariaDB in the left sidebar.
4. Choose the default charset:
   
   • If you have not yet migrated to MariaDB, the principle is the same.
5. Save your changes at the bottom of the page.

Force a specific encoding (latin1 for example)

If you need to work with a database in latin1 (ISO-8859-1), you must explicitly align the encoding when connecting, depending on your environment.

On current offers, place the following code in a user.ini file located at the root of your hosting:

mysql.connect_charset = "latin1"
mysqli.connect_charset = "latin1"
pdo_mysql.connect_charset = "latin1"

or in PHP (MySQL API):

mysql_query("SET CHARACTER SET latin1");

On older hosting plans, force the MySQL connection to latin1 via the .htaccess file located at the root of your hosting:

php_value mysql.connect_charset latin1
php_value mysqli.connect_charset latin1
php_value pdo_mysql.connect_charset latin1

This guide explains how to transfer a website on which WordPress is installed, using one of its extensions, All-in-One WP Migration.

Prerequisites

• Order a Web Hosting / Cloud Server if you don't already have one.
• Create a site on your new hosting by choosing to install Infomaniak WordPress (this option is offered when adding a site - you can also install a WordPress site after creating a blank site).

Complete backup of the WordPress site

To back up all the files and the database of an existing WordPress site:

1. Install and then activate the All-in-One WP Migration extension from the administration interface of the current site's WordPress.
2. Go to the dashboard of the newly installed extension.
3. Click on Export.

4. Download the exported archive:

Site restoration

As specified in the prerequisites above, install a new WordPress on your Infomaniak Web Hosting and then:

1. Install and activate the All-in-One WP Migration extension from the administration interface of the new WordPress (it may be necessary to use the preview URL to connect to the new site, for example if the domain is being transferred).
2. Go to the dashboard of the newly installed extension.
3. Click to import a file, in this case, the exported archive from your previous WordPress site.
   • If the archive is large, you need to increase, in the website settings, the value of the maximum size allowed for imports on the server.
4. Once the site has been re-imported, reconfigure the main site address on the Infomaniak side.
5. When possible (for example, after the domain name transfer is complete), install an SSL certificate and check point 4 above again to select the httpS:// address.

This guide explains how to access automatic backups and restore a specific file from a website on an Infomaniak hosting.

Restore specific files or folders

To do this:

1. Access the FTP server via Web FTP (need help?).
2. Go to the /backups folder.
3. Select the files and/or folders to restore.
4. Click the Copy button:
   
5. Select the location to which to copy/restore the data (existing data will be replaced by the selected data).

This guide concerns MySQL/MariaDB and, more specifically, index and query analysis with Web Hosting.

Slowlog for long queries

The MySQL slowlog is enabled on all MySQL servers and groups queries that take more than 5 seconds* to execute. If your queries are well-structured, you will never see these files. Otherwise, check them regularly to correct any issues and ensure your site functions properly.

Contact Infomaniak support in writing to obtain them (except for older v1 hosting plans - old formula), which can be directly accessed from the Web FTP, one level above /web in the /logs directory.

What about logs?

No MySQL log is created (apart from slowlogs) because the MySQL servers could not handle the load of millions of logs being recorded simultaneously. If needed, Infomaniak can activate this MySQL log for 5 minutes to allow you to analyze it with EXPLAIN and determine useful indexes, for example. To do this, contact Infomaniak support in writing.

* elapsed time. Regarding locks, the documentation provides the following clarification: "The time to acquire the initial locks is not counted as execution time."

This guide explains how to suspend the administrative management of a product so that no user of the Organization can use it within the Infomaniak Manager. It is also possible to block a user of your Organization, without deleting them.

Preamble

• By blocking the management of a product:
  • Only administrators and the legal representative will be able to unblock it.
  • Users with limited rights (collaborators and clients) who have access to this product will no longer be able to manage it.
• An email is sent to the users of the Organization.

Block a product

Prerequisites

• Be an Administrator or Legal Representative within the Organization (users with limited rights (collaborators and clients) who have access to this product will not be able to do so).

To block or unblock certain products for the entire Organization:

1. Click here to access product management in the Infomaniak Manager (need help?).
2. Access the service you wish to block.
3. Click on the action menu ⋮ located to the right of the item in question.
4. Click on Block product management:
   • Example 1, Cloud Server:
     
   • Example 2, domain name:
     
5. Confirm the suspension.

Suspend emails

A Mail Service cannot be blocked in the way indicated above, but it can be put into maintenance.

Prerequisites

• Be an administrator or legal representative; users with limited rights (collaborators and clients) who have access to this product will not be able to do so.

To suspend email addresses:

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 product in question.
3. Click on Manage.
4. Click on Enable maintenance:
   
5. Confirm by clicking the red button to suspend the use of email addresses (reception is not interrupted but consultation is impossible):
   

Block an Organization user

To quickly block an Organization user in case of a security incident, log in to manage your users as an Administrator or Legal Representative of the Organization:

1. Click here to access user management on the Infomaniak Manager (need help?).
2. Click on the user in question:
   
3. From the Manage button at the top of the page, you can remove the user from the Organization (which also removes their various product management access).
4. Further down, you can more finely manage the products to which the user should have access:
   

Thus, critical services, such as the Manager interface, of your Organization, the Web app kDrive and the Web app Mail may become inaccessible to them.

Depending on the situation, also refer to these links to block other services such as messaging (IMAP / SMTP) or Web services.

To not block the user yourself but to indicate a procedure for them to follow to secure their account, refer to this other guide.

This guide details the Infomaniak Managed Cloud Server offer and the Infomaniak VPS offer intended for different uses.

Preamble

• Infomaniak offers two advanced hosting solutions:
  1. the Managed Cloud Server, which allows you to create multiple hosts (FTP/SSH spaces) on which you add your sites (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 exceed the limits of shared hosting. You can create and distribute your sites as you wish, define the root directory of each site, and adjust parameters such as memory_limit and max_execution_time.

Integrated tools are provided: cronjobs, Site Creator, simplified installation of WordPress, access and error logs (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 certain specific programs can be installed.

VPS (unmanaged)

The VPS gives you full control over the server, but it is your responsibility. Infomaniak manages the hardware and installs the version of Linux or Windows chosen at the time of ordering. No software intervention is performed by Infomaniak: you administer the system, install, and configure the software.

You can restart the server via the Infomaniak Manager. A snapshot system is available (excluding 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. Associated with shared hosting, the Infomaniak VOD/AOD space allows you to efficiently store and stream videos, support load increases, and obtain detailed viewing statistics.

Migration between Cloud Server and VPS

There is no automatic migration solution between a Managed Cloud Server and a VPS. To switch from one offer to another, you need to cancel the product you no longer use and order the new offer. Infomaniak refunds, upon request, any new server if the cancellation occurs within 30 days of the order.