Letsencrypt reissue certificate

Help
1

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: learnchinese.kaiqiaozhi.space

I ran this command: certbot certonly -d learnchinese.kaiqiaozhi.space

It produced this output:
How would you like to authenticate with the ACME CA?

1: Apache Web Server plugin (apache)
2: Spin up a temporary webserver (standalone)
3: Place files in webroot directory (webroot)

Select the appropriate number [1-3] then [enter] (press 'c' to cancel): 3
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for learnchinese.kaiqiaozhi.space
Input the webroot for learnchinese.kaiqiaozhi.space: (Enter 'c' to cancel): /var/www/vhosts/kaiqiaozhi.space/learnchinese.kaiqiaozhi.space
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. learnchinese.kaiqiaozhi.space (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: 198.244.188.95: Fetching https://learnchinese.kaiqiaozhi.space/.well-known/acme-challenge/yv2sgaZofjoHacwGJ-qITrYlgAdhBRmt2nhCWG_HxZQ: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: learnchinese.kaiqiaozhi.space
    Type: connection
    Detail: 198.244.188.95: Fetching
    https://learnchinese.kaiqiaozhi.space/.well-known/acme-challenge/yv2sgaZofjoHacwGJ-qITrYlgAdhBRmt2nhCWG_HxZQ:
    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):

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

My hosting provider, if applicable, is: vps

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

2

Hi @yskapell, and welcome to the LE community forum :slight_smile:

You need an HTTP site that is accessible from the whole Internet.

You should upgrade that to a much newer version.
The latest is 2.9.0 [or 2.10.0]

3 Likes
3

Your IPv6 connection is timing out. Check the value in your DNS AAAA record. If you do not support IPv6 you should remove that record.

The Let's Encrypt server is trying an IPv6 connection but getting timed out. It then retries as IPv4 which reaches your nginx server. But, you then redirect the acme challenge request to HTTPS. When LE Server tries that it again times out on IPv6 and does not try IPv4 again.

The error message always shows the IPv4 address in this case. Which does not make it easy to identify this problem but I can reproduce this on my test system.

4 Likes
4

They really should fix this in Boulder :confused:

3 Likes
5

Hello,

I removed the IPv6 and I was able to renew the certificate without any issue.

What can I do if I decide to reassign the IPv6 ?

1 Like
6

Make sure the IPv6 address is correct for your server.

Check any firewall to ensure it allows IPv6.

You can test that connectivity with Let's Debug
https://letsdebug.net

4 Likes
7

And make sure the web server vhost(s) is/are listening to both IPv4 and IPv6.
[IPv6 listening isn't always turned on by default]

3 Likes
8

I don’t know about this bug. Somebody should file it in GitHub, please!

3 Likes
9

Oh, I thought this was already known. I'll see if I can set up a test host which can trigger the error.

[edit]Hmm, although Cloudflare seems to be able to proxy A RR but not AAAA RRs in their control dashboard, in reality the AAAA RR also gets proxied.. So I can't let that one time out using CF.. So I'll just open an issue with a link to this thread and explain it with words.

3 Likes
10

Me too. I've asked about it a couple times in threads where staff were involved without any comment. I assumed that meant it was expected.

3 Likes
11
2 Likes
12

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