Can't renew Let's Encrypt certificate; verification fails with file not found error

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I have used several times in the past to renew my certificate with no problems but today the Verification phase fails, saying it can’t find the files it needs.

I have checked and the files are there and do not have an extension; permissions are 644

My domain is:,

I ran this command:

It produced this output: Verification results

Some domains have failed verification. Please study the list below and then click “Next” to try requesting new challenges for them. Note: the challenge values will be different.

Domain Error Invalid response from []: “\n\n500 Internal Server Error\n\n

Inter” Invalid response from []: “\n\n500 Internal Server Error\n\n


My web server is (include version):
|Apache Version|2.4.39|

The operating system my web server runs on is (include version): Linux, doesn’t say what flavor or version

My hosting provider, if applicable, is: Godaddy

I can login to a root shell on my machine (yes or no, or I don’t know):I don’t know

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Cpanel |cPanel Version|70.0 (build 51)|

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):not using certbot

Hi @schaer,

Currently all files on your web site produce this 500 error:

including the main page

Your HTTP web site has to be a little bit more functional than this in order to get certificates via this method. Right now, it's not possible for anyone to access any file on your site, so the Let's Encrypt validation process also can't do so.

You might be able to ask GoDaddy support for help, or look at the /var/log/apache2/error_log file on your web file (or a similar file) to learn what the exact problem is.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.