Import backup
Classic Hosting
In the customer menu [Configuration ' Cronjob], we create a cronjob that creates a backup of the TYPO3 projects and databases installed during setup in the web space every night. We show you how to restore the data from the backup in our video tutorial: Restore project from backup
If you don't want to carry out a restore yourself, you can place an order with us online, the costs are 20 euros per order (incl. VAT).
If the project directory name changes or additional projects are added, the backup script (daily) must be adapted accordingly. We show where and how in our video: Backups: Adding projects to the backup
In addition to these local data backups, data is also backed up to external systems. In this case, a restore must be ordered from us: online restore form
Which PHP versions are available?
Cloud hosting
The PHP version can be selected for each domain or subdomain. This allows several PHP versions to be operated in parallel in one hosting package. This is particularly useful when upgrading the CMS software if the new version requires a higher PHP version. The following PHP versions are available:
- PHP 8.4 (recommended for TYPO3 12, 13)
- PHP 8.3 (recommended for TYPO3 11, 12, 13)
- PHP 8.2 (recommended for TYPO3 11, 12, 13)
- PHP 8.1 (recommended for TYPO3 11, 12)
- PHP 8.0 (recommended for TYPO3 11)
- PHP 7.4 (recommended for TYPO3 10, 11)
- PHP 7.3 (recommended for TYPO3 8, 9, 10)
- PHP 7.2
- PHP 7.1
- PHP 7.0
- PHP 5.6
- PHP 5.5
- PHP 5.4
- PHP 5.3
- PHP 5.2
- PHP 5.1
The older versions, which are no longer officially supported by php.net, also receive regular security updates from us. These are the hardened PHP versions of Cloud Linux
Classic Hosting
Selectable PHP versions in Classic Hosting (per domain)
- PHP 8.3 (recommended for TYPO3 11, 12, 13)
- PHP 8.2 (recommended for TYPO3 11, 12, 13)
- PHP 8.1 (recommended for TYPO3 11, 12)
- PHP 8.0 (recommended for TYPO3 11)
- PHP 7.4 (recommended for TYPO3 10, 11)
- PHP 7.3 (recommended for TYPO3 8, 9, 10)
- PHP 7.2
- PHP 7.1
- PHP 7.0
- PHP 5.6
OpCache is automatically activated in PHP. The cache can be deactivated with the entry opcache.enable=0; in a .user.ini file in the start directory of the domain.
A separate PHP version can be selected for each main domain (but not for subdomains). Switching between PHP versions takes effect within a few minutes. This allows you to quickly test whether a new PHP version works - if not, simply switch back again.
For simultaneous testing of different PHP versions, free development domains (ending in .webseiten.cc) can be booked in the customer menu under Order ' Domains.
How is PHP configured?
Cloud hosting
When the PHP version for a website is set in Plesk, individual parameters such as memory_limit (default: 256 MB) and upload_max_filesize (default: 128 MB) can be selected from defaults. The memory_limit can be increased to 1,024 MB. If the default values are not sufficient, other settings can be selected from the drop-down list. Alternatively, the values can also be changed directly in the input field.
Custom settings for php.ini can be made via a .user.ini file in the start directory of the domain or PHP script. Changes to the file take up to 5 minutes to take effect.
Working with MySQL/MariaDB databases
Cloud hosting
The following parameters are required to access the database:
- the database user
- the database name
- the database server (host)
- the server port (3306)
- the password for the database
The database user and the database name can be different for cloud hosting.
We offer three different database servers in parallel. MariaDB 10.11 (corresponds to MySQL 8.0), MariaDB 10.3 (corresponds to MySQL 5.7) and MySQL 5.6. This means that the right database version can be selected for every software application. Depending on the TYPO3 version, different database versions are required.
The MySQL or MariaDB server runs on the same server as the web server (Apache), so the data does not have to be transferred between the servers via the network. This results in higher performance and shorter website loading times.
The different database versions are addressed by specifying the host:
MariaDB 10.11: db.mariadb1011
MariaDB 10.3: db.mariadb103
MySQL 5.6: db.mysql56
The size of the database is limited by the size of the hosting package. However, care should be taken to ensure that databases do not become too large, as otherwise the performance of the website will suffer and a backup/restore may take longer. Furthermore, a backup on the web space can cause it to fill up and thus impair the function of the website.
Direct access to the databases from outside is not possible for security reasons. If required, a connection via an SSH tunnel is possible.
Classic Hosting
The following parameters are required to access the database:
- the database user
- the database name
- the database server (host)
- the server port (3306)
- the password for the database
The database user and the database name are identical for Classic Hosting and have the format db123456_789
Database server
The MySQL server runs on the same server as the web server (Apache), so the data does not have to be transferred between the servers via the network.
Database server (host) for MySQL 5.7: mysql
Database server (host) for MariaDB 10.4: localhost
Database versions
We currently provide MySQL 5.6 and MariaDB 10.4. The desired version can be selected when creating a new database. A conversion from MySQL to MariaDB is possible by exporting and then importing the database.
The size of the database is not limited by the size of the hosting package. However, care should be taken to ensure that databases do not become too large, as otherwise the performance of the website will suffer and a backup/restore can take a long time. Furthermore, a backup on the web space can cause it to fill up and thus impair the function of the website.
Direct access to the databases from external computers is not possible for security reasons. If required, a connection via an SSH tunnel and socket is possible.
Export and import of databases
In principle, you can also export/import databases via PHPMyAdmin, but especially with larger databases you will quickly reach the limits (PHP script runtime or memory limit).
Log in to the shell with your SSH user. Under Windows, you can use the free Putty or Mobaxterm program. Under MacOS/Linux, this can be done directly on the shell (via the terminal program). You can find your SSH access data in your customer menu [Configuration ' SSH access (shell)].
Here we have Video instructions for working with a shell access.
Cloud hosting
The safest way to export a database is directly on the shell using the mysqldump command.
You can export a MySQL database 5.6 with the command
mysqldump --opt -h db.mysql56 -u db_user -p db_name > filename.sql
Export a MariaDB database 10.3 with the command
mysqldump --opt -h db.mariadb103 -u db_user -p db_name > filename.sql
Export a MariaDB database 10.11 with the command
mysqldump --opt -h db.mariadb1011 -u db_user -p db_name > filename.sql
The -h parameter defines the database host for MySQL or MariaDB.
In this command, replace db_user and db_name with the corresponding names of your database. After pressing the Enter key, the database password will be requested. All this data can be found in your customer menu, the password for the database can also be found in the configuration of your website.
Classic Hosting
The safest way to export a database is directly from the shell using the mysqldump command.
You can export the MySQL 5.7 database with the command
mysqldump --opt --no-tablespaces -h mysql -u db12345_678 -p db12345_678 > filename.sql
You can export the MariaDB 10.4 database with the command
mysqldump --opt -h localhost -u db12345_678 -p db12345_678 > filename.sql
You can export the MariaDB 10.6 database with the command
mysqldump --opt -h mariadb106 -u db12345_678 -p db12345_678 > filename.sql
The -h parameter defines the database host (mysql or localhost).
Replace db12345_678 with the name of your database in this command. After pressing the Enter key, the database password will be requested. All this data can be found in your customer menu, the password for the database can also be found in the configuration of your website.
Import of databases
Cloud hosting
The safest way to import a database is directly on the shell using the mysql command.
A database file can be imported into a MySQL database with the following command:
mysql -h hostname -u db_user -p db_name < filename.sql
The -h parameter defines the database host: db.mariadb1011 (for Maria DB 10.11), db.mariadb103 (for MariaDB 10.3), db.mysql56 (for MySQL 5.6)
The file "filename.sql", which was previously created using mysqldump, is used as the "input source" in this example.
In this command, replace hostname, db_user and db_name with the corresponding data from your database. After pressing the Enter key, the database password will be requested. All this data can be found in your customer menu, the password for the database can also be found in the configuration file of your website.
Classic Hosting
The safest way to import a database is directly on the shell using the mysql command.
A database is created in MySQL 5.7 with the command
mysql -h mysql -u db12345_678 -p db12345_678 < filename.sql
A database is created in MariaDB 10.4 with the command
mysql -h localhost -u db12345_678 -p db12345_678 < filename.sql
The -h parameter defines the database host (mysql or loclhost).
In this example, the file "filename.sql", which was previously created using mysqldump, is used as the "input source".
Replace db12345_678 with the name of your database in this command. After pressing the Enter key, the database password will be requested. All this data can be found in your customer menu, the password for the database can also be found in the configuration of your website.
External database access
Direct access to the database from outside is not possible for security reasons. However, it is possible to access the database from another computer via an SSH tunnel.
In the following examples, we use a domain name as the host name. If you have problems establishing a connection, use the IP address of the server.
Establish SSH tunnel with PuTTY
To set up an SSH tunnel, please follow the steps below:
1. set up a normal SSH connection (with PuTTY)(supplementary video instructions)
2. set up the SSH tunnel
Now go to "Tunnels" under Category. Enter the number "3306" under "Source Port" and "db.mariadb103:3306" under "Destination" (adjust the name of the host depending on the database used, see above). Confirm the whole thing by clicking on "Add". Check two boxes next to "Port forwarding".
3. save settings
Now go back to the "Session" category and enter a name for your session under the text "Saved Sessions". By clicking on Save, you have saved the settings for the next connection and can restore them by selecting the previously created name and clicking on "Load".
Direct access to a database with "MySQL Workbench"
It is also possible to access the databases directly with external programs via SSH tunnel. Possible programs are, for example, "MySQL Workbench" (Windows, MacOS, Linux) or "Sequel Pro" (MacOS).
For the following example, we use the Windows version of "MySQL Workbench".
2. enter any name under "Connection Name".
For "Connection Method", select "Standard TCP/IP over SSH".
You can use the domain name as the "SSH host name", alternatively use the IP address of the server.
You can find the "SSH Username" in your customer menu in the "SSH Access (Shell)" area. If you no longer know the password, you will need to enter a new one there.
Click on "Store in Vault" under "SSH Password" and then enter the SSH password.
The "MariaDB Hostname" is bd.mariadb103, the "MariaDB Server Port" is 3306.
For the username, enter the database user name that you can find in your customer menu.
Enter the password for the database by clicking on "Store in Vault".
If you no longer know the database password, you may be able to find it in the LocalConfiguration.php of the TYPO3 installation (or a configuration file of another system if you are not working with TYPO3).
If you do not know the database password, you would have to assign a new one in your customer menu and then adjust it in the configuration file.
To check whether the connection can be established, you can click on "Test Connection". If everything is OK, then click on "OK".
2. enter any name under "Connection Name".
For "Connection Method", select "Standard TCP/IP over SSH".
You can use the domain name as the "SSH host name", alternatively use the IP address of the server.
You can find the "SSH Username" in your customer menu in the "SSH Access (Shell)" area. If you no longer know the password, you will need to assign a new one there.
Click on "Store in Vault" under "SSH Password" and then enter the SSH password.
The "MySQL Hostname" is 127.0.0.1, the "MySQL Server Port" is 3306.
For the username, enter the database user name that you can find in your customer menu.
Enter the password for the database by clicking on "Store in Vault".
If you no longer know the database password, you may be able to find it in the LocalConfiguration.php of the TYPO3 installation (or a configuration file of another system if you are not working with TYPO3).
If you do not know the database password, you would have to assign a new one in your customer menu and then adjust it in the configuration file.
After setting up the SSH tunnel, a socket connection to the database must be established in the terminal with the following command. The following command is used for this:
For MySQL 5.7:
ssh -N -L 3306:/var/lib/mysql5/mysql5.sock [ssh-user@domain.tld]
For MariaDB 10.4:
ssh -N -L 5001:/var/lib/mysql/mysql.sock [ssh-user@domain.tld]
The specifications ssh-user and domain.tld must be set to the individual values.
To check whether the connection can be established, you can click on "Test Connection". If everything is OK, then click on "OK".
SSL certificates
Cloud hosting
Access to the websites is only possible via an SSL-encrypted connection. Calls with http:// are automatically redirected to https://.
Free Let's Encrypt certificates can be installed for each domain or subdomain. These have a term of 3 months and are automatically renewed 1 month before expiry.
When setting up the certificates, you can specify whether e-mail traffic or webmail should be protected with the certificate.
Wildcard certificates can also be installed with Let's Encrypt, but they are not renewed automatically.
If required, extended certificates (e.g. Extended Validation) can also be ordered (subject to a charge). You can also upload and install your own SSL certificates via the customer menu.
Classic Hosting
In principle, yes. There are several options available for this:
- Access via meinedomain.de
However, a warning is displayed in the browser that the SSL certificate is not valid. However, the transfer is encrypted. An exception must be added in the browser for this. - Access via an SSL proxy in the form sslsites.de/meinedomain.de
No certificate warning is displayed here, the transfer is encrypted. - Setting up an SSL certificate for the domain. This costs 36 euros/year (incl. VAT). The SSL certificate is issued for a specific domain or subdomain within the hosting package. There is no automatic renewal; an automatic reminder is sent by e-mail four and two weeks before the certificate expires, which can then be renewed in the customer menu or using the form [Order ' SSL certificates ' Gears ' Renew].
Can I access the web space with the IP address?
No, this is not possible. As several customers share a server, the Apache web server would not be able to decide which website should be delivered based on the IP address alone. Even specifying the IP address in conjunction with a directory does not lead to the desired result. The domain name must always be entered in the address line of the browser.
However, if you are moving a website to us, for example, and would like to test it before it goes live, you can order free development domains. These are subdomains with the ending *.jweiland-hosting.de (Cloud Hosting) or *.webseiten.cc (Classic Hosting). These can be configured and used as regular domains.
Caching in Classic Hosting
There are two caching systems in Classic Hosting, which can be deactivated as follows:
1. an Nginx cache is active by default. In case of problems, the Nginx cache can be deactivated with the following entry in the .htaccess file:
Header always set Cache-Control: s-maxage=0
2. the PHP Opcache is active by default. In case of problems, this can be deactivated with the following entry in the .user.ini file in the start directory of the domain:
opcache.enable=0;
Can symlinks be set to directories and files?
Yes, symlinks can be set up for both directories and files.
The syntax on the shell is
ln -s [target file or directory] [alternative name]
If a symbolic link is deleted on the shell, only the reference to the target directory or file is deleted, not the directory or file itself.
Caution when accessing via FTP or SFTP: the target directory or file is deleted when a symlink is deleted!
Set TYPO3_CONTEXT (Application Context) in Classic Hosting
Due to security regulations, the TYPO3 Application Context in Classic Hosting cannot be set via .htaccess file. You can set the application context per domain using the following method.
1. log in to your hosting package via SSH
2. create and edit a PHP file in your hosting package with the name typo3context.php, for example. In the example the editor 'nano' is used, you can of course also use vim or mcedit.
touch typo3context.php
nano typo3context.php3. add the following lines to the file and save them:
<?php
putenv('TYPO3_CONTEXT=Development');4. go to your customer menu -> Domain administration. Click on the cogwheel to the right of the domain name and then on the menu item "Open".
5. in the window that then opens, click on Settings -> PHP.INI Editor
6. in the "General" tab, set "Use global PHP.INI settings" to "No (domain-specific)"
7. then determine the absolute path to the typo3context.php file on the shell with the command 'pwd':
pwd
The output then looks like this:
/www/380407_70794/rp-hosting/xxxxxxx/xxxxxxx
(instead of xxx... you will see digits)
8. in the "Frequently used options", enter the absolute path to the PHP file in the "auto_prepend_file" field, in this example
/www/380407_70794/rp-hosting/xxxxxxx/xxxxxxx/typo3context.phpUse the path on the server that you see when executing the pwd command under point 7!
Then click on the "Apply" button and then on "Save".
Reload the TYPO3 backend, then you should see in the "Application information" in the TYPO3 backend that the website is now running in the development context.
Is there an automatic update of TYPO3?
New TYPO3 major versions (10.x, 11.x, 12.x) are automatically provided on the hosting packages.
The TYPO3 minor updates (e.g. 11.5.4 to 11.5.5) are usually carried out automatically for existing projects. The following rules apply:
- We inform our customers by e-mail before we carry out an update. After the update, the version number should be checked in the backend. The website should also be checked for proper functioning.
- Security updates are usually carried out within a few hours
- Regular updates (bug fixes) are carried out a few days after publication. During this time, we check whether there are any new errors and, if necessary, postpone the update to the next version
- Updates of TYPO3 minor versions are only carried out if the TYPO3 source code installed by us is located in a subdirectory of typo3cms
- If the automatic update of the TYPO3 version is not to be carried out by us, an empty file with the name no-patch can be created in the typo3cms directory.
- Updates are not carried out by us if it is a Composer installation of TYPO3. In this case, the customer or agency should initiate the update with 'composer udpate'