I am facing very wiered issue. We have a VPS where we are having many websites with different domain names and sub domain names. Earlier we were not facing any issue with SSL implementation. But now what is happening that we have implementated SSL into one application that is app.clinicview.co.in and SSL is working fine there. On the same VPS we are havind different Virtual Server having name dms.solasticerenewables.com or jobs.9o9.in. We tried installing SSL there by lets Encrypt but it is taking SSL from app.clinicview.co.in. Means using same SSL certificate on all the places. We havn’t copied anything among these project.
Please look into this and let us know what we suppose to do or if we have done something wrong with it.
No, Let’s Encrypt will not do that because that’s not how the service works. However I can confirm that the same certificate (Serial Number: 04da6232e9f47a234a249e4c16899d01eb16) is applied to both dms.solasticerenewables as well as app.clinicview. But jobs.9o9 has Serial Number: 3c17ec7a6a1e72799bae0b043924d5285c357590 proving you are able to generate SSL certificates which are different from the one for app.clinicview.
No, not really.
I am in India too and if you get into a screen-share session with me, I would be happy to take a look around.
jobs.9o9.in is showing old certificate as earlier it was working fine. Now when I tried to renew it or recreate it then it is doing same thing with this domain too. I know letsencrypt doesnt do this but that is why I have raised the issue here. It is happening. Dont know what is wrong with it.
Thanks Joe…but i have checked everything which I knew best of my knowledge. It is not working…Do you have some solution about SSL or how we use duplicate certificate or remove duplicate certificate or remove default SSL certificate option in Virtualmin then please share. As I think…this could be one reason that may be system is using app.clinicview.co.in SSL as default one across the all the VMs.
They gave you one in that link Joe posted. Namely check the error logs, access logs and apache configuration files for the servers that are using the wrong certificate. At the very least you’ll come back with something considerably more detailed than “It is not working”. Getting unpaid support from the virtualmin team is already like drawing blood from a stone, I can’t imagine you’ll get anywhere with this approach. If you can’t or won’t put in the bare minimum you should put out a contract on freelancer.com or fiverr.com
Again, this is some variant of the wrong site shows up. If it’s not the exact configuration problem covered there it is still pretty much certainly some variant of Apache choosing what seems to you to be a wrong VirtualHost, but it is the one that Apache thinks best matches.
It could be an IPv6 misconfiguration (same problem, just a different IP:port combination than above).
As Maelstrom suggested, you also have to look at logs. You always have to look at logs. Logs are the first and last thing to look at when troubleshooting, you’ll almost never have a problem that isn’t showing up somehow in the logs.