Hello Friends, I am going to migrate my Ubuntu 20.04 ISPConfig 3.2.12 to another fresh Ubuntu 24.04 configured by ISPConfig-autoinstaller. My server is simple. A VPS with 8GB RAM. Managed by myself with root access. Running Nginx. 2 different FQDN web sites managed by myself. 2 mail boxes of the above FQDN. Now, my questions are: Which parts of my old server (ISPConfig 3.2.12 related) should I backup and restore later? Should I build the new Ubuntu 24.04 VPS with exactly the same hostname as the old server's, for example, subdomain.mydomain.com? Please guide me through. I am too poor to buy ISPCopy. After all, I have already donated about Euro50 since I began to use it for hobby.
In the forum, you can find various threads about manually migrating / moving ISPConfig to a new server.
Alternatively, backup and restore the whole old server into the new vps and upgrade your OS in there. It is actually not difficult to upgrade OS and all services in a server.
Two ISPConfig3 Experts approve this method. Let me do a complete image backup of my VPS and try. I hope you are not taking me in. I am very scared about this method.
and now after I ran under root: ispconfig_update.sh --force It seems that most of the services are running well except these 2: Roundcube mail: https://mysubdomain.example.com:8081/squirrelmail/ 502 Bad Gateway nginx/1.18.0 (Ubuntu) and https://mysubdomain.example.com:8081/phpmyadmin/: 502 Bad Gateway nginx/1.18.0 (Ubuntu) How do I correct it?
Did you try /webmail instead of /squirrelmail/ ? Or leave the directory altogether, use only :8081/ ? Try mysubdomain.example.com/phpmyadmin, I have always used that for PHPMyAdmin, but I do use Apache so ... Check what happens if you use http:// instead of https://. If this does not help, start with https://forum.howtoforge.com/threads/please-read-before-posting.58408/
I have given up this upgrade method. There are many problems. I am following the safer method: Install a fresh 24.04 OS. Install ISPConfig3 on it. Recreate my 2 sites manually. Restore the sites and emails from the old server's backup. Then, point the new server IP to the server host name in the ISP DNS. Both old and new ISPC server must have the same host name. Even if it does not work, my old ISPC server is still running on the old IP. It seems a very safe method for small server with very few user account.
That is an option though we cannot help if we do not know enough. Basically there might be other tutorial that you might overlooked while using our suggested method like: https://www.howtoforge.com/update-the-ispconfig-perfect-server-from-ubuntu-20-04-to-ubuntu-22-04/
There will be an upgrade tutorial for Ubuntu 22.04 to 24.04 published soon. We finished it, but it needs some more testing. Thanks to @Th0m for writing the guide.
It seems working even though imperfect. It is the log of ISPConfig Cron - Log How do I correct it? Also, the guide suggested us to update phpmyadmin as following. Does it work on my new Ubuntu 22.04 + Nginx server? https://forum.howtoforge.com/thread...automatically-how-to-update-phpmyadmin.88495/
some more imperfection after my hot OS upgrade. ISPConfig Cron - Log Overall, it is a good valid hot OS upgrade. webmail and phpmyadmin work now.
I had to reinstall rspamd, and fix roundcube with this extra line: $config['smtp_host'] = 'localhost:25'; after carelessy just upgrading my vps ....
