Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: www.studentobservation.com
I ran this command:
/snap/bin/certbot renew --allow-subset-of-names
It produced this output:
Failed to renew certificate www.studentobservation.com with error: Missing command line flag or config entry for this setting:
Please choose an account
Choices: ['dbs14.c.gam-project-kw6-b06-l2z.internal@2018-02-22T20:55:00Z (fcc3)', 'dbs-phptest@2016-08-21T16:27:38Z (c316)', 'dbs9@2016-02-17T16:43:48Z (592c)']
My web server is (include version):
Apache/2.4.41 (Ubuntu)
The operating system my web server runs on is (include version):
Ubuntu 20.04
My hosting provider, if applicable, is:
Google cloud
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
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 2.7.1
Yes this server is production server. We have several server using certbot. There are 8 projects using certbot on this server, but only 2 were up for renewal. And they both had the same error.
A production Let's Encrypt cert is the default. They are used in live servers and the certs will be trusted. You must specifically request Staging certs and these are NOT trusted by browsers. They are helpful when testing to avoid the production system rate limits.
You got 2 Staging certs earlier today so must have done a --dry-run or maybe --test-cert Certbot options
Now, I guess what is happening is that your very old acme-v01 account is now being shown as a viable option. That version was superceded by acme-v02 a long time ago. Perhaps a recent Certbot change is no longer ignoring the v01 accounts.
You could try backing up and removing that acme-v01 account folder. Before doing that you could even match the account number in the renewal config file(s) in /etc/letsencrypt/renewal to make sure it is not referenced.
I wasn't involved with Let's Encrypt / Certbot back then so this is very much a guess. Your current cert has plenty of life left so you could wait to see what other experts have to say about this.
Failed to renew certificate www.studentobservation.com with error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
How would you like to authenticate with the ACME CA?
1: Apache Web Server plugin (apache)
2: Runs an HTTP server locally which serves the necessary validation files under
the /.well-known/acme-challenge/ request path. Suitable if there is no HTTP
server already running. HTTP challenge only (wildcards not supported).
(standalone)
3: Saves the necessary validation files to a .well-known/acme-challenge/
directory within the nominated webroot path. A seperate HTTP server must be
running and serving files from the webroot path. HTTP challenge only (wildcards
not supported). (webroot)
Select the appropriate number [1-3] then [enter] (press 'c' to cancel):
What version of Certbot ? Because I get a different response using a current version.
certbot --version
You explicitly state --webroot authentication so it should not be asking you what kind of authentication to do.
If I do it I get below. It should fail of course because I am not on your server. And, I had to change the webroot path because yours does not exist on my machine. But, the rest is the same
sudo certbot certonly --dry-run --cert-name www.studentobservation.com --webroot -w /var/www/html -d www.studentobservation.com -d studentobservation.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Simulating a certificate request for www.studentobservation.com and studentobservation.com
Certbot failed to authenticate some domains (authenticator: webroot).
The Certificate Authority reported these problems:
