Stuck on updating status

I recently bought an asus router (RT-AC86U) and I’m trying to use the let’s enctrypt on the DDNS service. I have a host on dyndns but the server certificate always stuck in the “updating” status.
Here follows the log-file. What should I do?
My router is in the firmware:[3.0.0.4.384_45717] and the DDNS are working fine, just the encryption that is not woking well

Jul 2 09:39:26 start_ddns: update WWW.DYNDNS.ORG dyndns, wan_unit 0
Jul 2 09:39:26 ddns update: ez-ipupdate: starting…
Jul 2 09:39:27 ddns update: connected to members.dyndns.org (162.88.175.12) on port 443.
Jul 2 09:39:27 ddns update: members.dyndns.org says that your IP address has not changed since the last update
Jul 2 09:39:27 ddns update: asusddns_update: 0
Jul 2 09:39:27 ddns: ddns update ok
Jul 2 09:39:27 ddns update: exit_main
Jul 2 09:39:30 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Jul 2 09:39:30 kernel: acme-client: transfer buffer: [{ “type”: “urn:acme:error:rateLimited”, “detail”: “Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/”, “status”: 429 }] (189 bytes)
Jul 2 09:40:00 rc_service: service 19101:notify_rc restart_letsencrypt
Jul 2 09:40:17 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/challenge/lyBPqqHPw9emFr2mzQWMRFriuNWx7SNKiQZElILFyrc/17776385678: bad response
Jul 2 09:40:17 kernel: acme-client: transfer buffer: [{ “type”: “http-01”, “status”: “invalid”, “error”: { “type”: “urn:acme:error:connection”, “detail”: “Fetching http://eutevejo.dyndns.org/.well-known/acme-challenge/HiKKrkyg9iNvZOwrWaOKpbbL3u76wxTk7yB3Y-cHL44: Timeout during connect (likely firewall problem)”, “status”: 400 }, “uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/lyBPqqHPw9emFr2mzQWMRFriuNWx7SNKiQZElILFyrc/17776385678”, “token”: “HiKKrkyg9iNvZOwrWaOKpbbL3u76wxTk7yB3Y-cHL44”, "

Hi @rafabhmg, welcome to the community forum :wave:

This is caused by the Asus ACME client trying and failing to issue certificates too often. You might want to consider opening a support issue with them to ask if they have any bug fixes available that would prevent hitting this rate limit.

This looks like the reason that the validations are failing.

Does your home internet service provider block inbound HTTP requests on port 80? That's often a choice that residential ISPs will make that results in an error like the one you are seeing.

1 Like

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