Hi, I want to migrate my ISPconfig installation to a new server (from aws to hetzner). What is the best way to do that. Is there a how-to I can follow? thanks, Stefan
The easiest way is probably using the Migration Tool: https://www.howtoforge.com/tutorial...-confixx-plesk-to-ispconfig-31-single-server/
Thanks Till, thats exactly what I'm looking for. I have the old server running on apache. Would you recommend switching to nginx on the new one? Does the migration tool support that? I'm also thinking about using rspamd instead of amavis. Whaot is your recommendation? thanks, Stefan
No. It is possible, but most of your sites will probably need custom Nginx directives, so they will stop working after the migration until you created the custom config for each site. Use rspamd. We do not even test Amavis anymore on recent Linux versions, as rspamd is the default for many years now.
unfortunately, this doesn't work out of the box. 1) all DB-User credentials do not work - do I have to set them manually again? 2) PHP Versions are mixed up, original end up in and default PHP is displayed as PHP5.6.
I set up the new server (ubuntu 24.04) according to https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/ then used the migration tool according to https://www.howtoforge.com/tutorial...-confixx-plesk-to-ispconfig-31-single-server/
The MySQL passwords get migrated by the tool, so they should work. But its possible that the new MySQL or MariaDB version does not accept the passwords if it allows only the new MySQL hashing algorithm. I have not had that case yet, but it is possible. In that case, you will have to set the passwords again. Regarding PHP versions, the tool maps them to the choices made during migration. The tool asks which old PHP version shall get mapped to which new PHP version. There seem to be not that many sites, so manually selecting the desired PHP version in the seite(s) now, after migration is probably faster than redoing the migration. Regarding the default PHP version, that's typically the system PHP of the new OS, depending on the settings you made in the new ISPConfig. This setting is not migration related.
is it save to migrate again? Maybe i missed some important option... Most of the Websites run on default PHP version, that is not visible on the Additional PHP Versions Tab. However, the version is displayed wrongly in the Website settings, because the "Default" option is missing. meanwhile I uninstalled PHP5.6 on the new server, so it shows 7.0 now for all sites running the default php version (8.3)
The default option is configured under System > Server config > web, and whether it's shown or not is configured there and also which exact PHP version it is. Additional PHP versions are just additional PHP versions. Unless you have many sites, I won't risk migrating again. In general, you can run the migration agaian but you must take care to cioose that sites get overwritten, otherwise you end up with duplicate sites.
Please set the default PHP handler to php-fpm. Fast-CGI is not used anymore today, one would always use its successor PHP-FPM
yes it is PHP-FPM on the old server and I changed it already on the new one. However, that doesn't change that "Default" option is not selectable.
I fixed the PHP version problem by doing another migration. That fixed the Default issue, the few add'l PHP versions were still mixed up. I changed it manually. The DB-login problem seems to be connected to some special characters only. Didn't work when the password includes characters like / or öaü... So maybe you can fix that in future releases of the migration tool.
I will have a look at it, but I migrated passwords with umlauts in the past successfully. We had no other reports of failed passwords after migrations yet. The Migration Tool copies over the hashed passwords as they are, so it does not even know which chars are used in a password. In my opinion, tthe more likely reason for the issue you had is that the hashes of the old passwords can not be read by the new database system. But I will see if I can reproduce this.
