First server's SSL certificate becomes the hostname SSL certificate

[deepakdhingra]

SYSTEM INFORMATION
OS type and version	Debian Linux 12
Webmin version	2.610
Virtualmin version	7.50.2 GPL
Webserver version	Don’t know

Hello,

I am trying to solve a problem that has suddenly come up. I do not know what has caused it.
I had solved the same problem in a different server earlier but now even with replicating those steps, the problem is not going away.

The problem -

I have a few domains set up on a VPS and the hostname is server.axentra.tech

Out of nowhere, the page axentra.tech stopped loading in the browser because of an SSL issue.

SSL Labs showed me this -

Certificate name mismatch
Try these other domain names (extracted from the certificate(s)):

404 Page

api.affiliate.xircls.com
*.crm.xircls.com
*.api.affiliate.xircls.com

These are 4 other servers on my VPS.

Till 2 hours ago, it was picking up the first server in the list. I deleted that server and then it picked up the next one on the list. I deleted that and now it is picking up these 4.

I wanted to bring it to the admin’s notice and therefore, created this topic. I am sure many others must have faced this problem but I could not find any other thread with the exact same issue.

I tried to resolve this by reading other threads/posts. I did what I could do including deleting entries in /etc/webmin/miniserv.conf and what @Ilia has said here about deleting certain entries [quote=“Ilia, post:14, topic:130303”]
keyfile= key
[/quote]

Miniserv and removing old or incorrect SSL certs

Don’t use this feature with Virtualmin. We’ve updated the Webmin code to stop Certbot from renewing Virtualmin-managed domains automatically, even if certbot.timer is unmasked and re-enabled. Head back to that page and disable it… If your hostname can be resolved now, all you need to do is enable the “Setup Let’s Encrypt SSL certificate for hostname” option on the “System Settings ⇾ Virtualmin Configuration: SSL settings” page, and re-run configuration check — it will be automatically prompt…

And Dovecot stopped working because of this and does not restart.

Nothing has worked so far. Does anyone know what to do?

Thank you.

Deepak Dhingra

[deepakdhingra]

I solved this with the help of the AI at Hostinger,

All I had to do was this -

<VirtualHost *:443 IP4:443 [IP6]:443>

In the file - /etc/apache2/sites-available/hostname.conf

Please close this topic. Hope it helps others.

[Joe]

Yes, this is a “the wrong site shows up” problem, and not actually the first server’s cert becoming the hostname cert. (i.e. a VirtualHost misconfiguration due to mixing and matching * and IP-based VirtualHosts…Apache always prefers an IP match and will not consider names if there is an IP match.)

Troubleshooting Websites