Move websites, databases and mailboxes to cloud hosting

There can be many reasons for a move:

• The project needs to be updated and requires a newer PHP or MySQL version.
• The project does not support current PHP or MySQL versions and cannot be updated yet.
• The maximum mailbox size of 10 GB in Classic Hosting is not sufficient.
• Multiple packages should bemanaged in one customer account.
• You don't want to spend money on SSL certificates and use free Let's Encrypt certificates instead.

PHP and MySQL versions in Classic Hosting

In the data center in Cologne, which was previously used for the Classic Hosting packages, only PHP versions 5.6 to 7.3 are currently provided. Older PHP versions that are no longer provided with security updates have been removed from the servers. Newer PHP versions 7.4 or 8.0 and 8.1 cannot be provided in the existing tariffs.

A migration of the databases from MySQL 5.6 to MySQL 5.7 is planned before the end of this year.

PHP and MySQL versions in cloud hosting

In our cloud hosting tariffs, we continue to offer the old PHP versions (from version 4.4) as "Hardened PHP" in addition to the current PHP versions. These hardened PHP versions will continue to be provided with security updates. When new security updates are released for current PHP versions, these updates are also applied to the old PHP versions as far as this is technically possible (backport, see https://de.wikipedia.org/wiki/Backport).

Besides a MySQL 5.7 compatible MariaDB 10.3 database, MySQL 5.6 databases are still available.

When migrating MySQL 5.6 to MySQL 5.7 databases, it may happen that programs are not compatible with MySQL 5.7, which causes the website to malfunction.

The affected domain (website) will then usually stop working. Depending on the application and configuration, a blank (white) page appears instead because the PHP error messages are not enabled, or error messages are displayed.

If further old PHP versions have to be switched off due to security vulnerabilities, PHP version 7.3 will be discontinued for the affected domain.

Depending on the application, the programming may not be compatible with PHP 7.3 and a blank white page will appear (PHP error) or error messages will be displayed. In this case the application must be updated by a developer.

There will be no data loss, all data will still be available on the webspace.

To continue running web applications with outdated or newer PHP or MySQL versions, we recommend moving to our new cloud hosting plans.

For this you will need to sign a new hosting contract. All actively used files, databases and e-mail accounts as well as forwardings and DNS entries have to be moved from the data center in Cologne to the data center in Frankfurt. From a technical point of view, this is a change of provider.

There are several options for carrying out the move

1. You carry out the move yourself.
2. You commission your agency or the creator or programmer of the website with the move.
3. You commission us with the relocation of the websites. However, since our available capacities are limited, there may be longer waiting times.

In the following you will find the necessary steps. Depending on the option, parts will be done by us, your agency or yourself.

For all three options, please note that we cannot take over the relocation of the email inboxes. The necessary steps can be found under Step 8: Transfer e-mail boxes.

To perform the move, it is absolutely necessary to work on the 'shell' of the source and destination servers. The login on the shell is done via the SSH access and a terminal program. On Windows, use a program such as PuTTY or Mobaxterm.

Instructions for working on the shell.

If you don't have any experience with working on the shell so far, it is advisable to hire someone who already has experience with it to do the move.

Before the move can begin, a new hosting plan must first be ordered and set up.

We offer three cloud hosting plans to choose from: Cloud BASIC, Cloud PREMIUM and Cloud POWER. These differ in terms of storage space, performance and additional features.

We recommend the Cloud PREMIUM plan, which, in addition to 100 GB of storage space, also has numerous functions that are useful for developing and optimizing websites.

If, on the other hand, you only want to continue operating an existing website, the Cloud BASIC tariff with 30 GB of storage space could also be sufficient.

In our tariff overview, you can add the desired tariff directly to the shopping cart and complete the order as a new customer in our system. You also have to enter the bank details again if you want us to continue collecting the invoices by direct debit.

The package will automatically receive a free development domain from our system , according to the pattern 90xxxx.jweiland-hosting.de (the domain currently used by you will only be transferred when the move is completed).

Important note: When concluding a cloud hosting package, the conclusion of a contract for order processing with us is mandatory according to DSGVO. The hosting package will be activated as soon as this contract has been completed and signed.

While you had to book several packages with different customer numbers in Classic Hosting, there is now the possibility to book several packages in one customer account under one customer number in Cloud Hosting. Under this customer account you can now book as many cloud hosting plans (shared hosting or servers) as you like. Additional logins can be created for each of the booked tariffs, different authorizations are also possible.

A customer account is uniquely identified by the specified e-mail address, which thus cannot be used for multiple customer accounts. The address entered in the order or in the customer account corresponds to the billing address. Tariffs, domains or other additional services that are due at a certain time are billed in one invoice.

In this chapter we will provide troubleshooting tips in case the website on cloud hosting does not work as expected.

If an error 500 is displayed when calling the website, the following tips can help to fix it:

1. Delete the TYPO3 folder typo3temp/var/Cache.
2. Check if the file .htaccess in the start directory contains one of the following entries, if yes comment (prefix the line with #):Options +FollowSymLinks Options -Indexes Options +Indexes