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.
I ran this command: certbot certonly --webroot -m XXXXX@gmail.com -d jirafeau.tbbt.xenbox.fr --agree-tos
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert is due for renewal, auto-renewing...
Renewing an existing certificate for jirafeau.tbbt.xenbox.fr
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many certificates (5) already issued for this exact set
of domains in the last 168 hours: jirafeau.tbbt.xenbox.fr: see Rate Limits - Let's Encrypt
Please see the logfiles in /var/log/letsencrypt for more details.
My web server is (include version): Apache/2.4.48
The operating system my web server runs on is (include version): Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux
My hosting provider, if applicable, is: none
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 1.12.0
That's strange.
Four active certs and two expired certs.
Cross-checking, I see the same IP used in active and expired.
So, there must (now) be something "broken" within your system (or HTTP path thereto).
Let's start unraveling this mystery with the output of: sudo apachectl -t -D DUMP_VHOSTS
The expired cert "gitlab.tbbt.xenbox.fr" is no longer covered within the Apache config.
If it is no longer needed, you can remove it with: certbot delete --cert-name gitlab.tbbt.xenbox.fr
If it is needed, then you would first have to recreate the vhost
The expired cert "jirafeau.tbbt.xenbox.fr" is being served by Apache.
[and I see that is the one included in your original post]
So, let's have a look at the vhost file for it: /etc/apache2/sites-enabled/jirafeau.conf
gitlab.tbbt.xenbox.fr is needed but it is on a docker
for jirafeau I have 2 files : /etc/apache2/sites-enabled/jirafeau.conf : Debian Pastezone /etc/apache2/sites-enabled/jirafeau-ssl.conf : Debian Pastezone
Ok the HTTP block is very clean.
Let's test the access with: echo "test-file-1" > /var/www/Jirafeau/test-file-1
And also test the expected challenge path with: mkdir -p /var/www/Jirafeau/.well-known/acme-challenge/ echo "test-file-2" > /var/www/Jirafeau/.well-known/acme-challenge/test-file-2
We can then try them (from the Internet) via: http://jirafeau.tbbt.xenbox.fr/test-file-1 http://jirafeau.tbbt.xenbox.fr/.well-known/acme-challenge/test-file-2