My domain is: https://financieelonafhankelijkworden.nl/
I ran this command: certbot renew and certbot renew --force-renewal
It produced this output:
Processing /etc/letsencrypt/renewal/financieelonafhankelijkworden.nl.conf
Certificate not yet due for renewal
The following certificates are not due for renewal yet:
/etc/letsencrypt/live/financieelonafhankelijkworden.nl/fullchain.pem expires on 2023-02-22 (skipped)
But when forcing renewal:
Domain: penke.nl
Type: unauthorized
Detail: 83.96.253.108: Invalid response from Penke: hoe kan ik jou helpen? "<!doctype html><html lang="nl"><meta charset="utf-8"><meta name="viewp ort" content="width=devic"Domain: www.financieelonafhankelijkworden.nl
Type: unauthorized
Detail: 83.96.253.108: Invalid response from Financieel Onafhankelijk Worden "\n<html class="no-js" lang="nl" prefix="og: http://ogp.me/ns#\">\n\n <meta charset="UTF-8">\n <meta name="view"
Note: there are multiple domains in the cert.
My web server is (include version): Apache/2.4.37
The operating system my web server runs on is (include version): Centos 8 stream
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 1.32.0
The certbot renew command works fine. But when forcing to update the certificate it fails. The weird part is that the command tells me
is not reachable but when entering this in my browser I can access it. Also, the certificate is renewed yesterday so that seems to work.
For domain https://financieelonafhankelijkworden.nl/ it only says that Financieel Onafhankelijk Worden unauthorised without mentioning the ".well-known/acme-challenge/" path.
I don't understand why it did renew the certificate for penke.nl but not for https://financieelonafhankelijkworden.nl/ while both virtual hosts are the same. Does this have to do with the redirect to HTTPS?