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.4.7 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu 14.04
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): No
Certbot tries to place a challenge file at /.well-known/acme-challenge/ in your domain. Can you figure out where the document root for this domain (turistavip.hiptraveler.com) actually is in the file system?
Thank you for your reply. www.hiptraveler.com and turistavip.hiptraveler.com both point to same server and IP. And /.well-known/acme-challenge/ was created in /var/lib/tomcat7/webapps/ROOT/ folder. but then new code deployment removed that folder.
https still works for www even though there’s no /.well-known/acme-challenge/ in ROOT now. But it won’t work for turistavip.
My guess is that the port 443 is already enabled for https and so for some reason acme challenge is not able to reach and create this folder for turistavip on http.
This did work but it ended up modifying - “SSLCertificateFile /etc/letsencrypt/live/www.hiptraveler.com/cert.pem” to “SSLCertificateFile /etc/letsencrypt/live/turistavip.hiptraveler.com/cert.pem” in 000-default-le-ssl.conf which caused errors for www.hiptraveler.com when accessing on https.
Can I create another 000-default-le-ssl.conf with a different name for turistavip.hiptraveler.com with “SSLCertificateFile /etc/letsencrypt/live/turistavip.hiptraveler.com/cert.pem” values?
Do you have a separate VirtualHost in Apache for turistavip.hiptraveler.com? Or do both that and www.hiptraveler.com share one VirtualHost and Tomcat/the application deals with difference?
Then you just have to create a certificate with both names (hiptravaler.com, turistavip.hiptraveler.com) in it. You can specify the names with -d, I would recomment listing certificates first:
certbot certificates
Then decide (based on your current configuration) where to add the extra domain.