I have migrated using the migration toolkit my multiserver setup from ubuntu 16 to ubuntu 18. All data seems to be synced with both setups but my websites (conf,vhosts etc) are not migrated to apache2 therefore nothing really works. Is there a way to make the tool sync these or should I manually transferred the files to the new server setup? Also I am having trouble with the SSL certs. The migrated certs don't work so I decided to create new ones. I have multiple domains with the same ip, how can I have an SSL cert for each one with the same ip? thanks in advance
The data gets migrated automatically and the SSL certs too. Maybe you selected the master server as target for the files when the tool asked for the slave server IP address? Please contact migrationtion tool support by email to "migsupport at ispconfig dot org" and send them the migrate.log file which the tool created while migrating the web server.
The data is migrated fine, I just took a bit long to show up in apache. The reason I am migrating the server to a new installation besides the ubuntu distro upgrade is because I think I messed up the ssl and redirects with my websites. Here is where I get extremely confused. I want to secure all services and ispconfig panel with SSL and also secure alla websites with SSL, all are using the same public ip. I can't really seem to get this right. Also I need all websites to redirect to https nomatter what subdomain is used. Until now i get domain.com to redirect to https://domain.com but when www.domain.com is entered it doesn't redirect to https. I searched everywhere for a clean instruction using the embedded ispconfig functions but I can only find solutions where the configuration will probably get overwritten on next ispconfig update. How do I proceed? please help I am in a loophole!!
Secure other services with LE: https://www.howtoforge.com/tutorial/securing-ispconfig-3-with-a-free-lets-encrypt-ssl-certificate/ LE for websites: enable SSL and LE checkboxes in the website.
This is no problem. Same IP for all websites is the usual way, and no way affects the certificates. I have no guesses what is wrong, on my servers this just works. Try to check if your setup is somehow unusual.
