Migration issues

[BodisHS]

Hello there,

I'm tring to migrate my DA from CentOS 7 to CentOS 8
Right now everything is running on the CentOS 7 server.
After migrating i'm getting SSL errors

Current IP config:
CentOS 7 - xxx.xxx.xxx.152
CentOS 8 - xxx.xxx.xxx.199

Since i'm not managing all the domains, i need to re-use the xxx.xxx.xxx.152 IP so the xxx.xxx.xxx.199 is temporary (with a trial license)

So i did the following:

1. Restore the domains/website with "Admin Backups/Transfers" to the CentOS 8 machine.
2. Succesfully checked if all website are working (edited windows hostfile to xxx.xxx.xxx.199, removed after tests)
3. Turned off the old (CentOS 7) machine.
4. Updated the IP of the (CentOS 8) machine to xxx.xxx.xxx.152 (edited ifcfg-ensxxx file)
5. Rebooted the (CentOS 8) machine
6. Updated the license
   1. cd /usr/local/directadmin/scripts
   2. ./getLicense.sh xxxx xxxxx
7. Rebooted the (CentOS 8) machine
8. Succesfully check if DirectAdmin is starting
9. Swapped the IP
   1. cd /usr/local/directadmin/scripts
   2. ./ipswap.sh xxx.xxx.xxx.199 xxx.xxx.xxx.152
10. Request hostname certificate and set it correctly
    1. cd /usr/local/directadmin/scripts
    2. ./letsencrypt.sh request_single web01.domain.com 4096
    3. cd /usr/local/directadmin
    4. ./directadmin set ssl 1
    5. ./directadmin set carootcert /usr/local/directadmin/conf/carootcert.pem
    6. ./directadmin set ssl_redirect_host web01.domain.com
    7. service directadmin restart
11. Rebooted the (CentOS 8) machine

Now the problem starts.

Once I browse to the websites, every one of them gives me a certificate error.
It fetches/uses the web01.domain.com certificate when i browse to them.
Weirdest part is, for some reason ssllabs.com show me the correct certificate of the websites (but browsing to it shows me the web01.hostname.com)

Any idea what could be going on? I really want/need to migrate to CentOS 8

What i tried after step 11:

1. Go to Reseller level and re-request a Let's Encrypt certificate for every website (someone suggested this, just in case)
2. Saved the "private_html setup" just to try

Kind regards,
Justin

 

[zEitEr]

Hello Justin,

Did you clean hosts file on your windows box? You might connect to a wrong IP.

 

[BodisHS]

Hello Justin,

Did you clean hosts file on your windows box? You might connect to a wrong IP.

Hi Alex,
Hostfile is cleaned after testing. So i'm still connecting to xxx.xxx.xxx.152 (which is the correct ip, and dubble checked it)
For some reason it keeps giving me the web01.domain.com certificate but no idea why

 

[BodisHS]

Any idea? It's like it's not binding or something, but cannot find the issue
It seems like changing the IP back to the original one is causing issues