Status stuck on " updating "


#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. 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:

I ran this command:

It produced this output:

My web server is (include version):none

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

My hosting provider, if applicable, is: bigcid10.ddns.net

I can login to a root shell on my machine (yes or no, or I don’t know):no

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

I have a asus router RT-AC88U
My ddns section won’t update my wan ip
can the admins update it for me
Thank you

Sep 30 11:45:01 rc_service: service 1853:notify_rc restart_letsencrypt
Sep 30 11:45:17 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/challenge/pv_5fTqT6y5hQMKLDAqCdkSS1TmNFPShvPbKB4LmV5A/7825722093: bad response
Sep 30 11:45:17 kernel: /usr/sbin/acme-client: transfer buffer: [{ “type”: “http-01”, “status”: “invalid”, “error”: { “type”: “urn:acme:error:connection”, “detail”: “Fetching http://bigcid10.ddns.net/.well-known/acme-challenge/nkq_usZrXp1YVXHha0-BRE6hS5oIWppJ36vcMmVJ0yA: Timeout during connect (likely firewall problem)”, “status”: 400 }, “uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/pv_5fTqT6y5hQMKLDAqCdkSS1TmNFPShvPbKB4LmV5A/7825722093”, “token”: "nkq_usZrXp1YVXHha0-BRE6hS5oIWppJ36vcMmVJ0
Sep 30 11:50:00 rc_service: service 2049:notify_rc restart_letsencrypt
Sep 30 11:50:05 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Sep 30 11:50:05 kernel: /usr/sbin/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)
Sep 30 11:51:59 rc_service: httpds 1215:notify_rc restart_ddns_le
Sep 30 11:51:59 start_ddns: update WWW.NO-IP.COM default@no-ip.com, wan_unit 0
Sep 30 11:51:59 inadyn[2173]: In-a-dyn version 2.4 – Dynamic DNS update client.
Sep 30 11:52:00 inadyn[2173]: Update forced for alias bigcid10.ddns.net, new IP# 73.205.210.178
Sep 30 11:52:00 inadyn[2173]: Updating cache for bigcid10.ddns.net
Sep 30 11:52:05 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Sep 30 11:52:05 kernel: /usr/sbin/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)
Sep 30 11:55:01 rc_service: service 2295:notify_rc restart_letsencrypt
Sep 30 11:55:08 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Sep 30 11:55:08 kernel: /usr/sbin/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)
Sep 30 12:00:01 rc_service: service 2459:notify_rc restart_letsencrypt
Sep 30 12:00:06 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Sep 30 12:00:06 kernel: /usr/sbin/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)
Sep 30 12:05:01 rc_service: service 2618:notify_rc restart_letsencrypt
Sep 30 12:05:08 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Sep 30 12:05:08 kernel: /usr/sbin/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)


#2

Hi,

I’m sorry but I don’t quite get what’s your question.
First of all, are you trying to ask us to update your ddns pointed IP address for you? (e.g. the IP address changed and the resolved IP didn’t change)

Let’s encrypt query your authorizative name servers for the best result, avoiding changes not in effect, which means all results are the latest from your DNS provider.

Hence, if you want us to update the resolved IP address, we can’t do that since it’s reported from your DNS provider, contact your ddns provider or try to reboot your router.

Thank you


#3

Hi @bigcid10

you hit the limit

There is a Failed Validation limit of 5 failures per account, per hostname, per hour.

One hour later, it should work. But looks like your firewall or something else blocks. So you should first resolve that problem.

I must be able to get a server answer (http status 200 or 404) loading

http://bigcid10.ddns.net/.well-known/acme-challenge/nkq_usZrXp1YVXHha0-BRE6hS5oIWppJ36vcMmVJ0yA

or

http://bigcid10.ddns.net/

not a timeout.


#4

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