This guide explains how to add or remove a dedicated IP to a website. Learn more

Ordering Dedicated IPs

To order one or more dedicated IPs:

1. Log in to the Infomaniak Manager (manager.infomaniak.com) from a web browser like Brave or Firefox
2. Click on the ‍ icon at the top right of the interface (or navigate through the left side menu, for example)
3. Choose Hosting (universe Web & Domain)
4. Click on the name of the relevant object in the displayed table
5. Click on the shopping cart (in the Information section)
   
6. Choose the desired number of IPs
7. Click Validate and follow the wizard

Adding a Dedicated IP to a Website

To use a previously ordered IP on your site:

1. Log in to the Infomaniak Manager (manager.infomaniak.com) from a web browser like Brave or Firefox
2. Click on the ‍ icon at the top right of the interface (or navigate through the left side menu, for example)
3. Choose Website (universe Web & Domain)
4. Click on the name of the relevant object in the displayed table
5. Click on Dedicated IPs in the left side menu
6. Click on the blue button
   
7. Install the dedicated IP on the respective site

Uninstalling a Dedicated IP

To deactivate a previously installed dedicated IP on a site:

1. Log in to the Infomaniak Manager (manager.infomaniak.com) from a web browser like Brave or Firefox
2. Click on the ‍ icon at the top right of the interface (or navigate through the left side menu, for example)
3. Choose Website (universe Web & Domain)
4. Click on the name of the relevant object in the displayed table
5. Click on Dedicated IPs in the left side menu
6. Click on the action menu ⋮ to the right of the relevant object in the displayed table
7. Click on Deactivate
   
    

This guide helps you understand the different HTTP status codes.

1xx - Informational

Error 100: Continue
 The server has received the request headers, and the client can continue sending the request body.
 
Error 101: Protocol Change
 The server agrees to change the communication protocol as requested by the client.

2xx - Success

Error 200: Request succeeded
 The request has been successfully processed by the server.

Error 201: Document Created (reason: new URI)
 The request has succeeded and resulted in the creation of a new resource.

Error 202: Request Accepted for Async Processing (TBS)
 The request has been accepted, but the processing is not yet complete.

Error 203: Non-Authoritative Information
 The server successfully processed the request, but the returned information comes from a third-party source.

Error 204: No Content
 The request has been successfully processed, but there is no content to return.

Error 205: Reset Content
 The server has successfully processed the request and requests the client to reset the document that submitted the request.

Error 206: Partial Content
 The server is returning only part of the data, as requested by the client with the `Range` header.

3xx - Redirections

Error 300: Multiple Choices
 The request has multiple possible responses, and the server cannot automatically choose one of them.

Error 301: Moved Permanently
 The requested resource has been permanently moved to a new URL.

Error 302: Found (Moved Temporarily)
 The requested resource is temporarily located at another URL.

Error 303: See Other
 The response to the request can be found under a different URL using the GET method.

Error 304: Not Modified
 The resource has not been modified since the last request. No new data will be returned.

Error 305: Use Proxy
 The requested resource must be accessed through the proxy specified by the server.

Error 307: Temporary Redirect
 The requested resource resides temporarily under a different URL, but the client must use the same method for the next request.

4xx - Client Errors

Error 400: Bad Request
 The request is invalid or malformed.

Error 401: Unauthorized
 Access to the resource requires authentication.

Error 402: Payment Required
 This code is reserved for future use regarding online payments.

Error 403: Forbidden
 The server understands the request but refuses to authorize it.

Error 404: Not Found
 The server cannot find the requested resource.

Error 405: Method Not Allowed
 The method specified in the request is not allowed for the resource.

Error 406: Not Acceptable
 The requested resource is not capable of generating acceptable content according to the `Accept` headers sent in the request.

Error 407: Proxy Authentication Required
 Access to the resource requires authentication by a proxy.

Error 408: Request Timeout
 The server did not receive a complete request within the time limit.

Error 409: Conflict
 The request cannot be processed due to a conflict with the current state of the resource.

Error 410: Gone
 The requested resource is no longer available and will not be available again.

Error 411: Length Required
 The server refuses to process the request without a valid `Content-Length` header.

Error 412: Precondition Failed
 One of the conditions specified in the request headers has failed.

Error 413: Payload Too Large
 The server refuses to process the request because the size of the payload is too large.

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

Error 501: Not Implemented
 The server does not support the functionality required to fulfill 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 (overloaded or in 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.

This guide explains how to view and download Apache logs for Web Hosting, which are useful for troubleshooting PHP scripts or certain programming errors.

Accessing Access and Error Logs

To view these logs:

1. Log in to the Infomaniak Manager (manager.infomaniak.com) using a web browser like Brave or Firefox.
2. Click on the icon at the top right of the interface (or navigate through the left side menu, for example).
3. Choose Website (under the Web & Domain universe).
4. Click on the name of the relevant object in the displayed table.
5. Click on Access and Error Logs in the left sidebar.

This guide is for users making changes around a hosting where WordPress is installed.

Following a change in your Web hosting offer (migration from the old hosting plan v1 60 GB to the current offers), you may need to update the connection between the MySQL/MariaDB database and your WordPress site (to avoid the "error establishing a database connection" error for example) and thus restore the link between WordPress and the MySQL/MariaDB database.

Elements to Modify

Here are the details to adapt in the wp-config.php file to make your WordPress site work (generally, a prefix has simply been added before the existing database name and username):

1. the name of the MySQL database (bddname before, abcd_bddname after, for example)
2. the MySQL database host server (mysql.domain.xyz before, abcd.myd.infomaniak.com after, for example)
3. the username accessing the MySQL database (userbdd before, abcd_userbdd after, for example)

Modify the wp-config.php file of WordPress

To do this:

1. retrieve and keep your current MySQL information according to the list above
2. create an FTP account
3. Connect via FTP
4. edit the wp-config.php file located in the root folder of your WordPress
5. find the relevant paragraph and update the 3 pieces of information (according to the list above)
6. save the file and that's it, your WordPress will now connect to the correct database

This guide concerns RTMP (Real-Time Messaging Protocol), a service that allows for real-time multimedia streaming on the Internet:

• It is a proprietary protocol developed by Adobe and its use requires the configuration of a dedicated RTMP server or the use of RTMP hosting services
• Viewers can access the live stream using an RTMP-compatible media player, such as VLC
• By default, RTMP is blocked by Infomaniak's security rules
• Contact Infomaniak support if you wish to set up an exception: you will need to provide the fixed IP address of the machine you wish to reach as well as the desired port number

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

Importing a Database

To export an Infomaniak database:

1. Log in to the Infomaniak Manager (manager.infomaniak.com) from a web browser like Brave or Firefox
2. Click on the icon in the top right corner of the interface (or navigate through the left side menu, for example)
3. Choose Hosting (in Web & Domain)
4. Click directly on the name of the relevant object in the displayed table
5. Click on Databases in the left side menu
6. Click on the Import button
   

Then you have the option to:

• Directly upload your database (sql, gz, bz2, zip, max 300 MB) from your computer
• Select the file to import from your hosting after depositing it on the server via FTP

and also choose:

• Import data to a new database (creation)
• Import to an existing database (replace/overwrite)

Alternative Method (for advanced users)

Prerequisites

• Have the *.sql file of the database to be imported
• Have created a new empty database
• Have a user with all rights to the database
• Have an FTP + SSH account

Importing via SSH

1. Upload the database to be imported via FTP to your hosting
2. Open the PuTTY application (download and install on PC) or Terminal (installed by default in macOS)
3. Enter and adapt the following command: ssh ftp-user@server-address
   • Replace ftp-user with the FTP + SSH account username (e.g., abcd_user)
   • Replace server-address with the web server address of your hosting
4. Enter the password for the FTP + SSH account
5. Enter and adapt the following command: mysql --verbose -u db-user -p db-name -h db-host < path
   • Replace db-user with the database user name (e.g., abcd_user)
   • Replace db-name with the database name (e.g., abcd_sample)
   • Replace db-host with the MySQL server of your hosting
   • Replace path with the path where you uploaded 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)
6. Wait for the import to complete (this may take several minutes depending on its size)

This guide explains how to order Web Hosting with Infomaniak.

Ordering Web Hosting with Infomaniak

To order web hosting:

1. if necessary, create a customer account
2. log in to the Infomaniak Manager (manager.infomaniak.com) from a web browser like Brave or Firefox
3. click on Hosting (universe Web & Domain)
   
4. enter your hosting domain name and click Search (even if you manage it elsewhere)
5. two scenarios are possible:
   1. you don't own the domain name yet: click on the Next button
   2. you own and manage your domain names with another registrar: click on the action menu ⋮ for Order hosting only
6. choose the hosting plan that suits you
7. click Next
8. complete the order

You are already a customer and already own hosting

If you already have web hosting, you can add a site to an existing hosting without ordering or paying for new hosting (multi-site/multi-domain management).

Why choose Infomaniak as a web host?

• with a base of 250 GB SSD disk space, you won't run out of space for your online projects
• SSL certificates are free at Infomaniak and help enhance the security of your sites
• your sites are permanently protected against DDoS attacks. Learn more
• install WordPress, Joomla, PrestaShop, Drupal, ownCloud, and over 100 web applications in 1 click. Learn more
• use premium WordPress themes and extensions for free from Elegant Themes
• our web hosting is really fast, as it operates only with the latest generation SSD disks
• Infomaniak's support is easily accessible, and our knowledge base can answer most of your questions
• manage multiple websites or domain names with a single web hosting contract (multi-domain management)
• Infomaniak is ISO 14001 and ISO 50001 certified and has the most ecological data center in Switzerland. Learn more

This guide details the actions to take as a priority if you see no difference on your website after making changes to it, compared to its version before the changes. These tips are also valid if you encounter issues when using Infomaniak's product interface.

What is cache?

During your browsing, a web browser stores the data you've visited in a reserved space. This is done to avoid repeatedly requesting data from the server, which saves time and resources.

Your cache can contain a lot of data, and sometimes the browser gets confused. This can cause websites to display incorrectly or show an outdated version.

Clearing the cache ensures that you have the most up-to-date version of the page or folder you're viewing.

Clearing the web browser cache

Safari

Select your macOS version to read the corresponding Apple help (click here).

Google Tools (Chrome, Android, etc.)

Read the Google help (click here).

Firefox

Read the Mozilla help (click here).

Edge / Internet Explorer

Read the Microsoft help (click here).

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

Origin of the Errors

429 Too Many Requests

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

503 Service Temporarily Unavailable

This error can be caused by several factors, including scheduled maintenance work on the server, 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 a high number of simultaneous connections from the same IP address. Check "Access and Error Logs" on your hosting dashboard to find multiple entries like:

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

Resolution Steps

Some steps to resolve these errors:

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

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 access (CORS) from a web application.
 

List of Allowed Domains

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

To allow, for example, the site https://domain.xyz to access resources with CORS, the header should look like this:

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

You can set it using the header() function in PHP by referring to this guide in particular.

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