Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
sudo certbot --apache
It produced this output:
After going through the steps it stated successful creation of certificate
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):certbot 0.23.0
More info - the output of openssl s_client -showcerts -connect www.sengkanggrand.com:443 reports an incorrect CN of aba.com.sg
I had previously created a working certificate but chose to delete an old certificate no longer relevant using ```
certbot delete --cert-name old.defunctdomain.com
This is when the problems started. Chrome now reports
This site can’t provide a secure connection
www.sengkanggrand.com.sg sent an invalid response.
By the way, apart from other more important problems (you need to set up the port 443 vhost to use HTTPS instead of HTTP), this method won't show the right certificate with virtual hosting because it doesn't send any SNI field in the HTTPS connection. For that, you need to add the OpenSSL option -servername www.sengkanggand.com.sg; that more closely follows the behavior that a web browser would use in connecting to your site.
In your current situation, this wouldn't initially give a different result, but if you have to debug other things in the future related to certificate mismatches, it might give more relevant debugging information.