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

Installing WordPress multisite

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 creating 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:
    

Thank you for trusting Infomaniak with the hosting of your website.

Preamble

• A web hosting is a storage space available on a computer, also called a "server", connected to the Internet and managed by a web host, Infomaniak.
• This storage space, made available to professionals and individuals, is used to install websites or other types of tools (CRM, extranet, intranet...) that need to be accessible via the Internet.
• These guides allow you to quickly use the essential functions of your new product, your web hosting, which can accommodate multiple websites.

Where to start?

1. Create a WordPress website
2. Build the site with Site Creator
3. Install a web application (ownCloud, Joomla, Typo3, Drupal, phpBB, Simple Machines Forum, Magento, Prestashop, …)
4. Manage your FTP accounts/users
5. Manage and publish files on your hosting via Web FTP
6. Manage your MySQL databases
7. Add a site or subdomain to your hosting (multi-sites/multi-domains) including a Node.js site
8. Link another domain name to an existing website (domain alias)
9. Preview your site even if your domain name does not yet point to Infomaniak's servers

IMPORTANT: the domain name…

A web hosting, to be visible to the public on the Internet, must be associated with a domain name!

Your domain name is not managed by Infomaniak? Or it is in a different Organization than that of your web hosting? Then refer to this other guide to configure the DNS or the "A records" to link the domain name to your web hosting.

In case of a problem

To resolve an issue, please consult the Web Hosting Knowledge Base before contacting Infomaniak support.

Click here to share feedback or a suggestion about an Infomaniak product.

This guide explains how to replace, within an Infomaniak Web Hosting, the address of a site currently a subdomain (https://dev.domain.xyz) with the main domain (https://domain.xyz).

Preamble

• Operations in brief:
  1. We start with a site created and accessible via the main domain URL dev.domain.xyz.
  2. We add an alias domain.xyz to it.
  3. We reverse the 2 types (the main domain becomes an alias and the alias becomes the main domain).
  4. We remove the old name dev.domain.xyz.
• Note that the site's location remains in the original folder on the server; the name of this location may be of the form /sites/dev.domain.xyz but this has absolutely no impact on the production site.
• Also refer to the last chapter of this other guide.

Reverse a linked domain

Here are the detailed operations to go from a site with a subdomain type address to a direct address (here dev.domaine-exemple.ch becomes domaine-exemple.ch):

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. Then click on the chevron to expand the Domains section of this site:
4. Click on the Add a domain button:
   
5. Add the desired new name (if the domain name to be added is under the same Organization, it will be suggested in the list, otherwise enter its spelling):
   
6. Enable or disable the checkboxes:
   • If the added domain is not in the form of a subdomain, it is possible to request to automatically add the www version of the domain.
   • Automatically update (if possible) the DNS records of the added domains.
   • Automatically update the related SSL certificates (if possible).
7. Click the button to Confirm and wait:
   
8. Once the addition is complete, click on the action menu ⋮ located to the right of the domain that has just been added and that you wish to set as the main domain:
9. Choose to set the item as the main domain:
   
10. Confirm the operation to proceed with the domain reversal:
    

This guide explains how to order, link or remove a dedicated IP from a website.

Manage dedicated IPs on hosting

Order one or more first dedicated IP addresses

To do this:

1. Click here to access your site management on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the site concerned:
   
3. Click on the chevron to the right of Advanced Tools in the left sidebar menu.
4. Click on Dedicated IPs in the left sidebar menu.
5. Click the button to order one or more IP addresses:
   
6. Increase according to the number of desired IPs:
   

Order one or more additional dedicated IP addresses

To do this:

1. Click here to access your site management on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the site concerned.
3. Click on the chevron to the right of Advanced Tools in the left sidebar menu.
4. Click on Dedicated IPs in the left sidebar menu.
5. Click on the text to order one or more additional IP addresses:
   
6. Increase according to the number of desired IPs.

Link a dedicated IP address to a website on hosting

Once the IP is ordered and paid for, be aware of the prerequisites below as switching to a dedicated IP address for a website can cause temporary disruption, especially in the presence of a Let's Encrypt SSL certificate.

Prerequisites

• Start by reducing the TTL of DNS records A and AAAA (for @ and www) to 5 minutes.
• Wait for the previous TTL duration before making any changes.
• The change below should be made during a period of low traffic to limit the inconvenience caused by the inevitable disruption.
• At the end of the procedure, you will need to wait for the new TTL to propagate the new configuration and regenerate the SSL certificate, then check the accessibility of the site in HTTPS to ensure everything is working correctly.

To switch to a dedicated IP address:

1. Click here to access your site management on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the site concerned.
3. Click on the chevron to the right of Advanced Tools in the left sidebar menu.
4. Click on Dedicated IPs in the left sidebar menu.
5. Click the button to associate the IP with a site on your hosting:
   
6. Choose the site to assign the new IP address to.
7. Check the box after reading the warnings.
8. Click the Associate button:
   

Remove a dedicated IP address from a website

Once the IP is installed, to uninstall it:

1. Click here to access your site management on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the site concerned.
3. Click on the chevron to the right of Advanced Tools in the left sidebar menu.
4. Click on Dedicated IPs in the left sidebar menu.
5. Click on the action menu ⋮ located to the right of the item concerned.
6. Choose Unlink:
   
7. Read the warnings and confirm the deletion to complete the IP uninstallation procedure.

This guide presents commands that can be executed to test a connection or a network and thus specify the source of a potential error.

Perform a Telnet...

TELNET allows you to test the connection to a server without considering all the additional settings of a mail or FTP application in order to determine the origin of a problem. If the connection does not go through on an SMTP server, for example, you will need to check if your firewall is not blocking port 587 or 465.

... on macOS

1. Search for Network Utility.
2. Go to the Ping, Lookup, or Traceroute tab depending on what you want to test.
3. You can also use a Terminal type application (command line interface, CLI / Command Line Interface) on your device and, depending on what you want to test, enter:
   traceroute [server]
nc [server] [port]
   Replace [server] with the server name or its IP address, same for [port]...

... on Windows

Enable Telnet if necessary.

1. Use a Terminal type application (command line interface, CLI / Command Line Interface) on your device, for example by typing Run then cmd.
2. In the window that opens, depending on what you want to test, type:
   tracert [server]
telnet [server] [port]
   Example: telnet mail.infomaniak.com 587 (allows you to test the SMTP port if your software/email client does not allow sending emails)...

... on Android

1. Use the application Simple Telnet Client which allows you to test very simply via 2 fields to fill in (for example mail.infomaniak.com and port 143 or 993)...

Perform a PING

PING allows you to know if a machine is accessible via the Internet. You can also check with this tool if you are addressing the correct machine, for example during a DNS change, by looking at the IP address obtained. It is possible to perform a ping on a domain name, a hostname or an IP address.

This guide explains how to obtain your email address(es) from the Swiss host Infomaniak.

Preamble

• Except for certain free offers, an email address at Infomaniak is always created within an Email Service, and this Email Service revolves around a custom domain name that must exist and be configured for the email to work.
• Example: you want the address jean.dupont@domain.xyz then you need:
  1. To own the domain name “domain.xyz”.
  2. To obtain an Email Service “domain.xyz”.
  3. To create the email address “jean.dupont”.
• All of this is offered and requested in the ordering process on infomaniak.com (see below), preceded by the mandatory creation of a user account (for which you will need to provide your personal email address, or an address that already exists in all cases).
• If the corresponding domain name is already registered with an external registrar, you may need to enter the correct MX record in the DNS zone.

Order email addresses from Infomaniak

Before or after your registration:

• Click here to choose the offer that suits you and follow the process to start using the email services.
• Once the Email Service is ordered, you will be able to create email addresses and associated passwords.

Add an additional Email Service

To add a new Email Service (to obtain new addresses on another domain):

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on the cart icon above the displayed table:
   

Increase the number of available email addresses on an existing Email Service

To increase the quota of available addresses if necessary, refer to this other guide.

Once the Email Service is activated

• Create your email addresses.

• Configure your emails on your computer and devices.

• Sync your contacts & calendars on your devices.

• Restore the content (including that present with another provider).

This guide helps you resolve various issues related to setting up and using a DMARC policy with your email.

Refer to this other guide if you encounter a DMARC issue specifically when using Google services.

DMARC error or rejection...

...during a redirection while the initial destination address may have received the email (SPF error)

Email redirection without SRS generating an SPF error

Assume you have configured an email redirection from your email address "user@example2.com" to your new address "user@yourdomain3.com", without using SRS. When someone sends an email to "user@example2.com", it is automatically redirected to "user@yourdomain3.com". Example:

• sender: john.doe@gmahoo1.com
• initial recipient: user@example2.com
• final destination: user@yourdomain3.com (SPF error)

In summary: when John sends an email to "user@example2.com", the email is redirected to "user@yourdomain3.com". However, the mail server of "yourdomain3.com" still sees the email as coming from "john.doe@gmahoo1.com".

In detail: when John sends an email to "user@example2.com", the email is redirected to user@yourdomain3.com" that is to say that the sender's envelope address will remain john.doe@gmahoo1.com but the recipient's envelope address will be changed to user@yourdomain3.com.

This will generate an SPF error, as the SPF of the gmahoo1.com domain does not authorize the IP addresses of the example2.com SMTP servers to send emails for its domain.

It is this SPF error that will generate the DMARC rejection.

If you want the redirection to work without error, it is necessary that the provider of the redirecting email address performs the redirections with SRS.

How email redirections work at Infomaniak

When you receive an email on an Infomaniak address and it is redirected to another email address, the sender's email address is rewritten to reflect the redirection. Thus, the recipient's mail server sees the email as coming from your own domain.

In summary, the use of SRS in email redirection helps maintain the integrity and security of emails while ensuring that authentication mechanisms such as SPF and DKIM remain valid.

...related to an incorrect DNS entry

Malformed DMARC Record: if the DMARC record is not correctly formatted, this can cause errors. Make sure that the tags and values are correctly specified.

Invalid DMARC Policy: errors can occur if the specified DMARC policy is not correct. Possible values for the policy are "none", "quarantine", and "reject". An incorrect value can cause problems.

Multiple DMARC Entries: having more than one DMARC entry in the DNS zone is considered an error.

If you have multiple DMARC records, mail servers may interpret this in different ways, which can lead to unpredictable behavior. Fix this by consolidating your DMARC settings into a single entry.

Check your current DMARC entry in dedicated tools like the ones below:

• https://dmarcadvisor.com/dmarc-check
• https://mxtoolbox.com/dmarc.aspx

...linked to a send that does not comply with SPF and/or DKIM

A DMARC error or rejection related to SPF or DKIM can occur if the SPF or DKIM authentication mechanisms are not correctly configured or if they are not aligned with the domain's DMARC policy.

This can happen, for example, if you send an email from your Infomaniak email address using another provider's SMTP sending server. To resolve this issue:

• Check the overall security of the Mail Service.

I send an email from my Infomaniak address and I receive a "Reject DMARC" error email

To resolve this issue:

• Check the overall security of the Mail Service.
• Perform a send test from the Webmail mail.infomaniak.com and/or check the server settings of the email software/client.

I send an email from an external email address (Microsoft, Google, Yahoo, Orange, ...) and Infomaniak rejects my email with a DMARC error

To resolve this issue:

• Check with your email provider if the sends are made in accordance with their configuration recommendation and if necessary contact the email sender's provider to get more information.

I want to receive an email on my Infomaniak address but the sender informs me that they receive a DMARC error when sending to my address

To resolve this issue:

• In this case, the email has been blocked due to a violation of the DMARC policy that the sender has set up on their domain; it is necessary for the sender to contact their email provider or the administrator of their service to inform them of the situation.

This guide details the Auto DJ feature of the Infomaniak Streaming Radio service, which allows you to generate a 24/7 live radio station from your own audio content (music, shows, podcasts, jingles, etc.) previously uploaded to your storage space.

Preamble

• The Auto DJ relies on the files stored in your Infomaniak AOD (Audio on Demand) space to create a linear stream.
  • You can use this same space for your on-demand file storage needs.
• You organize your media, create your playlists, and schedule their broadcast via an intuitive calendar interface.
• This allows for continuous broadcasting without the need for an active encoder at all times.

Activate Auto DJ

To start Auto DJ:

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 in question.
3. Click on the name of the audio stream in question:
   
4. Click on Auto DJ in the left sidebar menu.
5. Read the warnings and click the button to Activate Auto DJ when you are ready:
   
6. Select the AOD space to use if you already have one.
7. Apply your choice by clicking at the bottom right:
   
8. There you go, the AOD space for your audio files to broadcast is at your disposal:
   

Organize, import your audio files

The first step is to prepare your content. The tool currently accepts files in .mp3 and .aac formats. You can import an entire folder containing your audio files:

Once imported, you can organize your files into dedicated folders within your storage space to facilitate the management of your library:

Metadata management

It is possible to modify the ID3 tags (title, artist, album, cover) directly from the interface so that this information is displayed correctly on your listening devices:

Create playlists

Once your files are imported, you can group them into playlists:

• Manual playlists: precisely select the tracks and their order of play.
• Automatic playlists: set smart criteria (by tags, styles, or artists) to let the system dynamically generate the playlist:
  

Schedule broadcasting (Planning)

The scheduling tool allows you to manage your program grid in a very detailed way:

• Slot programming: arrange your broadcasts by playlist or by folder on a weekly calendar:
  
• Filler playlist: configure a backup playlist that will be broadcast automatically when no specific program is scheduled, thus ensuring an uninterrupted stream.
• Live / AutoDJ Transition: you can schedule time slots or automate the resumption of the Auto DJ stream as soon as an encoder (external source) stops pushing its stream.

Advanced audio settings

To ensure professional listening quality, several processing options are available:

• Audio normalization: standardizes the volume level of all your files to avoid volume differences between two tracks.
• Transitions: set crossfades and overlaps between tracks:
  

Integration and statistics

The stream generated by the Auto DJ is a standard streaming stream that benefits from all the tools of the Infomaniak ecosystem:

• Infomaniak Player: automatic display of current titles and broadcast history.
• Multi-format broadcasting: support for HLS and stream transcoding.
• Advanced statistics: Precise tracking of your audience in real-time and detailed reports.

The BIMI (Brand Indicators for Message Identification) standard, brand indicators for message identification) allows companies to incorporate their logo into the emails they send.

Preamble

• Infomaniak applications (and other companies around the globe - read the in case of problem chapter below) are compatible with BIMI and will display the logos next to the received emails.
• Infomaniak Mail Services allow you to configure your email with your logo; the benefits are numerous:
  • increased trust: recipients can visually identify your emails, thus reducing the risk of phishing.
  • brand reinforcement: a well-visible logo in inboxes reinforces brand awareness.
  • better deliverability: emails compliant with DMARC have a better chance of reaching the main inbox.

1. Create a logo

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

To be imported on the Infomaniak interface (read below) it must not exceed 10 Mo, but it can also be hosted on a publicly accessible secure server and you will simply need to indicate its URL for the BIMI DNS registration.

2. Obtain the VMC certificate

A verified logo certification (VMC) is required; it certifies 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 receive a PEM file containing the entity 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 the Global Security indicators of your Mail Service must be green (SPF + DKIM + DMARC)!

To access the Mail Service and set the logo of your company:

1. Click here to access the management of your Mail Service on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the Mail Service concerned.
3. Click on Global Security in the left sidebar menu.
4. Click on the Create button (in the BIMI section):
   
5. Fill in the requested information from the documents received (see chapter 2 above) and do not forget to save.

In case of a problem

• If the Create button in the BIMI box remains gray, make sure to check the informative messages: DMARC may exist but not be at the required rejection percentage, so adjust the parameters according to the indications.
• When there are multiple domains linked to the Mail Service, you must ensure that you have a certificate on each linked domain if you want BIMI on them.
• 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 linked to the Mail Service and delete the corresponding TXT record.

This guide is about IP addresses, those…

• …assigned to sites/hosting/servers, dynamic or static, shared or dedicated,
• …assigned by your Internet Service Provider (ISP) when establishing an Internet connection to your Infomaniak product.

Preamble

• A dedicated or static IP address for a website is a permanent IP address specifically assigned to it.
• Unlike a shared IP address, which is used by multiple websites, a dedicated IP address ensures that only this platform is associated with this address.
• Dedicated IP addresses for websites are often used in cases where stability, customization, and security are important, such as server hosting, firewall configuration, or activating SSL certificates (although it is possible to proceed without a dedicated IP address to install an SSL certificate).
• Here are the main advantages:
  • Configuring a PTR entry or reverse DNS on dedicated IPs is useful, especially for installing a mail server, as some email providers check the PTR record before accepting emails sent from a server.
  • Better connection stability.
  • Reduced risk of a bad reputation due to websites sharing the same IP address.
  • Easier configuration of certain technical aspects.
  • A dedicated IP can improve a website's search engine ranking (although there are differing opinions among SEO specialists).
• Note: Infomaniak does not allow access to websites via HTTP(S) by IP (dedicated) on managed servers; you must use a domain name that points to the IP (or use the preview URL).

Add a dedicated IP to the website

To add a dedicated IP to your website, refer to this guide.

If you encounter issues directing web traffic to a defined port, refer to this other guide.

IP address blockage (Internet connection)

If you can no longer access…

• … all your email addresses that you own with Infomaniak (which usually work fine) and this with an email software/client from the same Internet network (i.e., from the same IP address provided by your ISP)…

… or if you unfortunately performed this type of operation:

• repeated unsuccessful connection attempts via FTP, SSH, or on access points such as the WordPress login…
• requests returning too many errors such as mass 403 errors…

… your access to Infomaniak servers may be blocked following the banning of the IP address (banip / ipban) of your internet connection.

To unblock the situation, contact Infomaniak support by email and specify the domain concerned and especially your public IP address concerned.

Permanent Unblocking (IP Whitelisting)

With a Managed Cloud Server, you can request to permanently authorize the IP address in question so that it is never blocked again, regardless of the situation. To do this, you must:

1. Have a dedicated IP associated with your Managed Cloud Server.
2. Be aware that Infomaniak will no longer block any potential attacks from this IP; attacks or malicious access attempts from this address will no longer be automatically blocked by the security systems.
3. Confirm by email and from a contact address associated with the account (owner or administrator) that you understand and accept full responsibility in case of an attack from this IP.

Thank you for choosing Infomaniak to secure your sites with a Sectigo EV or DV SSL certificate.

Main SSL guides

• Order a Sectigo EV SSL certificate
• Understand the difference between EV and DV certificates
• Use a Sectigo certificate on an external site (other host)
• Understand the Sectigo guarantee for SSL certificates
• Resolve an SSL/https issue
• Install a free Let's Encrypt SSL certificate on a site
• Install a free 'wildcard' SSL certificate
• Uninstall an SSL certificate
• Update a Let's Encrypt SSL certificate (for example after adding/removing aliases)

Additional help

• Learn about all SSL FAQs
• Contact Infomaniak support

This guide shows how to use the Newsletter tool provided by Infomaniak to create and send newsletters, i.e., recurring messages to multiple recipients.

Why use Newsletter instead of a Mail Service

A newsletter is a periodic communication tool sent by email to a specific group of subscribers. It generally aims to inform, share news, updates or relevant content on a specific subject and maintain a relationship with a targeted audience.

They can contain articles, announcements, promotions, links to recent content, upcoming events, and sometimes exclusive offers for subscribers. The main goal is to provide interesting and relevant content to stimulate engagement and maintain the interest of subscribers.

Infomaniak Newsletter allows you to schedule and send newsletters to a list of email recipients waiting for your sends; you thus distribute email marketing campaigns effectively and personally and maintain regular and relevant communication with your customers and subscribers.

The features include the creation of templates, management of the subscriber list, performance analysis and all this is not directly feasible with a traditional Mail Service. Moreover, the tool has its own interface, standalone within your browser, completely separate from Mail Infomaniak and does not require a mail application. This means that if you already have contacts to whom you wish to write with their consent, you will need to import them to the tool beforehand.

Prerequisites

• Have a domain name on which you will activate the Newsletter:
  • Access to its DNS zone if the domain name is not with Infomaniak.
  • Create a new domain name if necessary.
• Have Newsletter credits to allow sending (1 credit = 1 newsletter sent to 1 subscriber).

Activate the Newsletter tool

To activate the Newsletter tool for the first time:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on START FREE to subscribe to the Newsletter offer.
3. Enter the domain name that will be used (and that must belong to you - see prerequisites above).
4. Click the blue button to Approve.
5. Start using the tool - or refer to this other guide if you encounter a problem or if additional configuration is requested on the screen.

Access the Newsletter tool

To access the Newsletter once activated:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on the domain name concerned in the table that appears:
   

Go further with the tool

• Import contacts
• Create and send a newsletter
• Newsletter credits
• Newsletter subscription form
• Double opt-in to avoid being labeled as a spammer
• Resend a newsletter to specific types of subscribers
• The variables to customize your content
• Use the Newsletter API

See all Newsletter FAQs ; click here to share feedback or a suggestion on an Infomaniak product.

This guide explains how to deploy n8n using its official Docker image on the Jelastic Cloud (Infomaniak PaaS).

Preamble

• Unlike tools like Zapier or Make, n8n, a “fair-code” workflow automation tool, can be self-hosted, allowing you to maintain full control over your data while connecting hundreds of services via an intuitive visual interface.
• The official image used is n8nio/n8n.
• Using an external database (PostgreSQL) is strongly recommended for stability and managing large volumes of data.
• The default internal port is 5678.
• If needed, local partners referenced by Infomaniak can handle these procedures: launch a free call for tenders; they take care of everything, freeing you from technical details — also discover the role of the host.

1. Creating the Jelastic Environment

Proceed as follows to configure your topology:

1. Log in to the Jelastic Cloud Dashboard.
2. Click on New Environment.
3. In the creation wizard:
   • Go to the Docker tab.
   • Click on Select an Image and search for n8nio/n8n. Set a version (e.g., latest or a specific version like 1.75.0).
   • Load Balancer: add a node (e.g., Nginx) to manage SSL and public access.
   • Database: add a PostgreSQL node (version 14+ recommended).
4. Assign enough Cloudlets (8 min. recommended for peak n8n) and name your environment.
5. Click on Create.

2. Configuring Storage and Persistence

By default, Docker data is ephemeral. It is imperative to mount a volume:

1. On the n8n node, click on the Configuration icon (the gear).
2. Go to the Volumes section.
3. Click on Add:
   • Local path: /home/node/.n8n
4. Save; configuration files and local encryption will now be preserved.

3. Essential environment variables

Access the Environment Variables section of the n8n container to set the following parameters:

Linking with PostgreSQL

To use the external database, also add:

• DB_TYPE: postgresdb
• DB_POSTGRESDB_HOST: Internal IP address or DNS of the Postgres node.
• DB_POSTGRESDB_PORT: 5432
• DB_POSTGRESDB_DATABASE: Database name (e.g., n8n).
• DB_POSTGRESDB_USER: Your user.
• DB_POSTGRESDB_PASSWORD: Your password.

4. First access and security

1. Once the container is restarted, open the URL of your environment.
2. Account creation: n8n will ask you to create the first administrator account.
3. SSL: if you are using a custom domain, install the Let's Encrypt add-on on the Load Balancer node.

5. Post-installation verification

• Create a test workflow with a Webhook node and verify that the generated URL is in https.
• Check the container logs to ensure no database connection errors appear.

This guide explains how to optimize a website managed on a Web Hosting to make it faster and offer smooth navigation to all your visitors, regardless of their connection speed.

The role of the host

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

The role of the site owner and the webmaster

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

Analyze the cause of the slowness

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

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

If the problem persists

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

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

If your needs evolve

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

This guide helps you if your SFTP software/client suddenly displays a request to accept a new fingerprint (digital fingerprint) when using the Swiss Backup Infomaniak service.

SFTP software/client alert

If your SFTP software suddenly displays a message asking you to accept a new fingerprint (digital fingerprint), this does not necessarily indicate a security issue. This request may occur following planned technical changes to Infomaniak's infrastructure (if you have received an email about this).

Indeed, as part of the evolution of its services, Infomaniak has recently changed the SFTP gateway used to access hosted files. These changes involve the deployment of new SSH keys on the server side. However, for security reasons, SFTP software/clients systematically compare the server key with the one they have in memory.

If a difference is detected, even if legitimate, they alert you to request confirmation. Therefore, it is normal for an alert to appear and for you to be asked to approve a new fingerprint.

Check if necessary

You can check the official new fingerprints of Infomaniak's SSH keys below. If they match what is displayed in your software, you can accept them with confidence:

4096 SHA256:p4QkBc70lkIpDZpjJAZ4VbPEIaOv54lWxd/DRCMfwgg sftp.swiss-backup.infomaniak.com (RSA)
4096 MD5:a3:6b:fa:7c:0e:22:da:42:ca:82:c7:cc:7e:1f:0a:4a sftp.swiss-backup.infomaniak.com (RSA)

4096 SHA256:gMiEH8oVwWhq8ByQWQP8xMEVy3URi2omZNSMCc0n8z0 sftp.swiss-backup02.infomaniak.com (RSA)
4096 MD5:d2:1a:11:9a:06:4c:55:98:df:38:cd:70:be:08:dd:ca sftp.swiss-backup02.infomaniak.com (RSA)

4096 SHA256:EcQDR+VNUCbK1Zz/eDoa295c0+7JGQD7EP6n+ro5G0U sftp.swiss-backup03.infomaniak.com (RSA)
4096 MD5:bf:5e:92:f7:ed:81:de:84:9e:43:48:f3:1a:9c:3e:8d sftp.swiss-backup03.infomaniak.com (RSA)

4096 SHA256:xRU5RakUZ/yJYg3CDi9JiSRymodbPgM4S3FXvVHqK2s sftp.swiss-backup04.infomaniak.com (RSA)
4096 MD5:16:ce:56:02:c3:ab:80:7b:31:99:a6:cd:a8:00:0e:79 sftp.swiss-backup04.infomaniak.com (RSA)

This change has no impact on the security of your data. If you use scripts or automated software for your transfers or backups, make sure they take this new fingerprint into account.

This guide explains the "Options +Indexes" directive for Web Hosting, which facilitates navigation for visitors and allows for more advanced customization of how files are displayed.

Preamble

• One of the main advantages of enabling directory indexing is that visitors can view and list all files and subdirectories of a given directory, even if they do not know the exact name of the file they are looking for. This can be particularly useful for file-sharing websites or download sites.
• Directory indexing also facilitates navigation for visitors who are not familiar with the file structure of the site. They can simply browse through the subdirectories to find the file or folder they need.
• The "Options +Indexes" directive can be customized to display additional information, such as the size and modification date of files, or to hide specific files or directories.
• Without this directive, a visitor may encounter an error of the following type:

Accès interdit!
Vous n'avez pas le droit d'accéder au répertoire demandé.
Soit il n'y a pas de document index soit le répertoire est protégé.
Si vous pensez qu'il s'agit d'une erreur du serveur, veuillez contacter le gestionnaire du site.
Error 403

Listing the contents of a web folder

To list the items contained in a folder without a specific index:

1. Create a .htaccess file in the folder in question.
2. Enter the following command: Options +Indexes

It should be noted that this solution will only work if you have no index in the directory in question; you need to remove the index.php, index.html, index.htm files, etc. but also the possible welcome.php file...

Customizing the display

Here is an example of code to customize the appearance of the file list generated by Apache:

Options +Indexes
IndexOptions FancyIndexing
IndexOptions FoldersFirst IgnoreCase NameWidth=* DescriptionWidth=* Charset=UTF-8
HeaderName header.html
ReadmeName footer.html

In this example, the user enables the "Indexes" option, adds the "FancyIndexing" option for a more aesthetic appearance, specifies the sorting order of the files, defines the width of the columns for the name and description of the files, and specifies the names of the files to use for the header and footer of the file list.

This guide explains how to install and configure systemd on a Cloud Server and presents the main commands that can be used.

Prerequisites

• Follow the installation guide for systemd on Cloud Server.
• Consult the official documentation to learn about all the possibilities offered by systemd
• The "unit" files must be placed in: ~/.config/systemd/user/ ( /home/clients/absolute-path-id/.config/systemd/user ) (replacing absolute-path-id visible in your Manager) and the permissions must be set to 0644.
• The --user parameter must be specified in each command.

Main commands

Here is a non-exhaustive list of commands that can be used with systemd.

Force systemd to reload the unit files and take into account the changes:

systemctl --user daemon-reload

Activate a service:

systemctl --user enable --now SERVICENAME.service

Check the status of a service:

systemctl --user status SERVICENAME.service

Configuration of Node as a service with systemd

It will be necessary to create a "Unit" file with the ".service" extension, which must be saved in the directory:

~/.config/systemd/user/

It is possible to reuse the example below by replacing the values starting with {} :

[Unit]
Description={Le nom du service} # Spécifier ici un nom du service. Celui-ci est obligatoire mais n'a pas d'impact sur le fonctionnement
[Service]
Restart=always
Environment=NODE_VERSION={la version souhaitée} # Spécifier ici la version de Node à utiliser. S'assurer qu'elle soit installée au préalable avec "nvm install {la version souhaitée}"
WorkingDirectory=%h/{repertoire du projet Node} # %h correspond à la racine de l'hébergement
ExecStart=/bin/bash -c "exec $HOME/.nvm/nvm-exec {commande de lancement du script node}" # Cette commande dépend du projet. Par exemple, "npm run start", "npm run serve" ou encore "node server.js" sont courants
[Install]
WantedBy=default.target

Additional actions with a Unit file

systemctl --user daemon-reload

Start the service (if it is already active, nothing happens):

systemctl --user start [Nom du Unit]

Stop the service (if it is not active, nothing happens):

systemctl --user stop [Nom du Unit]

Restart the service (if it is not running, it is started):

systemctl --user restart [Nom du Unit]

Get information about the service; in particular:

• "Active" which indicates whether the service is running and for how long
• "CGroup" shows the process group that the service manages, this allows you to see the active processes, with their arguments and their ID

Below 'CGroup' are any logs (the standard output and error of the process):

systemctl --user status [Nom du Unit]

Enable automatic service startup on server boot; NB: this does not start the service:

systemctl --user enable [Nom du Unit]

Disable automatic service startup on server boot; NB: this does not stop the service:

systemctl --user disable [Nom du Unit]

Configuration with user entries:

[Unit]
Description="nom service"
[Service]
Restart=always
Environment=NODE_VERSION=16.17
WorkingDirectory=%h/sites/"nom-repertoire-site"/
ExecStart=/bin/bash -c "exec $HOME/.nvm/nvm-exec npm run start"
[Install]
WantedBy=default.target

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

Import a database

To import a database on Infomaniak:

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 in question.
3. Click on Databases in the left sidebar menu.
4. Click on the “More actions” button/menu for more choices.
5. Choose Import a database:
   
6. Follow the assistant to the end.

You will then have the choice…

• … to send your database directly (sql, gz, bz2, zip, 300 Mo max) from your computer
• … to select the file to import from your hosting after uploading it to the server via FTP
• … to choose a backup from those that are done automatically
  

… then also choose:

• import data into a new database (creation)
• import into an existing database (replacement/overwrite)
  

Alternative method (SSH - for advanced users)

Prerequisites

• Have the .sql file of the database to import.
• Have created a new blank database.
• Have a user who has all rights on the database.
• Have an FTP + SSH account.

To import via SSH:

1. Send the database to import via FTP to your hosting.
2. Open an SSH terminal/console,
3. From a Terminal type application (command line interface, CLI / Command Line Interface) on your device, for example the application PuTTY (to download and install on Windows) or Terminal (installed by default on macOS), run and adapt the following command:

4. ssh ftp-user@adresse-du-serveur‍

   • replace ftp-user with the FTP + SSH account username (for example abcd_user)
   • replace adresse-du-serveur with the web server address of your hosting
5. Enter the FTP + SSH account password.

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 (for example abcd_user)
   • replace db-name with the database name (for example abcd_sample)
   • replace db-host with the MySQL server of your hosting
   • replace path with the path where you sent 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 during the import (this can take several minutes depending on the size).

This guide explains the principle of URL rewriting (URL Rewriting), an essential technique for SEO and user experience.

Preamble

• Aesthetics and Clarity: transforms a complex URL (index.php?id=123) into a readable URL (/post-title/).
• Referencing (SEO): search engines prioritize URLs containing keywords over technical parameters.
• Security: hides the internal structure of your site and the technologies used (such as .php extensions).

URL rewriting example

Consider the URL: article.php?id=25&cat=4. The goal is for it to appear as: /article/25/4/. Here is how to configure your .htaccess file:

# Désactive l'affichage des répertoires et suit les liens symboliques
Options -Indexes +SymLinksIfOwnerMatch
# Active le moteur de réécriture
RewriteEngine on
# Définit la base de réécriture si votre site est dans un sous-dossier (ex: /admin/)
# RewriteBase /admin/
# Règle de réécriture
RewriteRule ^article/([0-9]+)/([0-9]+)/?$ article.php?id=$1&cat=$2 [L,QSA]

• [L] (Last): indicates that this is the last rule to apply if the condition is met.
• [QSA] (Query String Append): allows other potential parameters to be preserved at the end of the URL.

Important: implementing these rules does not automatically update your links; you must manually update the internal links in your HTML code or database to use the new format.

Redirect to a main domain (SEO)

To avoid duplicate content, it is imperative to redirect your secondary domains to your main domain in HTTPS.

RewriteEngine On
RewriteCond %{HTTP_HOST} ^domaine-secondaire.xyz [NC,OR]
RewriteCond %{HTTP_HOST} ^www.domaine-secondaire.xyz [NC]
RewriteRule ^(.*)$ https://www.mon-domaine-principal.com/$1 [R=301,L]

The R=301 header tells search engines that the redirect is permanent, thus transferring the SEO "power" to the correct domain.