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: jnrothen.ddns.net
I ran this command: letsencrypt renew
It produced this output:
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for jnrothen.ddns.net
Waiting for verification…
Cleaning up challenges
Unable to clean up challenge directory /var/www/nextcloud/.well-known/acme-challenge
Attempting to renew cert from /etc/letsencrypt/renewal/jnrothen.ddns.net.conf produced an unexpected error: Failed authorization procedure. jnrothen.ddns.net (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://jnrothen.ddns.net/.well-known/acme-challenge/0dehDVVGNnxXApc9WmsS2twIGUAz3nYXBTNlAFTWL70: "
All renewal attempts failed. The following certs could not be renewed:
1 renew failure(s), 0 parse failure(s)
The following errors were reported by the server:
Domain: jnrothen.ddns.netDie Seite wurde n"
Detail: Invalid response from
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address.
My web server is (include version): Apache/2.4.25 with Nextcloud/13.0.4
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
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
I checked access.log and error.log. I can’t find any request to the webserver requesting the file. I tried to creat another file in the acme directory, which I’m able to access without any problems. I checked letsencrypt.log and the IP address which is resolved and used is correct.