I had you remove that so certbot doesn't duplicate it. 
3 Likes
You have only an A record for: jackiesmcs.com
DNS can't find www.jackiesmcs.com: Non-existent domain
3 Likes
Add a CNAME record for www pointing to @
4 Likes
That did the trick!
3 Likes
For www.jackiesmcs.com it did. Thanks!
I am still unable to reach HTTPS though 
3 Likes
@griffin, do you want to prepare the install command line?
Or just use:
certbot --apache
[after we delete the current cert]
? ? ?
3 Likes
One step at a time - cowboy!
3 Likes
I can write it. Go ahead and track down the cert frags. 
3 Likes
@Leavii
Let's get rid of the one-named cert:
certbot delete --cert-name jackiesmcs.com
Then show:
certbot certificates
3 Likes
Sorry. I initially thought you both meant you could reach HTTPS when you said it did the trick 
3 Likes
Once the old cert(s) are toast...
Let's test first:
certbot certonly --apache -d "jackiesmcs.com,www.jackiesmcs.com" --dry-run
3 Likes
LOL that's on page four (trick)
We're still on page one (tricks)
3 Likes
Output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
No certificates found.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
3 Likes
Check the folders too @rg305
We don't want any goblins
3 Likes
Step #1: DNS = CHECKED!
Step #2: Verify current web config
apachectl -S
Step #3: Verify all LE folders& files:
ls -lR /etc/letsencrypt/
3 Likes
I was meaning this:
ls -lRa /etc/letsencrypt/archive
ls -lRa /etc/letsencrypt/live
edit: yours is better
3 Likes