Get started for free Log in

Knowledge base

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

Knowledge baseWeb hosting
Search

This guide explains how to protect a part of a website on a Web Hosting by making it mandatory to enter a password before viewing a directory (including subdirectories) from a browser.

Note, this does not prevent a user from accessing the folder via FTP.

 

Simple method

Password protect (authentication Digest) a directory using the "Folder Protection" tool:

  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 Security in the left sidebar:
  4. Click on Folder Protection in the left sidebar.
  5. Click on the directory to protect.
  6. Activate the protection with the toggle switch, then create one or more users*:
    • * Users are defined per directory; the tool does not allow managing user groups:
  7. Click on the Add button.
  8. Click on the button to add access for an additional user if necessary.
  9. Click on the action menu ⋮ located to the right of the user concerned to modify or remove them.
  10. Click again on the toggle switch to completely disable the directory protection:

 

Manual method via .htaccess

To password protect a folder using the .htaccess file of your site:

  1. Connect to your hosting via an FTP software/client or the FTP Manager.

  2. In the folder to protect, create a file called password.php and adapt the following content inside by replacing 12345 with the desired password:

    <?php
$pass = "12345";
echo password_hash($pass, PASSWORD_DEFAULT);  // Affiche le mot de passe chiffré
?>
  3. Open a web browser and display the password.php file (example: domain.xyz/folder-to-protect/password.php).
  4. The web browser displays your encrypted password; copy the encrypted password, it will be needed later...

In the folder to protect, create a file named .htaccess and adapt the following content inside:

AuthName "Page d'administration protégée"
AuthType Basic
AuthUserFile "/exemple/.htpasswd"
Require valid-user

Replace /exemple/ with the absolute path of the folder to protect. Example:

AuthUserFile "/home/clients/0f83c7afb710e5ae2645a1b704d8772f/web/dossier_a_proteger/.htpasswd"

In the folder to protect, create a file named htpasswd.txt and adapt the following content inside:

login:password_chiffré
  • Replace login with the desired login.
  • Replace password_chiffré with the encrypted password copied in step 1 of this guide.

Once the file htpasswd.txt is saved, rename it as follows: .htpasswd.

Open a web browser and try to display one of the pages contained in the protected folder. If the guide has been followed correctly, the login and password (not encrypted) chosen allow access to the protected folder.

Other restrictions can also be added by .htaccess.

Link to this FAQ:

https://faq.infomaniak.com/68

Has this FAQ been helpful?

This guide explains how to redirect a domain name directly to another or how to automatically send visitors to your website to another page address (internal or external URL).

 

Preamble

  • To redirect traffic, you will need to act…
    • … either on the domain name itself (it must be hosted by Infomaniak and its DNS must also be those of Infomaniak),
    • … or on the code present in your pages (page .htaccess, homepage, etc.) if you have a website.
  • Make your life easier! If needed, local partners referenced by Infomaniak can handle these procedures. Launch a free call for tenders. They handle everything, freeing you from technical details.

 

Act on the domain name

via Web Redirection Tool

The tool available on the Manager allows you to act simply on the domain name (or subdomain) to redirect it to the Internet address of your choice.

via DNS modifications or A record

Change the DNS of the domain name or modify its A/AAAA records to direct web traffic to another provider.

 

Act on the page code…

… via HTML code to insert

Insert this line of code between the <head> and </head> tags of your homepage (usually named index.html):

<meta http-equiv="refresh" content="5;url=INSERT-HERE-NEW-URL">

Replace 5 with the desired wait time in seconds (0 for immediate).

The search engine Google indicates that it is preferable to use a 301 type redirection on the server side (see below). The W3C also advises not to use it.

… via PHP code to insert

If the site page has a .php extension, insert this header function call at the very top of the file:

header("refresh: 5; url=INSERT-HERE-NEW-PAGE-URL");

… via .htaccess file

To redirect all traffic targeting your site (regardless of the page called) to another address, insert this in the .htaccess file at the root of your site:

RewriteEngine On
RewriteRule ^(.*)$ INSERT-HERE-NEW-URL/$1 [R=301]

To target the page that needs to be redirected:

Redirect permanent /ancienne_page.html insérer ici adresse URL de destination

Redirectpermanent, Redirect permanent and Redirect 301 are equivalent commands.

Here is another example of redirecting a sub-section to the homepage (this directive has the advantage of working with "deep links" unlike a permanent redirect):

RewriteEngine on
RewriteRule "old/path/url "/" [L]

Refer to this other guide on this topic.

Link to this FAQ:

https://faq.infomaniak.com/79

Has this FAQ been helpful?

This guide explains how to enable support for certain file types (e.g., .inc) on an Infomaniak web hosting via PHP so that they are processed in the same way as a .php file.

 

Preamble

  • Previously, you had to add the following line in a .htaccess file:
    • AddType application/x-httpd-php .inc
    • This prevented the file content from being displayed as text instead of being correctly interpreted by PHP when accessed via a browser.
  • Now you can manage file extensions via the FPM Extensions field in the Manager of your hosting.

 

Manage extensions recognized by PHP

To add support for a specific file type:

  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 Manage under Advanced settings:
  4. Click on the PHP / Apache tab.
  5. Edit the FPM Extensions field to add the desired extension.
  6. Click the button at the bottom of the page to save:

Link to this FAQ:

https://faq.infomaniak.com/82

Has this FAQ been helpful?

This guide explains how to view information about visitors who have accessed your Web Hosting sites (traffic stats).

 

Preamble

  • The result is presented in a simple format with a graph, allowing for easy interpretation.
  • Annual, monthly, daily, and hourly statistics are displayed per site, http address, referring site, country, etc.
  • Refer to this other guide if you are looking for information about access logs.

 

Access visit statistics

To view public traffic statistics:

  1. Click here to access your site management on the Infomaniak Manager (need help?)
  2. Click directly on the name assigned to the site in question.
  3. Click on Statistics in the left sidebar:
  4. The upper part allows you to choose:
    1. the potential site in question
    2. the type of desired statistics
    3. the period
    4. the download of the current tab's information to have it interpreted by a third-party tool:

 

Explanation of terms

There is no distinction between humans and robots. You can also use tools like Matomo, Open Web Analytics, Google Analytics, etc.

CategoryDescriptionDetails
HitsEach request made to the server is recordedHits include all requests, whether they are HTML pages, graphic files, audio, etc. Each element requested on your site, whether visible or not, is counted as a hit. It's as if each visitor presses an invisible button with each interaction with your site.
FilesRecords requests that require data to be sent backThis category records requests that require the server to return data, such as graphic files or HTML files. The difference between hits and files can be likened to the difference between incoming requests and outgoing data.
PagesCounts the number of pages displayed on your siteThis counter measures the number of pages viewed on your site, excluding graphic or audio files. Each time a user accesses a new HTML page, it is recorded as a page view.
VisitsCalculates the time elapsed since the last visit from an IP addressA visit is recorded when the IP address requests data from the server. If this address returns within 30 minutes, it is considered a unique visit. If it exceeds 30 minutes, a new visit is counted.
SitesEstimate of visits from fixed IP addressesThis category provides an estimate of the number of visits from fixed IP addresses, excluding connections via mobile networks or other dynamic connection technologies. This gives an overview of regular visitors to your site, often linked to businesses or institutions, which can help you better understand your target audience and tailor your content accordingly.
KBAmount of data sent by the server in KBThis figure represents the total amount of data transferred during the given period, measured in kilobytes. It is calculated from the server logs, but may have some calculation errors due to variations in file size.
Total hitsA hit is an HTML request, each page view generates multiple hitsFor example, if a page contains 3 images and a text, it will return 5 hits each time it is displayed: one for the page itself, one for the text, and 3 for the images. Thus, the total number of hits can be significantly higher than the number of page views.
Total filesTotal number of files called by the visitors' browser.This figure represents the number of specific files (images, HTML files, etc.) requested by visitors while browsing your site. It can be useful for assessing the complexity of your site and the variety of content viewed by visitors.
Total PagesTotal number of pages displayedEach time an internet user accesses a new page on your site, it is counted as a page view. This number may differ from the total number of hits, as a single page can generate multiple hits if it contains multiple elements to load.
Total VisitsTotal number of unique visits recordedA unique visit is recorded each time an internet user accesses your site. If the same visitor returns within a 30-minute period, it is counted as a single visit. This number is an indicator of visitor engagement on your site.
Total KBTotal amount of data transferred in kilobytesThis figure represents the total size of the data sent by your server to visitors during the given period. It can be used to assess your site's bandwidth consumption and plan hosting upgrades if necessary.
Total unique sitesTotal number of unique IP addresses that have visited your siteThis number represents the number of distinct IP addresses that have accessed your site during the given period. It can be used to assess the diversity of traffic sources to your site and identify the most active audience segments.
Total unique URLsTotal number of unique paths taken during visitsThis figure represents the number of distinct paths followed by visitors while browsing your site. Each unique URL corresponds to a specific page or file viewed by visitors. This can provide information about your site's navigation structure and the most viewed content.
Total unique referrersTotal number of distinct referring sitesThis number represents the number of external sites that have directed traffic to your site through links. Referrers are important indicators of the effectiveness of your online marketing strategy and can help identify the most performing partners or traffic channels.

 

Meaning of 'Commercial (com)' in the country list

When you view the statistics under 'Geographical areas', you will notice that 'Commercial' represents a significant portion of the traffic. This category includes users connected to the Internet via Internet Service Providers (ISPs) with a .com domain in their address. It is difficult to determine which country or countries are represented by .com as this extension is used by several ISPs from different countries. Additionally, the 'Commercial' category may also include companies using .com addresses regardless of their actual geographical location.

As for 'unresolved', these correspond to IP addresses that cannot be resolved to a specific geographical location. These addresses may result from various reasons such as ISP privacy settings or virtual private networks (VPNs). They therefore remain undetermined in the geographical location statistics.

Link to this FAQ:

https://faq.infomaniak.com/83

Has this FAQ been helpful?

This guide is for you if you encounter a 500 error that can have various causes generally related to the development of your website on a Web Hosting, particularly with the rewrites of your .htaccess files.

 

Preamble

  • Apache2, in place on the servers, no longer supports certain modules such as mod_auth_anon, mod_auth_dbm, mod_authz_dbm, mod_cern_meta, mod_imap, mod_imagemap, mod_mime_magic
  • Apache2 is strict about syntax errors and when it encounters syntax errors in a .htaccess file, this can result in 500 Internal Server Errors or unexpected URL rewrite errors

 

Syntax examples and correction

In this first example, the syntax error is that the rewrite rule does not specify the HTTP redirection response code to return.

RewriteRule ^articles/([0-9]+)/$ /article.php?id=$1 [L]

The correction adds the R=301 directive to specify that the redirection should return a 301 (permanent) code:

RewriteRule ^articles/([0-9]+)/$ /article.php?id=$1 [L,R=301]

 

In this second example, the syntax error is that the Options directive does not correctly specify the options to enable or disable.

Options -Indexes FollowSymLinks

The correction adds the "+" sign to specify that FollowSymLinks should be enabled rather than disabled:

Options -Indexes +FollowSymLinks

 

Resolving these errors

  • If the first page or another page displays a 500 error, rename the .htaccess file or comment out all lines with # and uncomment line by line until you find the problematic section.
  • If the error occurs after a modification made to one of your pages, the simplest solution is to restore the previous version of the file.

Link to this FAQ:

https://faq.infomaniak.com/106

Has this FAQ been helpful?

Access to the system commands who and users is prohibited for LDAP users on all Infomaniak servers.

Link to this FAQ:

https://faq.infomaniak.com/108

Has this FAQ been helpful?

This guide concerns the installation of PHP extensions on Infomaniak Web Hosting.

 

Using Zend PHP extensions

  • Zend Guard Loader is a PHP extension that allows you to run PHP scripts encrypted via Zend Guard.
    • Zend Guard Loader is installed by default for PHP <= 5.6 on all web hosting and is not available for PHP versions >= 5.6.
  • Since PHP 5.3.x, the Zend Optimizer module has been replaced by ZendGuardLoader
  • The ZendOPCache extension requires a Cloud Server configured with PHP 5.5 minimum

Link to this FAQ:

https://faq.infomaniak.com/130

Has this FAQ been helpful?

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.

Link to this FAQ:

https://faq.infomaniak.com/147

Has this FAQ been helpful?

This guide explains how to enable the following functions on Web Hosting (in italics, Cloud Server only):

  • proc_open
  • popen
  • exec()
  • shell_exec()
  • set_time_limit
  • passthru
  • system

 

These functions are disabled by default as they pose a significant security risk in case of a website hack. Only enable them if there is a real need (for a script or CMS ImageMagick, Typo3, CraftCMS, etc.).

 

Enable PHP functions

To access website management:

  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 Manage under Advanced Settings:
  4. Click on the PHP / Apache tab.
  5. Click on the toggle switches On/Off as desired:
  6. Click on the Save button at the bottom of the page to validate the changes.

Link to this FAQ:

https://faq.infomaniak.com/173

Has this FAQ been helpful?

This guide explains how to access InnoDB at Infomaniak.

 

Use the MySQL InnoDB storage engine

As soon as your Infomaniak hosting gives you access to MySQL / MariaDB databases, InnoDB is available at the same time (MyISAM previously).

InnoDB offers advanced features such as ACID transactions, row-level locks, full-text indexes, etc. You can take advantage of these features by using appropriate SQL statements in your queries.

Link to this FAQ:

https://faq.infomaniak.com/176

Has this FAQ been helpful?

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.

Link to this FAQ:

https://faq.infomaniak.com/206

Has this FAQ been helpful?

This guide details the errors of type Rejected, too many connections from this host if they occur when visiting a website.

 

Error origins

429 Too Many Requests

This error occurs when the server is overwhelmed by a large number of requests in a short period of time, which can be due to heavy use of the site or abuse.

503 Service Unavailable

This error can be caused by several factors, including scheduled maintenance work on the server, server overload due to high traffic, or running a script that exceeds the server's resource limits.

Rejected, too many connections from this host

This error occurs when the server rejects connections due to a high number of simultaneous connections from the same IP address. Check the "Access and error logs" on your hosting dashboard to find multiple entries of the form:

[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/js/modules/blocktopmenu/js/superfish-modified.js current:34 limit:30	

[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/js/modules/blocktopmenu/js/hoverIntent.js current:34 limit:30	

[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/js/modules/productscategory/productscategory.js current:34 limit:30	

[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/modules/feeder/rss.php current:35 limit:30	

[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/js/modules/favoriteproducts/favoriteproducts.js current:34 limit:30

In this example, the IP 222.111.123.123 is executing 30 simultaneous connections on each page, consequently, it is automatically rejected as this may resemble an attack or scan.

 

Resolution tips

A few tips to resolve these errors:

  • Check the scripts that make multiple connections to the server to display data.
  • Optimize the affected script(s) so that they require fewer resources.
  • Increase the limits of the affected site to allow the script to do everything it needs to do and/or limit the number of simultaneous connections (especially on a Cloud Server where the limits — RAM, execution time, simultaneous connections — can be significantly increased).
  • Migrate your hosting to a Cloud Server.

Link to this FAQ:

https://faq.infomaniak.com/231

Has this FAQ been helpful?

This guide explains how to block access to certain directories of a Web Hosting for certain visitors / robots / crawlers by filtering and blocking their IP addresses or hostnames.

 

Setting up .htaccess rules

Create a .htaccess document at the root of your site and enter the rules intended to block certain IP addresses or bots.

 

To block visitors based for example on the beginning of their IP address, use the directive "deny from":

Order Deny,Allow
Deny from 123.456.
Allow from all

This means that all requests from an IP address starting with "123.456." will be denied, while all other requests will be allowed. Blocked users will receive an HTTP 403 Forbidden error message.

Block a specific IP address

Order Allow,Deny
Deny from 123.456.789
Allow from all

This means that a single IP address, 123.456.789, is blocked and all other IP addresses can access the site.

Block multiple IP addresses

Order Allow,Deny
Deny from 123.456.789
Deny from 987.654.321
Allow from all

This means that two IP addresses, 123.456.789 and 987.654.321, are blocked and all other IP addresses can access the site.

Block a bot by its user-agent

SetEnvIfNoCase User-Agent "BadBot" BadBot
Order Allow,Deny
Deny from env=BadBot
Allow from all

This means that any bot identified with a user-agent "BadBot" will be blocked and all other users can access the site.

Block access to a specific folder

Order Allow,Deny
Deny from all

This means that all accesses to the folder "/folder" will be blocked, regardless of the IP address or user-agent. An assistant for a similar feature is available in your Infomaniak Manager.

 

mod_rewrite directives

You can also use the mod_rewrite directive to block certain IP addresses or bots in a .htaccess file.

The mod_rewrite directive can affect the performance of your website if used excessively or incorrectly. It is therefore recommended to be cautious when modifying your .htaccess file.

Here are a few examples:

Block a specific IP address

RewriteEngine on
RewriteCond %{REMOTE_ADDR} ^123\.456\.789\.
RewriteRule ^(.*)$ - [F,L]

This means that a single IP address, 123.456.789, is blocked and all other IP addresses can access the site.

Block multiple IP addresses

RewriteEngine on
RewriteCond %{REMOTE_ADDR} ^123\.456\.789\. [OR]
RewriteCond %{REMOTE_ADDR} ^987\.654\.321\.
RewriteRule ^(.*)$ - [F,L]

This means that two IP addresses, 123.456.789 and 987.654.321, are blocked and all other IP addresses can access the site.

Block a bot by its user-agent

RewriteEngine on
RewriteCond %{HTTP_USER_AGENT} BadBot [NC]
RewriteRule ^(.*)$ - [F,L]

This means that any bot identified with a user-agent "BadBot" will be blocked and all other users can access the site. This can be useful to prevent unwanted robots from accessing certain pages or from consuming resources unnecessarily.

Block access to a specific folder

RewriteEngine on
RewriteRule ^dossier/secret - [F,L]

This means that all accesses to the folder "/folder/secret" will be blocked, regardless of the IP address or user-agent.

Block and redirect elsewhere

RewriteEngine On
RewriteCond %{REMOTE_ADDR} ^123\.456\.789\.
RewriteRule ^(.*)$ http://www.domain.xyz/blocked.html [L,R=301]

This means that all requests from the IP address 123.456.789 will be redirected to the page "blocked.html" on the site "www.domain.xyz". The last part of the line RewriteRule, [L,R=301] indicates that the redirection is permanent (R=301) and that this is the last rule to be applied (L).

You can add multiple conditions RewriteCond to block different IP addresses and redirect to different pages.

Also refer to this other guide.

Link to this FAQ:

https://faq.infomaniak.com/232

Has this FAQ been helpful?

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

 

Web Hosting (Starter, Shared, Cloud Server)

Refer to these guides to restore automatic backups:

 

Refer to these guides to backup and restore:

 

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

 

Hosting v1 (old 60 Go offer)

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

 

Mail

 

Domains / DNS Zones

Link to this FAQ:

https://faq.infomaniak.com/250

Has this FAQ been helpful?

This guide helps you set up the header Access-Control-Allow-Origin, an HTTP header that specifies which origin (domain, protocol, and port) can access resources on a server. This header is used to control cross-origin (CORS) access from a web application.

 

⚠️ For additional help contact a partner or launch a free call for tenders — also discover the role of the host.

 

List of authorized domains

You can add the origin of a request to the list of authorized domains to access server resources by adding it to the values of the header Access-Control-Allow-Origin.

To authorize, for example, the site https://domain.xyz to access resources with CORS, the header must be as follows:

Access-Control-Allow-Origin: https://domain.xyz

You can set it via the header() function of PHP by drawing inspiration from this guide in particular.

If you need this header to be applied everywhere, you can use an auto-prepend.

Link to this FAQ:

https://faq.infomaniak.com/256

Has this FAQ been helpful?

This guide helps you understand the different HTTP status codes.

 

1xx - Information

error 100: Continue
The server has received the request headers and the client may continue to send the request body.

error 101: Switching Protocols
The server agrees to switch the communication protocol according to the client's request.

 

2xx - Success

error 200: Request executed successfully
The request has been successfully processed by the server.

error 201: Document created (reason: new URI)
The request was successful and resulted in the creation of a new resource.

error 202: Request completed asynchronously (TBS)
The request has been accepted but the processing is not yet complete.

error 203: Request completed incompletely
The server successfully processed the request, but the returned information comes from a third-party source.

error 204: No information to return
The request was successfully processed, but there is no content to return.

error 205: Request completed but form empty
The server successfully processed the request and asks the client to reset the document that submitted the request.

error 206: Incomplete GET request
The server returns only part of the data, as requested by the client with the Range header.

 

3xx - Redirections

error 300: The server cannot determine the return code
The request has several possible responses, and the server cannot automatically choose one of them.

error 301: Document permanently moved
The requested resource has been permanently moved to a new URL.

error 302: Document temporarily moved
The requested resource is temporarily located at another URL.

error 303: Redirection with new access method
The response to the request can be found under another URL using a GET method.

error 304: The 'If-Modified-Since' field was not modified
The resource has not been modified since the last request. No new data will be returned.

error 305: Redirection to a proxy specified by the header
The requested resource must be accessed through a specified proxy.

error 307: Temporary redirection
The requested resource is temporarily located at another URL, but the client must use the same method to make the next request.

 

4xx - Client errors

error 400: Syntax error in the document address
The request is incorrect or malformed.

error 401: No authorization to access the document
Access to the resource requires authentication.

error 402: Access to the document subject to payment
This code is reserved for future use regarding online payments. Some services outside of Infomaniak use it in certain cases to indicate a payment issue, but these uses are specific to these platforms — not a global standard.

error 403: No authorization to access the server
The server understands the request but refuses to authorize it.

error 404: The requested page does not exist
The server cannot find the requested resource.

error 405: Form request method not authorized
The method specified in the request is not authorized for the target resource.

error 406: Request not accepted by the server
The requested resource is not capable of generating acceptable content according to the Accept headers sent in the request.

error 407: Proxy authorization required
Access to the resource requires authentication by a proxy.

error 408: Access time to the requested page expired
The server did not receive the complete request within the allotted time.

error 409: The user must resubmit with more information
The request cannot be processed due to a conflict with the current state of the resource.

error 410: This resource is no longer available
The requested resource is no longer available and this is permanent.

error 411: The server refused the request because it has no length
The server refuses to process the request without a valid Content-Length header.

error 412: The precondition given in the request failed
One of the conditions specified in the request headers has failed.

error 413: The request entity was too large
The server refuses to process the request because the entity size is too large.

error 414: The request URI was too long
The server refuses to process the request because the URI is too long.

error 415: Unsupported media type
The server refuses to process the request because the format of the request entity is not supported.

 

5xx - Server errors

error 500: Internal server error
The server encountered an unexpected condition that prevents it from processing the request.

error 501: Request made to the server not supported
The server does not support the functionality required to process the request.

error 502: Bad gateway access
The server, acting as a gateway or proxy, received an invalid response from the upstream server.

Error 503: Service unavailable
The server is not available at the moment (overloaded or undergoing maintenance).

Error 504: Gateway timeout
The server, acting as a gateway or proxy, did not receive a timely response from the upstream server.

Error 505: HTTP version not supported
The server does not support the HTTP protocol version used in the request.

Link to this FAQ:

https://faq.infomaniak.com/257

Has this FAQ been helpful?

This guide concerns the homepage names that can be on your Infomaniak Web Hosting, and which will be prioritized when a visitor accesses your website via its domain name.

 

Regarding Site Creator, refer to this other guide.

 

Preamble

  • The default homepages on a web server are the first pages that appear when a user accesses a website without specifying a particular file.
  • If you simply enter http://domain.xyz in your browser's address bar, the web server will look for a default homepage to display, for example index.html, index.php, index.htm, or other similar variations.

 

Priority order of homepages

Here is the priority order of the default pages loaded at Infomaniak:

  1. index.html
  2. index.htm
  3. home.html
  4. home.htm
  5. default.html
  6. default.htm
  7. index.cgi
  8. index.php
  9. index.php5
  10. index.php4
  11. index.php3
  12. default.php
  13. home.php
  14. welcome.php

In summary:

  • If you have 2 pages at the root of your hosting, thanks to the ranking above, you can see that index.php is recognized as a priority over welcome.php.
  • It can also be deduced that if you only have welcome.php as a page in the root folder, it will be loaded and function as a homepage.
  • If you have a page accueil.html, it will not work because this name is not in the list.
  • When you type www.domain.xyz in the browser, only index.php will be displayed automatically (and to display welcome.php you will need to type the exact page name www.domain.xyz/welcome.php).

 

Customize the default homepage

To set a different default homepage, add DirectoryIndex followed by the appropriate pages in the .htaccess file:

DirectoryIndex accueil.html index.php index.html

This means that the web server will first look for a file named home.html. If it does not find home.php, it will look for index.php, then index.html.

Link to this FAQ:

https://faq.infomaniak.com/261

Has this FAQ been helpful?

This guide details the error "Database connection error: could not connect to mysql" that may occur when making changes around an Infomaniak hosting on which the Web app Joomla is installed.

 

Preamble

  • To get the site working again, you need to check and update some information in the Joomla configuration.php file:
    1. The name of the MySQL database — this is often a prefix that has been added before the existing database name and the username (for example bddname before, abcd_bddname after).
    2. The MySQL database host server (for example mysql.domain.xyz before, abcd.myd.infomaniak.com after).
    3. The username that accesses the MySQL database (for example userbdd before, abcd_userbdd after).
    4. The path of two directories /tmp and /logs:

 

Obtain updated information

For points 1, 2 and 3 of the preamble above:

  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 Database in the left sidebar.
  4. Find and keep your current MySQL information (need help?).

For point 4 of the preamble above:

  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 Manage under Advanced settings:
  4. Under the PHP | Apache tab, under PHP Information click on Show Information.
  5. At the line _SERVER['DOCUMENT_ROOT'] copy the path to the right:

 

Modify the Joomla configuration.php file

Prerequisites

Then edit the configuration.php file which is in the root folder of your Joomla:

  1. Find the relevant paragraph and update the 4 pieces of information in the preamble above.
  2. Also replace the old path (including "www") with the new path:
     
  3. Save the file; your Joomla will now connect to the correct database.

 

Check the changes made

On the Joomla interface, it is possible to check the paths of the /logs and /tmp folders:

  • For the /logs folder: go to System / Configuration then System
  • For the /tmp folder: go to System / Configuration then Server

Link to this FAQ:

https://faq.infomaniak.com/272

Has this FAQ been helpful?

This guide concerns IonCube Loader, a PHP module that allows decoding of PHP scripts that have been encoded with IonCube Encoder.

 

Preamble

  • IonCube encoding is used to protect the source code of an application and prevent its modification or illegal distribution.
  • By using IonCube Loader, website owners can ensure the security of their code and content while allowing secure and easy distribution of their applications.

 

Using ionCube Loader

With shared hosting it is no longer offered. You can check this from the dashboard:

  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 Manage under Advanced settings:
  4. Click on the PHP Extensions tab.
  5. Click on ionCube Loader (if present in the list) to view the details:

Link to this FAQ:

https://faq.infomaniak.com/285

Has this FAQ been helpful?

In terms of free software for handling multimedia files, FFmpeg is a powerful and flexible tool. It can be used to convert, edit, and stream videos and audio.

However, using FFmpeg on shared hosting presents certain issues and limitations for both users and hosts.

You should opt for the Cloud Server offer for using FFmpeg.

You can also opt for the Infomaniak VOD/AOD service.

Link to this FAQ:

https://faq.infomaniak.com/286

Has this FAQ been helpful?