My domain is: www.ericsbinaryworld.com
I ran this command: certbot --apache
It produced this output: (the correct output)
My web server is (include version): apache
The operating system my web server runs on is (include version): Centos 7
My hosting provider, if applicable, is:Digital Ocean
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
Things went got FUBARed last night so I blew away the offending httpd.conf and the one created by certbot to get back to a situation where my website was working.
In an attempt to get the best help, here’s how things went.
I had a httpd.conf where I had definted the ServerName and document root in the body of the httpd.conf because it’s the only site on that VM. So certbot didn’t know what to do because I didn’t have virtual hosts.
So I created a virtualhost with the same info. (Perhaps important: I did not remove it from the general config when I created the virtualhost - so there were effectively 2 declarations for www.ericsbinaryworld.com)
Now certbot would install.
But I went to the “is your cert working correctly” page and it reported everything was good.
But when I tried t load the site, I got the error that it was a self-signed cert.
Couldn’t figure out how to get things fixed so I blew everything away. I noticed that there is an SSL.conf either in /conf/modules.d or conf.d/ . That one points to the self-signed cert.
So, question time:
- When I create the virtual host do I need to get rid of the info from further up the httpd config?
- Should my virtualhost be for www.ericsbinaryworld.com or ericsbinaryworld.com? When I tried to setup ServerAlias to make sure both circumstances were covered, I got an error on the cert-check site that the name didn’t match.
- Do I need to do anything to SSL.conf? or once I fix whatever I did wrong (if anything) with questions 1 and 2 does the httpd-someting.conf that certbot adds take care of things?