Renew LetsEncrypt Certificate

[Kal1975]

I noticed today when trying to set up a server on my network with HTTPS that the LetsEncrypt certificate that I had set up for my RT-AC3100 had expired. I'm trying to renew it but it doesn't seem to be working. I've tried to:

• On the WAN > DDNS page, just pressing Apply without making any changes
• Setting the SSL certificate to none, applying the change, setting it back to LetsEncrypt and applying
• Running /sbin/le_acme from the command line. This causes a few entries in the system log and then nothing...comes back to the prompt.

I've also turned the le_acme_debug NVRAM setting on. Some partial output from the system log follows. It looks like there is a fetch to http://abc.no-ip.biz/.well-known/acme-challenge/A3B4YY-UmrLFY4-D_tKVRMnn_mSyKR3Gmx54UPZq_7g that times out. This seems fine as Merlin should only allow access using HTTPS. It's also asking to serve something that I wouldn't think is accessible externally.

Am I doing something wrong? Is this the correct procedure and if not, what is the correct procedure?

Thanks in advance.

Jun 20 23:17:00 rc_service: httpd 13304:notify_rc restart_ddns_le
Jun 20 23:17:00 custom_script: Running /jffs/scripts/service-event (args: restart ddns_le) - max timeout = 120s
Jun 20 23:17:00 start_ddns: update [URL='http://WWW.NO-IP.COM']WWW.NO-IP.COM[/URL] [EMAIL]default@no-ip.com[/EMAIL], wan_unit 0
Jun 20 23:17:01 inadyn[14741]: In-a-dyn version 2.5 -- Dynamic DNS update client.
Jun 20 23:17:02 inadyn[14741]: Update forced for alias abc.no-ip.biz, new IP# 99.99.99.99
Jun 20 23:17:03 inadyn[14741]: Updating cache for abc.no-ip.biz
Jun 20 23:17:17 kernel: /usr/sbin/acme-client: [URL]https://acme-v01.api.letsencrypt.org/acme/challenge/OGcJBjKq9PqvmOdj_aZeW_MSguqvAEPJw5vMrwa0z9s/17325947124[/URL]: bad response
Jun 20 23:17:17 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching [URL]http://abc.no-ip.biz/.well-known/acme-challenge/A3B4YY-UmrLFY4-D_tKVRMnn_mSyKR3Gmx54UPZq_7g[/URL]: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "[URL]https://acme-v01.api.letsencrypt.org/acme/challenge/OGcJBjKq9PqvmOdj_aZeW_MSguqvAEPJw5vMrwa0z9s/17325947124[/URL]", "token": "A3B4YY-UmrLFY4-D_tKVRMnn_mSyKR3Gmx5
Jun 20 23:17:19 rc_service: le_acme 14757:notify_rc restart_httpd
Jun 20 23:28:58 kernel: /usr/sbin/acme-client: /tmp/.le/www/.well-known/acme-challenge: -C directory must exist
Jun 20 23:33:45 kernel: /usr/sbin/acme-client: /jffs/.le/account.key: account key exists (not creating)
Jun 20 23:33:45 kernel: /usr/sbin/acme-client: /jffs/.le/abc.no-ip.biz/domain.key: domain key exists (not creating)
Jun 20 23:33:45 kernel: /usr/sbin/acme-client: /tmp/.le/www/.well-known/acme-challenge: -C directory must exist
Jun 20 23:36:41 kernel: /usr/sbin/acme-client: /jffs/.le/account.key: account key exists (not creating)
Jun 20 23:36:41 kernel: /usr/sbin/acme-client: /jffs/.le/abc.no-ip.biz/domain.key: domain key exists (not creating)
Jun 20 23:36:41 kernel: /usr/sbin/acme-client: /tmp/.le/www/.well-known/acme-challenge: -C directory must exist
Jun 20 23:39:25 rc_service: httpd 14847:notify_rc restart_ddns_le
Jun 20 23:39:25 custom_script: Running /jffs/scripts/service-event (args: restart ddns_le) - max timeout = 120s
Jun 20 23:39:25 start_ddns: update [URL='http://WWW.NO-IP.COM']WWW.NO-IP.COM[/URL] [EMAIL]default@no-ip.com[/EMAIL], wan_unit 0
Jun 20 23:39:26 inadyn[18895]: In-a-dyn version 2.5 -- Dynamic DNS update client.
Jun 20 23:39:26 inadyn[18895]: Update forced for alias abc.no-ip.biz, new IP# 99.99.99.99
Jun 20 23:39:27 inadyn[18895]: Updating cache for abc.no-ip.biz
Jun 20 23:39:30 kernel: /usr/sbin/acme-client: /jffs/.le/account.key: account key exists (not creating)
Jun 20 23:39:30 kernel: /usr/sbin/acme-client: /jffs/.le/abc.no-ip.biz/domain.key: domain key exists (not creating)
Jun 20 23:39:30 kernel: /usr/sbin/acme-client: /jffs/.le/abc.no-ip.biz/cert.pem: certificate renewable: -229 days left
Jun 20 23:39:30 kernel: /usr/sbin/acme-client: [URL]https://acme-v01.api.letsencrypt.org/directory[/URL]: directories
Jun 20 23:39:30 kernel: /usr/sbin/acme-client: acme-v01.api.letsencrypt.org: DNS: 88.88.88.88
Jun 20 23:39:30 kernel: /usr/sbin/acme-client: [URL]https://acme-v01.api.letsencrypt.org/acme/new-reg[/URL]: new-reg
Jun 20 23:39:31 kernel: /usr/sbin/acme-client: [URL]https://acme-v01.api.letsencrypt.org/acme/new-authz[/URL]: req-auth: abc.no-ip.biz
Jun 20 23:39:31 kernel: /usr/sbin/acme-client: /tmp/.le/www/.well-known/acme-challenge/cLKLvRrVjaKdW88Z3iAfIeVZdDzx9T_kzjfsMyvCNK4: created
Jun 20 23:39:31 kernel: /usr/sbin/acme-client: [URL]https://acme-v01.api.letsencrypt.org/acme/challenge/QdZYv_iJBpzeSpr37qIpDbx-6Mk2Kr5NnMy555-4RUY/17326543208[/URL]: challenge
Jun 20 23:39:37 kernel: /usr/sbin/acme-client: [URL]https://acme-v01.api.letsencrypt.org/acme/challenge/QdZYv_iJBpzeSpr37qIpDbx-6Mk2Kr5NnMy555-4RUY/17326543208[/URL]: status
Jun 20 23:39:42 kernel: /usr/sbin/acme-client: [URL]https://acme-v01.api.letsencrypt.org/acme/challenge/QdZYv_iJBpzeSpr37qIpDbx-6Mk2Kr5NnMy555-4RUY/17326543208[/URL]: status
Jun 20 23:39:42 kernel: /usr/sbin/acme-client: [URL]https://acme-v01.api.letsencrypt.org/acme/challenge/QdZYv_iJBpzeSpr37qIpDbx-6Mk2Kr5NnMy555-4RUY/17326543208[/URL]: bad response
Jun 20 23:39:42 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching [URL]http://abc.no-ip.biz/.well-known/acme-challenge/cLKLvRrVjaKdW88Z3iAfIeVZdDzx9T_kzjfsMyvCNK4[/URL]: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "[URL]https://acme-v01.api.letsencrypt.org/acme/challenge/QdZYv_iJBpzeSpr37qIpDbx-6Mk2Kr5NnMy555-4RUY/17326543208[/URL]", "token": "cLKLvRrVjaKdW88Z3iAfIeVZdDzx9T_kzjf
Jun 20 23:39:42 kernel: /usr/sbin/acme-client: bad exit: netproc(18921): 1