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.
Domain: support.appvision.net
Type: unauthorized
Detail: Incorrect validation certificate for tls-sni-01 challenge.
Requested
8f5445b3c6d80baea32e62aad1933d8f.7d91bc19e853fb64b44cfd7ad2a590df.acme.invalid
from 104.197.131.45:443. Received 2 certificate(s), first
certificate had names “corp.appvision.net”
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
My web server is (include version): Apache 2.2
The operating system my web server runs on is (include version): Centos 6.9
My hosting provider, if applicable, is: SiteGround
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): cpanel
Are you trying to expand your existing cert for corp.appvision.net to also cover support.appvision.net? If so, you should list both domains in the -d option eg ./certbot-auto certonly --cert-name corp.appvision.net -d support.appvision.net,corp.appvision.net
If that doesn’t help, could you please post the output of apachectl -S?
cpanel is just for the Web Hosting. The Apache server is in the Google cloud and all the pages are working. Just trying to get SSL turned on for support.appvision.net
[root@test-devserver1-2 krist]# apachectl -S
[Tue Dec 19 01:29:28 2017] [warn] module deflate_module is already loaded, skipping
[Tue Dec 19 01:29:28 2017] [warn] default VirtualHost overlap on port 443, the first has precedence
VirtualHost configuration:
wildcard NameVirtualHosts and default servers:
*:443 test-devserver1-2.c.third-opus-86816.internal (/etc/httpd/conf.d/ssl.conf:74)
*:443 support.appvision.net (/etc/httpd/conf/httpd.conf:373)
*:80 is a NameVirtualHost
default server corp.appvision.net (/etc/httpd/conf/httpd.conf:359)
port 80 namevhost corp.appvision.net (/etc/httpd/conf/httpd.conf:359)
Syntax OK
Btw, Thanks so much for your help. This has been a frustrating thing with CentOS. We also are in Google Cloud Environment (Compute Engine) and I don’t know if I put that in the earlier thread.
Already have NameVirtualHost *:80 there.
I tried adding in the 443 and it broke the apache config.
Snippet from the httpd.conf
Use name-based virtual hosting.
NameVirtualHost *:80
NameVirtualHost *:443
THIS IS THE VH Config for the site that I’m trying to enable SSL for. Keeps telling me it doesn’t like the name because the cert i have is for corp.appvision.net, but since they both are appvision.net it should work. It worked on CentOS 7 using multiple domains for one cert and was super easy. Maybe because certbot is actually in the yum repos.
It’s not complaining because you have a cert for the other name. Certbot is trying to configure a temporary virtualhost to respond to the tls-sni-01 challenge, but for some reason your existing vhost for the corp subdomain is taking precedence and preventing the validation server from reaching the temporary vhost.
I thought that might be due to the lack of name based virtual hosting on port 443, which is why I suggested adding that line. In what way did it break your config?
Could you please also post the vhost config for the corp subdomain?
This is the error that it throws after putting in the NameVirtualHost :*443 directive. Even after I commented it out.
[root@test-devserver1-2 krist]# service httpd start
Starting httpd: [Tue Dec 19 16:35:52 2017] [warn] module deflate_module is already loaded, skipping
[Tue Dec 19 16:35:52 2017] [warn] default VirtualHost overlap on port 443, the first has precedence
[FAILED]
[root@test-devserver1-2 krist]#
[root@test-devserver1-2 ragediver24]# ./certbot-auto certificates
/opt/eff.org/certbot/venv/lib/python2.6/site-packages/cryptography/init.py:26: DeprecationWarning: Python 2.6 is no longer supported by the Python core team, please upgrade your Python. A future version of cryptography will drop support for Python 2.6
DeprecationWarning
Saving debug log to /var/log/letsencrypt/letsencrypt.log
No certs found.
The certs were done previously through another method, not certbot.
but certbot is downloaded to the vm
Get HTTPS for free!
You can now get free https certificates from the non-profit certificate authority Let’s Encrypt! This is a website that will take you through the manual steps to get your free https certificate so you can make your own website use https! This website is open source and NEVER asks for your private keys. Never trust a website that asks for your private keys!
NOTE: This website is for people who know how to generate certificate signing requests (CSRs)! If you’re not familiar with how to do this, please use the official Let’s Encrypt client that can automatically issue and install https certificates for you. This website is designed for people who know what they are doing and just want to get their free https certificate.
Step 1: Account Info
Let’s Encrypt requires that you register an account email and public key before issuing a certificate. The email is so that they can contact you if needed, and the public key is so you can securely sign your requests to issue/revoke/renew your certificates. Keep your account private key secret! Anyone who has it can impersonate you when making requests to Let’s Encrypt!
I’m assuming the same way. I’m not the one who installed it lol. I believe they followed the process on that site. The certs are contained in /etc/pki/tls/private
What I’m not understanding is where the corp.appvision.net certificate is coming from. You said it’s in /etc/pki/tls/private but I don’t see any reference to that directory in the configuration you posted. Maybe it’s in /etc/httpd/conf.d/ssl.conf? Are you sure it’s on that server? Is Apache listening on port 443? lsof -i :443 | grep LISTEN
Where did you put the NameVirtualHost *:443 when you tried it?