Renew stopped working, new certs not working too

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: admin.fsczech.cz

I ran this command: sudo certbot certonly --standalone --preferred-challenges http -d admin.fsczech.cz -d www.admin.fsczech.cz

It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for admin.fsczech.cz
http-01 challenge for www.admin.fsczech.cz
Waiting for verification…
Challenge failed for domain admin.fsczech.cz
Challenge failed for domain www.admin.fsczech.cz
http-01 challenge for admin.fsczech.cz
http-01 challenge for www.admin.fsczech.cz
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

My web server is (include version): Apache/2.4.6 (CentOS) (at moment of execution stopped)

The operating system my web server runs on is (include version): CentOS 7

My hosting provider, if applicable, is: local

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): 1.0.0

Hi, I’m quite mad with certbot which stopped working. All experiments ended with Unathorized, Invalide response error, 404. Even standalone type of execution. Using --debug-challenges, I was able to track acme files created only when using --webroot -w /var/www/html/admin.fsczech.cz/public_html, but it concluded in 404 error either :frowning:

1 Like

Your server seems to expose Apache httpd on port 81 (http://89.190.37.90:81/), not port 80 (http://89.190.37.90).

Port 80 seems to be forwarded to some Windows server, as far as I can tell.

If your port forwarding for port 80 doesn’t actually point to the CentOS server that is running Apache, then yes, the HTTP challenge is going to fail.

3 Likes