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 section of a website on a Web Hosting plan by requiring a password to be entered before a directory (including subdirectories) can be accessed from a browser.

Please note that this does not prevent a user from accessing the directory via FTP.

 

Simple method

To password-protect (Digest authentication) a directory using the "Folder Protection" tool:

  1. Click here to access the management of your website on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the website in question:
  3. Click on Security in the left-hand menu.
  4. Click on Folder Protection.
  5. Click on the directory you want to protect.
  6. Enable protection using the toggle switch, then create one or more users:
    • * Users are defined per directory; the tool does not allow you to manage user groups:
  7. Click the Add button.
  8. Click the button to Add access for an additional user if needed.
  9. Click on the action menu ⋮ located to the right of the user you want to modify or remove.
  10. Click on the toggle switch again to completely disable directory protection:

 

Manual method via .htaccess

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

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

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

    <?php
$password = "12345";
echo password_hash($password, PASSWORD_DEFAULT); // Displays the hashed password
?>
  3. Open a web browser and display the password.php file (example: domain.xyz/folder-to-protect/password.php).
  4. The web browser will display your encrypted password; copy the encrypted password, as you will need it later…

In the folder you want to protect, create a file called .htaccess and adapt the following content within it:

AuthName "Protected Administration Page"
AuthType Basic
AuthUserFile "/example/.htpasswd"
Require valid-user

Replace /example/ with the absolute path of the folder you want to protect. Example:

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

In the folder you want to protect, create a file called htpasswd.txt and adapt the following content within it:

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

Once the htpasswd.txt file has been 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 instructions have been followed correctly, the login and password (not encrypted) you chose will allow you to access the protected folder.

Other restrictions may also be applied via .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).

 

Introduction

  • To redirect traffic, you will need to take action…
    • … either on the domain name itself (it must be hosted by Infomaniak and its DNS must also be Infomaniak's),
    • … or on the code present in your pages (e.g., .htaccess page, homepage, etc.) if you have a website.

 

Acting on the domain name

Via Web Redirection Tool

The tool available in the Manager allows you to easily manage your domain name (or subdomain) and redirect it to the internet address of your choice.

via DNS modifications or A record updates

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

 

Modify the page code…

… by inserting HTML code

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 execution).

The Google search engine indicates that it is preferable to use a 301 redirect on the server-side (see below). The W3C also advises against using it.

… via PHP code to be inserted

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

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

… via the .htaccess file

… via fichier .htaccess

To redirect all traffic to your site (regardless of the page being accessed) to another address, insert the following into the .htaccess file at the root of your site:

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

To target the page that should be redirected:

Redirect permanent /old_page.html insert destination URL here

Redirectpermanent, Redirect permanent, and Redirect 301 are equivalent commands.

The following 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 for more information.

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 account, so that they are processed in the same way as a .php file.

 

Introduction

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

 

Manage PHP-recognized extensions

To add support for a specific file type:

  1. Click here to access the management of your website in the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the website in question:
  3. Click on Manage advanced settings:
  4. Click on the PHP / Apache tab:
  5. Edit the FPM Extensions field to add the desired extensions.
  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 websites (traffic statistics).

 

✘ UNAVAILABLE‍ with
Site Creator standalone (independent of web hosting; see this other guide regarding the Pro offer)
Starter hosting

 

Introduction

  • The results are presented in a simple format with graphs, allowing for easy interpretation.
  • Annual, monthly, daily, and hourly statistics are displayed by site, HTTP address, referring site, country, etc.
  • Refer to this other guide if you are specifically looking for access logs.

 

Access visit statistics

To view website traffic statistics:

  1. Click here to access the management of your website in the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the website in question:
  3. Click on Statistics in the left-hand menu:
  4. The top section allows you to choose:
    1. the type of statistics,
    2. the period,
    3. or to download the data for 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, or Google Analytics.

CategoryDescriptionDetails
HitsAny request sent to the server.Includes everything (HTML, images, audio, etc.). Each requested element, whether visible or not, counts as a hit. It's as if a visitor activated an invisible button with each interaction.
FilesRequests requiring data to be sent back.Records requests that require the server to return a file (graphic, HTML). The difference with hits corresponds to the ratio between incoming requests and outgoing data.
PagesNumber of pages displayed on your website.Measures the number of HTML pages viewed, excluding graphics or audio files. Each access to a new HTML page is recorded as a page view.
VisitsSessions based on the IP address.A visit starts with an IP request. If the address returns within 30 minutes, it is counted as a unique visit. After that, a new visit is recorded.
SitesEstimate visits via fixed IP addresses.Excludes mobile or dynamic connections. This targets regular visitors (businesses, institutions) to better understand your target audience.
KoVolume of data sent by the server.Total amount of data transferred during the period, calculated via log files (with a possible margin of error depending on the size of the files).
Total hitsTotal number of requests.A page with 3 images and text generates 5 hits (the page + the text + the 3 images). This total is therefore much higher than the number of page views.
Total Pages / VisitsEngagement metrics.The number of pages viewed compared to the number of unique visits allows you to assess the interest users have in your content.
Total number of unique sitesNumber of distinct IPs.Represents the diversity of traffic sources and helps identify the most active audience segments during the period.
Total unique URLsDistinct paths accessed.Corresponds to the different pages or files visited, providing an overview of your navigation structure and the most popular content.
Total number of unique referrersNumber of referring sites.External sites that directed traffic to you. This is a key indicator of the effectiveness of your marketing and partnerships.

 

Meaning of "Commercial (com)" and "Unresolved"

"Commercial" often represents a significant portion of geographic traffic. It includes users connected via internet service providers (ISPs) using a .com domain. As this extension is used by many ISPs and global companies, it does not allow for the identification of a specific country.

"Unresolved" refers to IP addresses that cannot be geographically located, often due to privacy settings, the use of VPNs, or network restrictions.

Link to this FAQ: https://faq.infomaniak.com/83

Has this FAQ been helpful?

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

 

Introduction

  • Apache2, which is installed 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 lead to 500 Internal Server Error errors or unexpected URL rewriting errors.

 

Examples of syntax 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

 

Troubleshooting 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 section that is causing the problem.
  • If the error occurs after a modification made to one of your pages, the easiest solution is to restore the previous version of the file.

Link to this FAQ: https://faq.infomaniak.com/106

Has this FAQ been helpful?

This guide details CHMOD (short for change mode), which allows you to change the access permissions of a file or directory.

 

Modify FTP Permissions

The permissions (see this other Wikipedia guide) available for each user/group are as follows:

  • read: grants the right to list (also requires execute permission) and read within a directory and/or read a file.
  • write: grants the right to create, modify, rename, and delete files and/or directories
  • execute: for a directory: grants the right to access it to read its subdirectories -> For a file: grants the right to execute it if it is a program or script, for example.
  • set uid (?): for a file with execution rights, this will cause it to be executed with the rights of the owner if the execve or setuid system call is used.
  • set gid (?): all new files created will belong to the group of the directory, and for a file with execution rights, this will cause it to be executed with the rights of the group.
  • sticky bit (?): on a directory, files in the directory can only be renamed or deleted by the owner, even if other users have write permissions. This permission is not very useful for files.

The Web FTP in the Manager allows you to change file permissions (including the permissions for /web).

Most FTP software/clients allow you to change file access permissions; this function is usually called "CHMOD" and can be found under "Properties," "Permissions," or "Attributes" (usually by right-clicking on the file or folder to be modified). A checkbox often allows you to apply the permissions to all subdirectories and files in the folder, in recursive mode.

Once you have checked the permissions you want, validate them, and the rights will be modified, except for those you do not have permission to modify, or rather, that the user you are logged in as does not have the right to modify.

Example with Filezilla:

 

Learn more

When we talk about changing permissions, it usually involves using a command like "chmod 777", "chmod 666", or something similar. This involves three digits:

  • the first corresponds to the owner's rights
  • the second corresponds to the group's rights
  • the third digit corresponds to the rights of other users.

And the rights are broken down as follows:

  • "4" for read access
  • "2" for write access
  • "1" for execute permission

Simply add these numbers together. For example, if you want all permissions for the owner but no permissions for others, you would use "chmod 700" (4 + 2 + 1 = 7). If you only want read and write permissions for everyone (4 + 2 = 6), you would use "chmod 666".

These values are recognized by any standard FTP software/client, so you can directly enter the number in your FTP software/client to change the permissions.

To change permissions on files or directories in PHP, you can also use the “chmod” function, as in the following example:

chmod ("/a_folder/a_file", 0755)

Note that the value to be applied must be in octal format, hence the mandatory leading zero. Be careful if you store the value in a variable, as you will encounter a data type issue, which you can circumvent using the octdec() function, as in the following example:

$mode = 0755;chmod("a_folder/a_file", octdec($mode))

Link to this FAQ: https://faq.infomaniak.com/111

Has this FAQ been helpful?

This guide covers installing PHP extensions on Infomaniak Web Hosting.

 

Using PHP Zend Extensions

Attention:

  • 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 plans 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 or later.

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 makes navigation easier for visitors and allows for more advanced customization of how files are displayed.

 

Introduction

  • 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 makes it easier for visitors who are not familiar with the site's file structure to navigate. They can simply browse 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 such as:
Access denied!
You do not have permission to access the requested directory.
Either there are no indexed documents or the directory is protected.
If you believe this is a server error, please contact the site administrator.
Error 403

 

List the contents of a web folder

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

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

Please note that this solution will only work if there are no index files in the directory in question; you will need to remove the index.php, index.html, index.htm files, etc., as well as any welcome.php file...

 

Customize 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 appealing appearance, specifies the file sorting order, defines the column width for the file name and description, and specifies the file names 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, Managed Cloud Server only):

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

 

These functions are disabled by default because they pose a significant security risk if a website is hacked. Only enable them if absolutely necessary (for a script or CMS such as ImageMagick, Typo3, CraftCMS, etc.).

 

Enable PHP functions

To access website management:

  1. Click here to access your website management on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the site in question:
  3. Click on Manage advanced settings:
  4. Click on the PHP / Apache tab:
  5. Click on the On/Off toggle buttons as desired:
  6. Click the Save button at the bottom of the page to apply 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.

 

Using the MySQL InnoDB storage engine

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

InnoDB offers advanced features such as ACID transactions, row-level locking, 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 and shows how to use it on an Infomaniak Web Hosting service using a .htaccess file.

 

Introduction

  • URL rewriting allows you to present more readable and explicit addresses, for example by replacing a URL such as index.php?id=123 with /article/123/.
  • Clear URLs make it easier for visitors to navigate and can help improve natural search engine optimization (SEO) by highlighting the content of the page.
  • This technique also makes it possible to hide certain technical details of the application, such as file extensions or the use of parameters in the URL, without changing the way the site works.

 

Example of URL rewriting

The following example transforms a URL such as article.php?id=25&cat=4 into a more readable URL in the form /article/25/4/.

Add the following rules to the .htaccess file located in the root directory of your site:

# Disable directory listing and allow symbolic links owned by the same user
Options -Indexes +SymLinksIfOwnerMatch

# Enable the rewrite engine
RewriteEngine On

# Set the rewrite base if your site is installed in a subdirectory
# RewriteBase /admin/

# Rewrite rule
RewriteRule ^article/([0-9]+)/([0-9]+)/?$ article.php?id=$1&cat=$2 [L,QSA]

The options used in this rule have the following meaning:

  • L (Last): indicates that no other rewrite rule should be applied if this one matches.
  • QSA (Query String Append): preserves any additional parameters that may already be present in the URL.

Important: Creating these rules does not automatically update the links on your website. You must update your internal links so that they use the new URL format.

 

Redirect to a primary domain

If multiple domain names point to the same website, it is recommended to redirect all secondary domains to a primary domain. This practice avoids duplicate content and allows search engines to index only one version of your website.

Example of a permanent redirect to a primary domain using 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 option indicates that this is a permanent redirect. Browsers and search engines are thus informed that the content is now accessible at this new address.

Link to this FAQ: https://faq.infomaniak.com/206

Has this FAQ been helpful?

This guide details the Rejected, too many connections from this host error if it occurs when visiting a website.

 

Cause of the error

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 may be due to heavy site usage or abuse.

503 Service Temporarily Unavailable

This error may be caused by several factors, including planned server maintenance, server overload due to high traffic, or the execution of 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 the high number of simultaneous connections from the same IP address. Consult the "Access and Error Logs" on your hosting dashboard to find multiple entries in the following format:

[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 address 222.111.123.123 is making 30 simultaneous connections to each page, and is therefore automatically rejected, as this may resemble an attack or scan.

 

Possible solutions

Here are some possible solutions to resolve these errors:

  • Check the scripts that make multiple connections to the server to display data.
  • Optimize the script(s) in question so that they require fewer resources.
  • Increase the limits for the website in question to allow the script to perform all necessary operations 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 service for specific visitors, bots, or crawlers by filtering and blocking their IP addresses or hostnames.

 

Setting up .htaccess rules

Create a .htaccess file in the root directory of your website and add the rules to block specific IP addresses or bots.

 

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

Order Deny,Allow
Deny from 123.456.
Allow from all

This means that all requests originating 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 only one 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 of "BadBot" will be blocked, while all other users can access the site.

Block access to a specific folder

Order Allow,Deny
Deny from all

This means that all access to the "/folder" directory 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 exercise caution when modifying your .htaccess file.

Here are some examples:

Block a specific IP address

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

This means that only one 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 of "BadBot" will be blocked, while all other users can access the site. This can be useful to prevent unwanted bots 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 access to the "/dossier/secret" folder 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 coming from the IP address 123.456.789 will be redirected to the "blocked.html" page on the "www.domain.xyz" website. The last part of the RewriteRule, [L,R=301] line indicates that the redirection is permanent (R=301) and that this is the last rule to be applied (L).

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

You may also find this other guide helpful: 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 hostings, 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 Hostings (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.

 

Messaging

 

Domains / DNS Zones

Link to this FAQ: https://faq.infomaniak.com/250

Has this FAQ been helpful?

This guide helps you set up the Access-Control-Allow-Origin header, 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.

 

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 Access-Control-Allow-Origin header.

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 referring to 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 - Informational

Error 100: OK to continue
The server has received the request headers and the client can continue sending the request body.

Error 101: The server has switched protocols
The server accepts changing the communication protocol as requested by the client.

 

2xx - Success

Error 200: Request successful
The request was 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 processing is not yet complete.

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

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

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

Error 206: Incomplete GET request
The server only returns a portion 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 multiple 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 a different URL.

Error 303: Redirection with new access method
The response to the request can be found at a different 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: Redirect to a proxy specified by the header
The requested resource must be accessed through a specified proxy.

Error 307: Temporary Redirect
The requested resource is temporarily located under a different 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 requires payment
This code is reserved for future use regarding online payments. Services outside of Infomaniak use it in some cases to indicate a payment problem, but these uses are specific to these platforms – not a global standard.

Error 403: Access to the server is not authorized
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 allowed
The method specified in the request is not allowed for the target resource.

Error 406: Request not accepted by the server
The requested resource is unable to generate content acceptable according to the Accept headers sent in the request.

Error 407: Proxy authentication required
Access to the resource requires authentication through a proxy.

Error 408: Request timeout
The server did not receive the complete request within the allotted time.

Error 409: The user must resubmit with more information
The request could not 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 has been permanently removed.

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 failed.

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

Error 414: Request-URI 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 prevented it from fulfilling the request.

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

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

Error 503: Service unavailable
The server is currently unavailable (overload or 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 names of the home pages that you can have on your Infomaniak Web Hosting, and which will be prioritized when a visitor accesses your website via its domain name.

 

Regarding Site Creator, please refer to this other guide.

 

Introduction

  • Default home pages 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, such as index.html, index.php, index.htm, or other similar variations.

 

Homepage Priority Order

The following pages are loaded by default at Infomaniak, in order of priority:

  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 in the root directory of your hosting account, based on the ranking above, you will see that index.php is recognized as the priority page over welcome.php.
  • You can also conclude that if you only have welcome.php as a page in the root directory, it will be loaded and function as the homepage.
  • If you have a home.html page, 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 homepage to be loaded by default, 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 accueil.html. If it doesn't find accueil.php, it will then look for index.php, and finally index.html.

Link to this FAQ: https://faq.infomaniak.com/261

Has this FAQ been helpful?

This guide details the "Database connection error: could not connect to mysql" error, which may occur when making changes to an Infomaniak hosting environment on which the Joomla web application is installed.

 

Introduction

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

 

Get the 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-hand menu.
  4. Find and save your current MySQL information (need help?).

Regarding point 4 of the introduction above:

  1. Click here to access the management of your website in the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the website in question:
  3. Click on Manage advanced settings:
  4. Click on the PHP / Apache tab:
  5. Copy the path displayed in the first field under Auto Prepend File at the bottom:

 

Modify the configuration.php file in Joomla

Prerequisites

Then, edit the configuration.php file, which is located in the root directory of your Joomla:

  1. Replace the old log and tmp paths with the new path:
  2. Find the relevant paragraphs for the rest of the information in the introduction above:
  3. Save the file; your Joomla will now connect to the correct database.

 

Check the changes made

In the Joomla interface, you can check the paths of the /logs and /tmp folders:

  • For the /logs folder: go to System / Configuration then Logs:
  • 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 site on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the site concerned:
  3. Click on Manage advanced settings:
  4. Click on the PHP Extensions tab.
  5. Click on ionCube Loader (if present in the list) to see the details:

Link to this FAQ: https://faq.infomaniak.com/285

Has this FAQ been helpful?

When it comes to open-source 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 challenges and limitations, both for users and hosting providers.

We recommend the Cloud Server offer for using FFmpeg.

You can also consider the Infomaniak VOD/AOD service.

Link to this FAQ: https://faq.infomaniak.com/286

Has this FAQ been helpful?