Found the following certs:
Certificate Name: all-sites
Domains: daniellewisjj.com daniellewisjj.uk dlmdesigns.co.uk inmotionbucks.uk thegrapplingaddict.com
Expiry Date: 2021-11-15 07:59:28+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/all-sites/fullchain.pem
Private Key Path: /etc/letsencrypt/live/all-sites/privkey.pem
Certificate Name: dlmdesigns.co.uk
Domains: dlmdesigns.co.uk daniellewisjj.uk inmotionbucks.uk thegrapplingaddict.com
Expiry Date: 2021-11-13 18:51:07+00:00 (VALID: 88 days)
Certificate Path: /etc/letsencrypt/live/dlmdesigns.co.uk/fullchain.pem
Private Key Path: /etc/letsencrypt/live/dlmdesigns.co.uk/privkey.pem
OK how do you edit files?
nano file.name
-
vi file.name
OR - you copy the file out of the server
edit it on your PC
copy it back to the server
You mean the wordpress-le-ssl.conf
How would you edit any file on the server?
I normally download them, and edit it in notepad
OK that will work.
Change these two lines:
SSLCertificateFile /etc/letsencrypt/live/dlmdesigns.co.uk/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/dlmdesigns.co.uk/privkey.pem
to:
SSLCertificateFile /etc/letsencrypt/live/all-sites/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/all-sites/privkey.pem
and then restart Apache
For good measure and housekeeping: YES.
Will it break if you don't? NO; There is only one TLS vhost (so all connections will go there).
Apache restarted and BOOM all secure!!
And for good measure, you might want to update the other files' redirection section.
FROM:
RewriteEngine on
RewriteCond %{SERVER_NAME} =daniellewisjj.uk [OR]
RewriteCond %{SERVER_NAME} =85.159.210.215 [OR]
RewriteCond %{SERVER_NAME} =thegrapplingaddict.com [OR]
RewriteCond %{SERVER_NAME} =dlmdesigns.co.uk [OR]
RewriteCond %{SERVER_NAME} =inmotionbucks.uk
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
TO JUST:
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
Great I will do that shortly. Just heading out for a couple of hours of teaching then I'll get this sorted.
Thank you so much for all your help so far!!! It means a lot of has destressed my brain massively!!
Now we delete the unused cert:
certbot delete --cert-name dlmdesigns.co.uk
Then we recheck it with:
certbot certificates
Glad to have helped
Cheers from Miami
#FreeCuba
I'm assuming I just need to update the WordPress.conf file in the sites enabled?
All done with the additions to the wordpress.conf and deleted the unrequired certificate.
Just out of interest the what is the purpose for the .conf change?
Again a huge thank you for your help with this.
Which .conf change specifically? (we changed two .conf files)
This code section.
In English, that says:
If HTTPS is NOT used on this connection, then redirect it to HTTPS://{whatever URL was requested}
So, it doesn't require you to add lines each time you add a site, it will redirect every name to HTTPS.
This is something to consider when requesting a new cert.
LE will not complain about the cert used when trying to validate a new request but a cert must be used in order to speak via HTTPS.
[if that sounds.. complicated, just reach out to us when you try to get a new cert and it if it fails]
Thank you so much for your help on this. Can I make a donation to either you or to LE to thank you for your time?