Unable to get a new cert using cert bot

Help
1

Getting the below error when trying to renew the cert for the domain.
the server could not connect to the client to verify the domain timeout

My domain is: telemetry.blueprism.it

I ran this command: sudo certbot renew --cert-name telemetry.blueprism.it -a webroot -w /var/www/html1/ --dry-run

It produced this output: Processing /etc/letsencrypt/renewal/telemetry.blueprism.it.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for telemetry.blueprism.it
Using the webroot path /var/www/html1 for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (telemetry.blueprism.it) from /etc/letsencrypt/renewal/telemetry.blueprism.it.conf produced an unexpected error: Failed authorization procedure. telemetry.blueprism.it (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://telemetry.blueprism.it/.well-known/acme-challenge/pJVEwZ03TJfu0xx_1kewTGmgwOgZvOWgfGqr5QbvwYo: Timeout during connect (likely firewall problem). Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/telemetry.blueprism.it/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/telemetry.blueprism.it/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)

1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: telemetry.blueprism.it
    Type: connection
    Detail: Fetching
    http://telemetry.blueprism.it/.well-known/acme-challenge/pJVEwZ03TJfu0xx_1kewTGmgwOgZvOWgfGqr5QbvwYo:
    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
    that you are serving files from the webroot path you provided.

My web server is (include version): 18.0 - ubuntu

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

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

1 Like
2

Hi @Bob403020

there is a check of your domain, 20 minutes old - https://check-your-website.server-daten.de/?q=telemetry.blueprism.it

Only timeouts:

Domainname Http-Status redirect Sec. G
• http://telemetry.blueprism.it/ 52.142.117.156 -14 10.026 T
Timeout - The operation has timed out
• https://telemetry.blueprism.it/ 52.142.117.156 -14 10.046 T
Timeout - The operation has timed out
• http://telemetry.blueprism.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.142.117.156 -14 10.027 T
Timeout - The operation has timed out

If you want to use webroot as authenticator, you use http validation. So an open port 80 is required.

Works http internal?

curl http://telemetry.blueprism.it/
curl http://telemetry.blueprism.it/.well-known/acme-challenge/1234

If yes, it's a firewall- or routing problem.

2 Likes
3

Hi @JuergenAuer - I can confirm that port 80 is open and still getting the same issue, when you say that the domain timeout, I did check on the site, to see if I could find the problem, but it still shows the same error, When you say routing problem, is there steps I can take to see where it fails, like on windows there is a traceroute option.

4

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