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: glidos.net
I ran this command: /usr/bin/certbot renew
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Cert is due for renewal, auto-renewing…
Non-interactive renewal: random delay of 82 seconds
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for imap.glidos.net
http-01 challenge for intranet.glidos.net
http-01 challenge for smtp.glidos.net
Using the webroot path /srv/www/htdocs for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Running deploy-hook command: /etc/letsencrypt/renewal-hooks/deploy/restart-all
Error output from deploy-hook command restart-all:
AH00558: httpd-prefork: Could not reliably determine the server’s fully qualified domain name, using 10.0.0.5. Set the ‘ServerName’ directive globally to suppress this message
new certificate deployed without reload, fullchain is
Congratulations, all renewals succeeded. The following certs have been renewed:
My web server is (include version): Apache 2.4.33
The operating system my web server runs on is (include version): Opensuse Leap 15.1
My hosting provider, if applicable, is: N/A
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. Using the command line.
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): Using a package called python2-certbot. Version 1.0.0
I thought I’d successfully reconfigured to use ACMEv2, but I’ve just received an automated notice that I recently renewed using ACMEv1.
Files /etc/letsencrypt/cli.ini and /etc/letsencrypt/renew/intranent.glidos.net.conf both contain the line
server = https://acme-v02.api.letsencrypt.org/directory
On the other hand. /etc/letsencrypt/accounts/acme-v02.api.letsencrypt.org/directory is a soft link to /etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory, and the regr.json below that references uri’s beginning https://acme-v01.api
I’m confused. I’m not sure what is configuration and what is automatically generated, and hence what I’m allowed to edit. Possibly some of this is config from an old version and is no longer used.