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. https://crt.sh/?q=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: casazza.net
I ran this command: certbot
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please choose an account
1: www.casazza.net@2019-06-25T00:32:44Z (3997)
2: dev.casazza.net@2022-01-29T22:12:42Z (cf1d)
Select the appropriate number [1-2] then [enter] (press 'c' to cancel):
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: 1&1
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): 1.23.0
I've read some other threads. Romoing the "staging" directory did not fix this. This is my accounts folder listing
/etc/letsencrypt/accounts# l -R
.:
total 16
drwx------ 4 root root 4096 Feb 19 11:24 .
drwxr-xr-x 9 root root 4096 Feb 19 11:25 ..
drwx------ 3 root root 4096 Jun 28 2019 acme-staging-v02.api.letsencrypt.org
drwx------ 3 root root 4096 Jun 24 2019 acme-v02.api.letsencrypt.org
./acme-staging-v02.api.letsencrypt.org:
total 12
drwx------ 3 root root 4096 Jun 28 2019 .
drwx------ 4 root root 4096 Feb 19 11:24 ..
drwx------ 3 root root 4096 Jun 28 2019 directory
./acme-staging-v02.api.letsencrypt.org/directory:
total 12
drwx------ 3 root root 4096 Jun 28 2019 .
drwx------ 3 root root 4096 Jun 28 2019 ..
drwx------ 2 root root 4096 Jun 28 2019 4b936816d6e8de384d61265f06a1c9f9
./acme-staging-v02.api.letsencrypt.org/directory/4b936816d6e8de384d61265f06a1c9f9:
total 20
drwx------ 2 root root 4096 Jun 28 2019 .
drwx------ 3 root root 4096 Jun 28 2019 ..
-rw-r--r-- 1 root root 75 Jun 28 2019 meta.json
-r-------- 1 root root 1630 Jun 28 2019 private_key.json
-rw-r--r-- 1 root root 85 Jun 28 2019 regr.json
./acme-v02.api.letsencrypt.org:
total 12
drwx------ 3 root root 4096 Jun 24 2019 .
drwx------ 4 root root 4096 Feb 19 11:24 ..
drwx------ 4 root root 4096 Jun 24 2019 directory
./acme-v02.api.letsencrypt.org/directory:
total 16
drwx------ 4 root root 4096 Jun 24 2019 .
drwx------ 3 root root 4096 Jun 24 2019 ..
drwx------ 2 root root 4096 Jun 24 2019 3997ef8802072e9f69bf896f570d2ade
drwx------ 2 root root 4096 Jan 29 17:12 cf1da9ee15ebbe41fc911c681eeb4dc3
./acme-v02.api.letsencrypt.org/directory/3997ef8802072e9f69bf896f570d2ade:
total 20
drwx------ 2 root root 4096 Jun 24 2019 .
drwx------ 4 root root 4096 Jun 24 2019 ..
-rw-r--r-- 1 root root 75 Jun 24 2019 meta.json
-r-------- 1 root root 1632 Jun 24 2019 private_key.json
-rw-r--r-- 1 root root 78 Jun 24 2019 regr.json
./acme-v02.api.letsencrypt.org/directory/cf1da9ee15ebbe41fc911c681eeb4dc3:
total 20
drwx------ 2 root root 4096 Jan 29 17:12 .
drwx------ 4 root root 4096 Jun 24 2019 ..
-rw-r--r-- 1 root root 119 Jan 29 17:13 meta.json
-r-------- 1 root root 1632 Jan 29 17:12 private_key.json
-rw-r--r-- 1 root root 79 Jan 29 17:12 regr.json