Hello and good afternoon. How does this handle migrating user accounts from one OS (openSUSE) to another OS (Ubuntu or Debian) via the /etc/passwd file? The target system might have data already in it.
The migration tool uses the ISPConfig API to import websites etc. into the enw ISPConfig system. Shell users are not copied directly. So it is no problem when the target server has already some websites, mail accounts etc. as you can use the migration tool to merge servers as well.
So how are the users transfered to the new system? Manually? Through ISP CPanel Sync? This has been the sole issue I have stayed with opensuse over moving to ubuntu or debian.
The migration tool, which gets started on the old server, connects to the ISPConfig remote API of the new server and imports the website, mail accounts etc. into the new ispconfig system. ISPConfig then takes care to configure everything on the new server like adding users, writing config file and so on.
So it's completely automated? From Start to finish? I am definitely interested if it's automatic. Also, how much is the tool and where is the link? Is the license perpetual?
The migration tool works like this: You upload the software to the source server and start it there. The tool asks you some questions like the IP of the target system etc. and shows you instructions what you have to do on the target like adding a remote user in ISPConfig. The tool will then connect from source server to the ispconfig api on the target system and import clients, websites, ftp and shelll users, email domains etc. During the import, the tool creates a script to copy the databases, website content and email messages. This script needs to be copied by you to the target system and executed there as root user. You can read more about the toolincl. licensing details here: https://www.ispconfig.org/add-ons/ispconfig-migration-tool/ Your migration case is a bit special as OpenSuSE uses /srv/www as directory while the target system uses /var/www. This should work in general, but it might be that the path needs to be adjusted in the created data copy script with a text editor. So before you run the data copy script in your case, please take a short look in the script if the paths are correct or contact our support if you are unsure if the path needs adjusted so we can helpyou with that: https://www.ispconfig.org/get-support/?type=migration
Till, Hello and good morning. The user and group names will probably change. Does the script handle this as well? If so, those permissions will need to be set on the files and directories. Does the script set these new permissions on those user folders? For instance, client101 is on opensuse. It has a uid of 100 on opensuse But on ubuntu, 100 might be taken. Does the script handle these "little" problems and corrects them? This is the main reason I have not switched over. So pardon me for asking so many questions
Hello and good day. I purchased the migration tool. Setup ISPConfig 3 On Ubuntu 17. But the migration tool can not connect to the target api. I am running a multiserver setup. DB Server + Webserver. Would the migration tool have an issue with this? The error I was receiving stated bad username. Now it's stating config file not present. What exactly is it looking for?
Hi. Please look in the conf/ or legacy/conf subfolder and delete the importer.conf.php in there. It seems it is empty and though cannot be read correctly. Multiserver is not an issue. If it states bad username, then the remote user you created under system/remote users seems not to be accessible by the credentials you gave.
There is no importer.conf.php on either system. The log shows the following: 2017-07-10 19:25:44 - [INFO] Migration tool version 1.6.10 started. 2017-07-10 19:25:45 - [INFO] Config file not present. 2017-07-10 19:26:39 - [ERROR] 2017-07-10 19:29:42 - [ERROR] What is the Config file that it is looking for?
That config is not the problem. The more important question is why it gives you two [ERROR] entries without text. At what point of the migscript does it end exactly? Which is the last input that you can make?
Last input: And I shall connect to 'https://IPADDR:8080/remote/' Is this correct? (y,n) [y]:Y I will now make a test connection to the remote api. Please press return when I may try to connect. Could not connect to api. Please check if the data you provided is correct. That's it.
So if you have made sure that you created the correct remote user with all privileges checked, it might be that your source php does not like the SSL connection. Please disable SSL temporarily on the target ISPConfig (comment out all SSL lines in the ispconfig.vhost and restart apache) then try again.
I did this a couple days ago and it did not work. I changed SSLEngine from On to Off in the ispconfig.vhost and the default-vhost-ssl.conf (can't remember the exact name.).
May you please post a screenshot of the created remote user (the remote user settings)? And you are able to connect from source server to the remote api on the target server with e.g. wget? wget http://IPADDR:8080/remote/ without getting a timeout? And the remote api URL that you used was http:// after you disabled ssl, just to be sure
isp:~/migration/legacy # wget https://IPADDR:8080/remote/ --2017-07-12 13:29:10-- https://IPADDR:8080/remote/ Connecting to IPADDR:8080... connected. ERROR: cannot verify IPADDR's certificate, issued by ‘/C=US/ST=California/L=Bakersfield/O=RDE Enterprises/CN=FQDN/emailAddress=[email protected]’: Self-signed certificate encountered. ERROR: certificate common name FQDN’ doesn't match requested host name ‘IPADDR’. To connect to IPADDR insecurely, use `--no-check-certificate'. Looks like a certificate issue. So I ran the following: isp:~/migration # /root/migration/migrate --no-check-certificate ionCube Check succeeded. Your license could not be verified. Please make sure the server can access our license server and your license.key file is in place. The license file was working the other day. I dont know what has changed. Screenshots SS 1 - https://drive.google.com/open?id=0By89nxg-2eq-aVBEY1J3SjJTQ3c SS 2 - https://drive.google.com/open?id=0By89nxg-2eq-Si1lNU1vRkxKeFU SS 3 - https://drive.google.com/open?id=0By89nxg-2eq-X3dGRlU0alVtdzA
Is your license server up? I deleted the license.key file, reran migrate, reentered the license and the same error comes up. When I first ran the tool, after purchase, it worked. Nothing has changed. Update: A Server reboot has resolved the license issue. Not sure why.
