Attempting to renew cert / produced an unexpected error: Failed authorization procedure

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: https://cloud.etbvandebeek.nl

I ran this command: sudo certbot renew --dry-run, sudo certbot --apache

It produced this output:
sudo certbot renew --dry-run
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/cloud.etbvandebeek.nl.conf


Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Running pre-hook command: service apache2 stop
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for cloud.etbvandebeek.nl
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (cloud.etbvandebeek.nl) from /etc/letsencrypt/renewal/cloud.etbvandebeek.nl.conf produced an unexpected error: Failed authorization procedure. cloud.etbvandebeek.nl (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://cloud.etbvandebeek.nl/.well-known/acme-challenge/-2FodLn7mgHiKpdtDdchNhiXxZwzfLLf5qhQjQfW0r4: Timeout during connect (likely firewall problem). Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/cloud.etbvandebeek.nl/fullchain.pem (failure)


** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/cloud.etbvandebeek.nl/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)


Running post-hook command: service apache2 start
1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: cloud.etbvandebeek.nl
    Type: connection
    Detail: Fetching
    http://cloud.etbvandebeek.nl/.well-known/acme-challenge/-2FodLn7mgHiKpdtDdchNhiXxZwzfLLf5qhQjQfW0r4:
    Timeout during connect (likely firewall problem)

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify

My web server is (include version):Server version: Apache/2.4.18 (Ubuntu)
Server built: 2019-04-03T13:34:47

The operating system my web server runs on is (include version):
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial

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

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

Hi @wpp

your port 80 doesn't answer ( https://check-your-website.server-daten.de/?q=cloud.etbvandebeek.nl ):

Domainname Http-Status redirect Sec. G
http://cloud.etbvandebeek.nl/
83.247.50.191 -14 10.026 T
Timeout - The operation has timed out
https://cloud.etbvandebeek.nl/
83.247.50.191 302 Purple ~ Powered By Fancit 1.093 B
Purple ~ Powered By Fancit 200 0.290 B
Purple ~ Powered By Fancit
83.247.50.191 -14 10.030 T
Timeout - The operation has timed out

Is there a firewall that blocks? Is port 80 configured?

If you want to use http-01 validation, an open port 80 is required.

@JuergenAuer Thats weird because i can telnet to port 80 from my local machine

1 Like

@JuergenAuer never mind fixed it already someone added ad second portforwarding for port 80 thats why i could telnet but not renew lmao.

1 Like

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