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.
My domain is: hoba.ium.edu.mv
I ran this command: sudo certbot renew
It produced this output:
Renewing an existing certificate for hoba.ium.edu.mv
Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: hoba.ium.edu.mv
Type: unauthorized
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: DigitalOcean
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):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
This is the first time I need to renew, but the renewal command returned an 'unauthorized' error.
Does Let's Debug actually check anything at all? As near as I can tell, it just refers everyone to this forum, pretty much regardless of the nature of their problem. (Maybe it checks some very minimal stuff, like whether the domain resolves and port 80 is open? Not much beyond that, that I can see.)
Let's Debug does see the 500 status code too (Let's Debug), but it doesn't complain because it doesn't expect the fictitious challenge file to exist. As long as a web server responds properly as per HTTP spec, the test is considered successful. We could consider warning on server-side errors as those are more unexpected than a 404 though.
