This guide explains how to migrate a shared web hosting to a Cloud Server by retrieving all its data, websites, databases, etc.

Preamble

• If you already have a **Serveur Cloud**, go straight to step 2 of this guide.
• To migrate a web hosting from one Server Cloud to another Server Cloud, refer to this other guide.
• To migrate a web hosting from a Server Cloud to a shared web hosting, refer to this other guide; note that this is a manual operation.

1. Order a Cloud Server

For this:

1. Click here to access the management of Cloud Servers on the Infomaniak Manager (need help?).
2. Click on Order, choose a Managed Cloud Server and follow the assistant to complete the order:
   

2. Migrate the hosting to the Cloud Server

Once the Cloud Server is up and running:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on the action menu ⋮ located to the right of the relevant item.
3. Click on Change Offer:
    
   
    
4. Select the free transfer offer.
5. Select the Serveur Cloud to which to migrate your hosting:
   ‍
6. Click on the Next button at the bottom of the page and complete the procedure entirely.‍
7. Please wait during the hosting migration, a service interruption will be felt during the process.
8. Note:
   1. The names of the databases and database users are retained.
   2. FTP accounts are retained with the same names, but the host server changes to an address of type xxxx.ftp.infomaniak.com.
   3. The IP addresses of the sites will change except for dedicated IPs.

This guide provides tips to perform operations related to a WordPress site, which notably allows you to…

• …copy and migrate a WordPress site from a competing host to Infomaniak,
• … change the domain name of a WordPress site,
• … backup an entire WordPress site…

Preamble

• Depending on the context, instead of performing a WordPress transfer, you can also simply…
  • … change the site address (the associated domain name) very easily if you have installed WordPress via the Infomaniak installer,
  • … duplicate a WordPress site to work in parallel in a development environment…
• Make your life easier! If needed, **local partners recommended by Infomaniak can handle these tasks**. Launch a free tender. They take care of everything, freeing you from technical details.

Transfer a WordPress site…

… with the All-in-One WP Migration extension

• Refer to this guide.
• Requires installing a new, clean WordPress (for example via the automatic Infomaniak installer) to import the old site onto it.

… with the Duplicator extension

• Refer to this guide.
• Requires connecting to the hosting via FTP to send a .zip archive and a PHP file to reinstall the old site.

This guide explains how to use PHPMailer with the Web hosting.

Introduction

• PHPMailer is a library that allows sending HTML-formatted emails from a website.
• It notably handles attachments, and supports SMTP authentication and multipart/alternative for clients who cannot read HTML-formatted emails.

Using PHPMailer

To use PHPMailer, it is necessary to install it manually:

1. Click here to download the PHPMailer library.
2. Copy the files into a directory of your website via FTP.

3. Link your script to PHPMailer, example:

   require_once('chemin_a_modifier/class.phpmailer.php');

Fixing a Sender mismatch error

In the SMTP (Simple Mail Transfer Protocol) protocol, the From header specifies the email address of the message sender. This is the address that will appear in the ‘From’ field of the message received by the recipient.

In PHPMailer, the method setFrom is used to set the sender's email address, while the header From is used to specify this same address when sending the message. The method setFrom also sets the Reply-To field of the email.

The error Sender mismatch SMTP code: 550 Additional SMTP info: 5.7.1 occurs when the email address specified in the setFrom field does not match the email address specified in the From header when sending the message.

To avoid this error:

1. Instead of using the setFrom method to set the sender's email address, use the From property of the PHPMailer object, example:

   $mail = new PHPMailer();
   $mail->From = 'expediteur@domain.xyz';

2. Make sure the value specified in the From property exactly matches the email address used in the setFrom field.

   Example, if you use setFrom with a sender name like this:

   $mail->setFrom('expediteur@domain.xyz', 'Nom Expediteur');

   … then make sure that the value of From is also set with the sender's name:

   $mail->From = 'expediteur@domain.xyz';
   $mail->FromName = 'Nom Expediteur';

Then, continue with the configuration and sending of the email as usual.

Learn more

• Authenticated Mail (SMTP) from a website
• Unauthenticated mail via PHP mail()

This guide explains how to generate a certificate signing request (CSR) for a domain name and all its subdomains with a Web Hosting. This allows you to encrypt the connection to your domain name and all its subdomains via SSL.

Setting up a Wildcard certificate

1. Add a wildcard domain alias with asterisk *

To add a wildcard alias * to your website:

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. Then click on the chevron ‍ to expand the Domains section of this site.
4. Click on the Add a domain button:
   
5. Enter the domain name to add in this format:
   • *.domain.xyz (the asterisk is mandatory, followed by a dot, then the domain name of the website which is domain.xyz in this example)
6. Click on the Confirm button to complete the procedure:
   

2. Install a SSL certificate or update it

Example of updating the existing certificate to include the wildcard sub-domain *:

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 relevant product.
3. Click on SSL in the left sidebar.
4. Click on the action menu ⋮ located on the right.
5. Click on Change the certificate:
   
6. Select the same certificate that you already own.
7. Click on the button Next:
   
8. Make sure the recently added subdomain is selected.
9. Click on the Install button at the bottom:
   
10. Wait for the creation or update to complete.

This guide explains how to view and download Apache logs from Web Hosting useful for correcting PHP scripts or certain programming errors.

Preamble

• Infomaniak keeps the last 500 error or access displays for a maximum retention period of 10 days.
• It is impossible to perform a previous search even upon request.
• You can also find these logs on the server via FTP in the /ik-logs folder.

Accessing the access and error logs

To display these logs:

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 relevant product.
3. Click on Logs in the left sidebar:
   
4. Click on Errors or Access to display the error log or access log.
5. Click on Send by email to immediately receive all entries by email at your user address:
   

This guide explains how to prevent cyberattacks and how to avoid hacking of the website you manage.

The role of the hoster

Infomaniak's job is to provide high-quality hosting, so it is crucial to respond extremely quickly to the various and varied attacks that any Internet actor may be subject to. Infomaniak therefore does everything possible to take the maximum precautions against hacking, notably by keeping the different versions of the technologies used up to date.

In the case of a proven hacking, if it is possible to track down the author and the machine has been compromised due to a security flaw on Infomaniak's part, and the integrity of the servers is at stake, Infomaniak takes care of it itself.

The role of the site owner and the webmaster

If your site has been hacked due to your responsibility (an outdated script, a security patch that has not been applied, etc.), Infomaniak will contact you to warn you of a problem that needs to be resolved quickly. Some organizations like Saferinternet can also suspend the domain name upstream, which will disable the site but also the email.

Infomaniak cannot counter exploits related to a bug in your PHP code or otherwise. If the hacking is not detected, you will generally notice the intrusion quite quickly through suspicious elements on your pages or by receiving numerous error emails.

It is therefore your responsibility to manage the evolution of your website over time and to ensure that it does not become neglected, even if it means hiring a webmaster whose job it is.

Infomaniak's recommendations

1. Update all your web applications (WordPress, Joomla, Drupal, ownCloud, etc.) regularly.
2. Keep the PHP version of your site on Infomaniak servers up to date.
3. Keep your site up to date by migrating to new offers when they are proposed to you.
4. ‍Add a protection system to your contact forms (captcha, etc.) and any "recommend to a friend" tools (tell-a-friend...).
5. Regularly run a antivirus scan of the hosting.
6. Monitor the vulnerability detection tool.
7. Remove anything you did not develop yourself and for which the author has not provided an update or correction in several months.
8. Perform regular backups of your site (refer to this other guide if you use WordPress) when everything is fine and keep it safe (since automatic backups are only kept for a few days and this is sometimes not far enough back to restore after you notice an intrusion).
9. Visit ibarry.ch.

If an issue has occurred...

1. Change the passwords of your Web applications, your FTP accounts and your databases after previously checking that no virus is on your computer.
2. Restore a backup but update immediately whatever can be updated as soon as the restoration is complete.

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

Manage dedicated IPs on a hosting plan

Order one or several first dedicated IP addresses

To do this:

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 relevant product.
3. Click on Web in the left sidebar.
4. Click on Dedicated IPs in the left sidebar.
5. Click on the button to order one or more IP addresses:
   

Order one or several additional dedicated IP addresses

To do this:

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 relevant product.
3. Click on Web in the left sidebar.
4. Click on Dedicated IPs in the left sidebar.
5. Click on Order :
   

Associate a dedicated IP address with a website on a hosting plan

Once the IP has been ordered and paid for, familiarize yourself with the prerequisites below, as switching to a dedicated IP address for a website may cause a temporary interruption, especially in the presence of a certificat SSL Let’s Encrypt. To limit the impact:

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

To switch to a dedicated IP address:

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 relevant product.
3. Click on Web in the left sidebar.
4. Click on Dedicated IPs in the left sidebar.
5. Click on the button to dedicate the IP to a site on your hosting:
   
6. Select the site to assign the new IP address to.
7. Check the box after reviewing the warnings.
8. Click on the Associate button:
   

Remove a dedicated IP address from a website

Once the IP is installed, to uninstall it:

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 relevant product.
3. Click on Web in the left sidebar.
4. Click on Dedicated IPs in the left sidebar.
5. Click on the action menu ⋮ located to the right of the relevant item.
6. Choose Unbind:
   
7. Take note of the warnings and confirm the deletion to complete the IP uninstallation procedure.

This guide helps you understand the various 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 protocols as requested by the client.

2xx - Success

error 200: Request successful
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 processing is not yet complete.

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

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

error 205: Request completed but form empty
The server has 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: Moved Permanently
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 under another URL using a GET method.

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

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 temporarily resides under a different URL, but the client must use the same method to make the next request.

4xx - Client Errors

Error 400: Bad request
The request is incorrect or malformed.

error 401: No authorization to access the document
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: The requested page does not exist
The server cannot find the requested resource.

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

Error 406: Request not acceptable 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 Authentication Required
Access to the resource requires authentication by a proxy.

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

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 has 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 size of the entity 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 prevented it from fulfilling the request.

error 501: Requested feature not supported by server
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 not available at the moment (overloaded 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.

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

Preamble

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

Modify the important elements

Here is the information to update in the wp-config.php file to ensure your WordPress site works (in most cases, a prefix has simply been added to the existing database name and username):

1. the name of the MySQL database (database namebefore, abcd_database name after, for example)
2. the MySQL database host server (mysql.domain.xyz before, abcd.myd.infomaniak.com after, for example)
3. the username that accesses the MySQL database (userbddbefore, abcd_userbdd after, for example)

Modify the WordPress wp-config.php file

To do this:

1. Find and keep your current MySQL information according to the list above.
2. Create an FTP account.
3. Log in via FTP.
4. Edit the wp-config.php file located in the root folder of your WordPress site.
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 the streaming of multimedia content in real-time over 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 have an exception set up:
  • You will need to provide the fixed IP address of the machine you wish to reach as well as the desired port number.