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. crt.sh | 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: ordertrack.prime-vendor.com
I ran this command:
**Case: **
**I did install let's encrypt last week in the mentioned server(previously it was Ubuntu server), but due to certain requirement, we had to reset the server to centos version. **
**After successful installation of apache in new centos (7.6) server[note: domain name is same though] **
I proceed through the process of installing ssl.
yum install epel-release
yum install certbot python2-certbot-apache mod_ssl
certbot --apache -d ordertrack.prime-vendor.com
(proceed according to instruction and choose auto https redirect option 2)
It produced this output:
Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you're confident your site works on HTTPS. You can undo this
change by editing your web server's configuration.
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Redirecting vhost in /etc/httpd/sites-enabled/ordertrack.prime-vendor.com.conf to ssl vhost in /etc/httpd/sites-available/ordertrack.prime-vendor.com-le-ssl.conf
Congratulations! You have successfully enabled
https://ordertrack.prime-vendor.com
You should test your configuration at:
https://www.ssllabs.com/ssltest/analyze.html?d=ordertrack.prime-vendor.com
IMPORTANT NOTES:
-
Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/ordertrack.prime-vendor.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/ordertrack.prime-vendor.com/privkey.pem
Your cert will expire on 2019-09-25. To obtain a new or tweaked
version of this certificate in the future, simply run certbot again
with the "certonly" option. To non-interactively renew all of
your certificates, run "certbot renew" -
Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal. -
If you like Certbot, please consider supporting our work by:
Donating to ISRG / Let's Encrypt: Donate - Let's Encrypt
Donating to EFF: Support EFF's Work on Let's Encrypt | Electronic Frontier Foundation
My web server is (include version):
Server version: Apache/2.4.6 (CentOS)
Server built: Apr 24 2019 13:45:48
The operating system my web server runs on is (include version):
CentOS Linux release 7.6.1810 (Core)
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
I'm using puTTy terminal and operating using commands.
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot):
certbot 0.34.2
I would be really thankful if this mismatch issue could be resolved.
NOte:
Using same domainname: ordertrack.prime-vendor.com
Initially, I had to install new cert in Ubuntu system.
Later, due to certain requirement, we had to change the same system to centoos.
When it was in Ubuntu system, I installed certificate for domain and it was working fine.
https://ordertrack.prime-vendor.com
was working.
Later, when system changed to centos,
I repeated same process, and log says,
cert has been installed successfully,
However,the certificate name mismatch SSL report was seen.
and SSL is not installed.
What could be the actual issues here?
It would be helpful if anyone can update me on related issue.
I also looked into the similar error:
**which says: **
Sounds like Apache has another certificate configured elsewhere that is taking precedence.
But I've only installed one cert in the system.
Thank you.
Rajendra