Multiple SSL certificates not working with LetsEncrypt

[kbmetz]

SYSTEM INFORMATION
OS type and version	Ubuntu 20.04
Virtualmin version	7.7 Pro

I’m running several domains and trying to use a LetsEncrypt SSL cert for each one.

First try, select the LetsEncrypt cert for siteA, it completes successfully. Select LetsEncrypt for siteB and it completes successfully. Go back to siteA and see that it’s using the cert for siteB now (under the SSL settings). This behavior continues for any and all cert requests and domains. Each domain uses the SSL cert that was last requested by LetsEncrypt for all domains

Second, I go and ensure that ‘Share SSL certs’ is turned off in the settings. Try the same steps as above and nothing changes

Third, I put siteA, siteB and siteC all on dedicated IP’s. Run through the same steps of select a LetsEncrypt for siteA and it works. siteB it works, but now siteA is using the cert for siteB

Is there something broken in the Apache config? I saw a posting from 3 years back where the person had to edit the apache configs by hand.

Could this have to do with the fact that I’ve ‘cloned’ domains when I’ve gone to set up a new one? And if so, is there something I have to ‘unlink’ to make this work again? Just checked and this doesn’t appear to be effecting all of the domains, just possibly the ones that I’ve cloned.

Also, I notice that /etc/ssl/virtualmin/xxxxxxxxx does not match the correct domain ID assigned by virtualmin. In both domains it has the same domain ID listed as the SSL directory. So this is what is causing the problem

Thanks

[TiMoscow]

you need to see what is written in the configs of specific domains:
/etc/apache2/sites-available (/etc/apache2/sites-enabled)

<VirtualHost  ip:443>
...
<VirtualHost ip :443>

There are paths to certificate files.

[kbmetz]

That was the source of the issue, those paths were not updating.

I resolved my own issue by going through and removing all of the certs from services and then from each virtual server. After deleting everything I was able to re-add by hand and it appears to have resolved the issue.