BUT the certbot renew command produces this output
It produced this output: The following certs are not due for renewal yet:
/etc/letsencrypt/live/samuele.site-0001/fullchain.pem expires on 2021-08-20 (skipped)
No renewals were attempted.
Additionally, the following renewal configurations were invalid:
/etc/letsencrypt/renewal/samuele.site.conf (parsefail)
My web server is (include version): Apache 2
The operating system my web server runs on is (include version): Ubuntu 20
My hosting provider, if applicable, is: rhosting.it
I can login to a root shell on my machine (yes or no, or I don't know): yes
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 0.40.0
So you've got your certificate. And your site is still labeled as insecure. Perhaps a superfluous question, but did you actually install the certificate into your website?
And a follow-up question: do you actually require the use of the wildcard certificate? Because if you don't, things probably would have been much easier than manually fiddle with your DNS entries. For example, simply running certbot --apache would probably suffice, which would take care of authentication and installation of the certificate (unless your Apache is not properly configured).
Uch.. Looking at your site more closely, there is an OLD certificate installed currently. You might have lead with that. Now I thought this was your first attempt to get a certificate in the first place.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Renewal configuration file /etc/letsencrypt/renewal/samuele.site.conf produced an unexpected error: expected /etc/letsencrypt/live/samuele.site/cert.pem to be a symlink. Skipping.
Found the following certs:
Certificate Name: samuele.site-0001
Domains: samuele.site *.samuele.site
Expiry Date: 2021-08-20 13:25:04+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/samuele.site-0001/fullchain.pem
Private Key Path: /etc/letsencrypt/live/samuele.site-0001/privkey.pem
The following renewal configurations were invalid:
/etc/letsencrypt/renewal/samuele.site.conf
It seems you've not used the certbot delete option, but manually deleted the files.. Did you also remove the /archive/ directory? Please post the output of:
Hmm, 16 February, that's of no use unfortunately..
As you've already deleted the /live/ directory and there are only expired certificates left, please delete the files still laying around of that expired certificate:
deleted everything, when i run certbot --apache this happens:
root@vps:/# certbot --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Error while running apache2ctl configtest.
Action 'configtest' failed.
The Apache error log may have more information.
AH00526: Syntax error on line 33 of /etc/apache2/sites-enabled/000-default-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/samuele.site/fullchain.pem' does not exist or is empty
The apache plugin is not working; there may be problems with your existing configuration.
The error was: MisconfigurationError("Error while running apache2ctl configtest.\nAction 'configtest' failed.\nThe Apache error log may have more information.\n\nAH00526: Syntax error on line 33 of /etc/apache2/sites-enabled/000-default-le-ssl.conf:\nSSLCertificateFile: file '/etc/letsencrypt/live/samuele.site/fullchain.pem' does not exist or is empty\n")
Why did you delete everything? That's not the advice I gave.. You've deleted a perfectly fine certificate we could have used as backup. Unless by "deleted everything" you mean just the two commands I gave above. In that case, I didn't say anything
Anyway, the error is to be expected: Apache is still referring to the older certificate of which you've deleted the /live/ directory.
At this stage I would like to urge you NOT to make rash decisions. Please think things through first. Learn the consequences of certain steps first. Always make a backup. Please learn how to manage a server properly.
That said, it seems your previous certificate was managed by the apache certbot plugin to begin with. Before we do anything stupid, please give the output of the following command:
apachectl -S
So we can make sure we're not about to delete something essential in the next step.
root@vps:/# apachectl -S
AH00526: Syntax error on line 33 of /etc/apache2/sites-enabled/000-default-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/samuele.site/fullchain.pem' does not exist or is empty
Action '-S' failed.
The Apache error log may have more information.
sorry, I won't from now, this has been a rough week
Afterwards you should be able to run certbot --apache
Note that the HTTP to HTTPS redirect is still in place, so users won't be able to access your site temporarily.. However, they get an error now for the certificate anyway..
Your site seems to be missing the HTTP to HTTPS redirect. Did certbot ask anything about that? I didn't check before (assumptions......), but it seems it was never there?
That's weird. Only one configuration file should be present. Could you give us the contents of both files 000-default.conf and 000-default-le-ssl.conf?
