Perhaps to be totally safe:
certbot renew --cert-name snackconscious.com -i apache -a webroot -w /var/www/snackconscious.com/html/web
It’s the same thing but just more explicit.
Perhaps to be totally safe:
certbot renew --cert-name snackconscious.com -i apache -a webroot -w /var/www/snackconscious.com/html/web
It’s the same thing but just more explicit.
Did it work? OMG
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator webroot, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for snackconscious.com
http-01 challenge for www.snackconscious.com
Using the webroot path /var/www/snackconscious.com/html/web for all unmatched domains.
Waiting for verification...
Cleaning up challenges
new certificate deployed with reload of apache server; fullchain is
/etc/letsencrypt/live/snackconscious.com/fullchain.pem
Congratulations, all renewals succeeded. The following certs have been renewed:
/etc/letsencrypt/live/snackconscious.com/fullchain.pem (success)
Yeah, your site works now: https://www.snackconscious.com/
I notice that https://snackconscious.com points to the wrong location, but that problem already existed before you came to this forum for help. You’ll need to find a developer to help you with that.
OMG AZ thank you soo much I can’t thank you enough. Please can I donate to you?
What do you mean that it’s pointing to the wrong location - I am a noob
Also, do I need to do this every three months or will it renew automatically?
If you wanna donate to anyone, send it to: Donate - Let's Encrypt
Click the second link. You'll see you get a 404 error page.
The problem is that some leftover configuration from your previous staging site is causing that link to point to your (now-defunct) staging website.
I can't fix that for you - you'll need to find a developer to help you repair that issue.
It'll be automatic from now.
Thank you once again AZ. I will definitely donate to /letsencrypt.org/donate, is there any way to donate to you?
I see it now that it’s a 404 error. Does it need to be fixed since people will go to
https://www.snackconscious.com/ vs (https://snackconscious.com/)
So that I can explain to the new dev
Yup.
Basically the dev needs to remove the ServerAlias snackconcious.com
from the old staging virtualhost @ etc/apache2/sites-enabled/snackconscious.com-le-ssl.conf:2
.
Thanks @_az will pass it on to the team. I can’t thank you enough for helping me out. Just make a donation
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.