Cannot renew, no valid IP addresses found

Trying to renew my cert which expires in 18 days!!

root@localhost:/etc/letsencrypt# certbot renew --dry-run
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/streamingworld.us-0001.conf


Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for streamingworld.us
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (streamingworld.us-0001) from /etc/letsencrypt/renewal/streamingworld.us-0001.conf produced an unexpected error: Failed authorization procedure. streamingworld.us (http-01): urn:ietf:params:acme:error:dns :: No valid IP addresses found for streamingworld.us. Skipping.


Processing /etc/letsencrypt/renewal/streamingworld.us.conf


Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for streamingworld.us
http-01 challenge for www.streamingworld.us
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (streamingworld.us) from /etc/letsencrypt/renewal/streamingworld.us.conf produced an unexpected error: Failed authorization procedure. streamingworld.us (http-01): urn:ietf:params:acme:error:dns :: No valid IP addresses found for streamingworld.us. Skipping.


Processing /etc/letsencrypt/renewal/www.streamingworld.us.conf


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


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

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: streamingworld.us
    Type: None
    Detail: No valid IP addresses found for streamingworld.us

  • The following errors were reported by the server:

    Domain: streamingworld.us
    Type: None
    Detail: No valid IP addresses found for streamingworld.us

  • The following errors were reported by the server:

    Domain: www.streamingworld.us
    Type: connection
    Detail: Fetching
    https://www.streamingworld.us/.well-known/acme-challenge/G79DC19Vluxx03-I-cFyGkOdob5ay_igGEpCCcjyHUQ:
    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.

  • Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.
    root@localhost:/etc/letsencrypt#

this is right, there is no A record for streamingworld.us

# dig streamingworld.us

; <<>> DiG 9.16.1-Ubuntu <<>> streamingworld.us
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53389
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;streamingworld.us.             IN      A

;; Query time: 3 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Jul 30 14:25:38 CEST 2020
;; MSG SIZE  rcvd: 46

add an A record for that domain

like: @ 300 in A 10.10.10.10

this is the same error

This I cannot reproduce, check your firewall. And make sure Apache your webserver is running during validation.

# curl -IL www.streamingworld.us/.well-known/acme-challenge/404
HTTP/1.1 302 Found
Cache-Control: no-cache
Content-length: 0
Location: https://www.streamingworld.us/.well-known/acme-challenge/404

HTTP/1.1 404 Not Found
Server: nginx/1.17.10 (Ubuntu)
Date: Thu, 30 Jul 2020 12:23:45 GMT
Content-Type: text/html
Content-Length: 163

You probably mean “webserver” in general here, as the topicstarter doesn’t run Apache it seems :wink:

1 Like

I am fairly new to using DNS. My Domain is with Go Daddy. My website is hosted by Linode.
I guess I am confused as to where I create this A record?
That said, my Domain Manager (Go Daddy) is pointing to my Linode Nameservers.
My Linode has an A record for streamingworld.us and just streamingworld.

dig streamingworld.us resuts in still no IP? Here is my web host A records.

You need to add an A record for “@” to the ip of the webserver.

I am now getting this error when I do certbot renew:

root@localhost:/etc/letsencrypt/live/www.streamingworld.us# certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/streamingworld.us-0001.conf


Cert not yet due for renewal


Processing /etc/letsencrypt/renewal/streamingworld.us.conf


Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Attempting to renew cert (streamingworld.us) from /etc/letsencrypt/renewal/streamingworld.us.conf produced an unexpected error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping.


Processing /etc/letsencrypt/renewal/www.streamingworld.us.conf


Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Attempting to renew cert (www.streamingworld.us) from /etc/letsencrypt/renewal/www.streamingworld.us.conf produced an unexpected error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/streamingworld.us/fullchain.pem (failure)
/etc/letsencrypt/live/www.streamingworld.us/fullchain.pem (failure)


The following certs are not due for renewal yet:
/etc/letsencrypt/live/streamingworld.us-0001/fullchain.pem expires on 2020-10-28 (skipped)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/streamingworld.us/fullchain.pem (failure)
/etc/letsencrypt/live/www.streamingworld.us/fullchain.pem (failure)


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

this should go away in an hour (and the original error will come back).

use certbot renew --dry-run in the meantime.

By the way, I’ve removed the screaming “HELP” from your thread title: the capitals are rude and everybody in the ‘Help’ section is asking for help which therefore makes it superfluous.

I’ve also added a few words b/c otherwise the Discourse would complain about too few letters…

certbot renew --dry-run fails.

root@localhost:/etc/letsencrypt/live/www.streamingworld.us# certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/streamingworld.us-0001.conf


Cert not yet due for renewal


Processing /etc/letsencrypt/renewal/streamingworld.us.conf


Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for www.streamingworld.us
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (streamingworld.us) from /etc/letsencrypt/renewal/streamingworld.us.conf produced an unexpected error: Failed authorization procedure. www.streamingworld.us (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://www.streamingworld.us/.well-known/acme-challenge/yvth5mmgV--c6OmRDXX0uDqa0zXGSSPj6lFH4Fugi0I: Timeout during connect (likely firewall problem). Skipping.


Processing /etc/letsencrypt/renewal/www.streamingworld.us.conf


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


The following certs are not due for renewal yet:
/etc/letsencrypt/live/streamingworld.us-0001/fullchain.pem expires on 2020-10-28 (skipped)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/streamingworld.us/fullchain.pem (failure)
/etc/letsencrypt/live/www.streamingworld.us/fullchain.pem (failure)


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

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: www.streamingworld.us
    Type: connection
    Detail: Fetching
    https://www.streamingworld.us/.well-known/acme-challenge/YeCWs0vYVvFbZqECR0eL1B98npHYAetRThJdoTQCNbQ:
    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.

  • The following errors were reported by the server:

    Domain: www.streamingworld.us
    Type: connection
    Detail: Fetching
    https://www.streamingworld.us/.well-known/acme-challenge/yvth5mmgV--c6OmRDXX0uDqa0zXGSSPj6lFH4Fugi0I:
    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.
    root@localhost:/etc/letsencrypt/live/www.streamingworld.us#

So here basically is my issue:

Your IPv6 isn’t working. Let’s Encrypt prefers IPv6 when an AAAA record is present. It doesn’t do IPv4 fallback, probably due to security reasons (Let’s Encrypt doesn’t know the reason why IPv6 doesn’t work, could be a MitM trying to limit connectivity to make his attack vector better for example).

My webserver is nodejs running on a LXD container.
It is accessed via a subdomain bcast I showed in my previous comment.

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