Lets Encrypt broken on RT-AX88U

[sanke1]

I have changed my LAN IP address to 192.168.1.1 (ASUS idiotically assigns 192.168.50.1 as default IP address after reset)
So it is trying to get a certificate for 192.168.50.1 from the screenshot and failing hard.

RT-AC88U on 3.0.0.4.384_6436 firmware. Tried nvram reset and everything. Same issue every time.

 

[sanke1]

Log entries

Oct 17 22:39:08 kernel: acme-client: SSL_read return 5: Success
Oct 17 22:39:08 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-reg: bad comm
Oct 17 22:39:08 kernel: acme-client: transfer buffer: [{ "4hqECmJmAxc": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417", "key-change": "https://acme-v01.api.letsencrypt.org/acme/key-change", "meta": { "caaIdentities": [ "letsencrypt.org" ], "terms-of-service": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf", "website": "https://letsencrypt.org" }, "new-authz": "https://acme-v01.api.letsencrypt.org/acme/new-authz", "new-cert": "https://acme-v01.api.
Oct 17 22:39:10 kernel: acme-client: SSL_read return 5: Success
Oct 17 22:39:10 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad comm
Oct 17 22:39:10 kernel: acme-client: transfer buffer: [{ "4hqECmJmAxc": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417", "key-change": "https://acme-v01.api.letsencrypt.org/acme/key-change", "meta": { "caaIdentities": [ "letsencrypt.org" ], "terms-of-service": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf", "website": "https://letsencrypt.org" }, "new-authz": "https://acme-v01.api.letsencrypt.org/acme/new-authz", "new-cert": "https://acme-v01.api.

 

[Grisu]

or on all Asus?
https://www.snbforums.com/threads/l...enew-due-to-port-80-closed.48394/#post-520296

 

[sanke1]

Oct 28 18:33:25 kernel: acme-client: SSL_read return 5: Success
Oct 28 18:33:25 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-reg: bad comm
Oct 28 18:33:25 kernel: acme-client: transfer buffer: [{ "U_LFJV9nggI": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417", "key-change": "https://acme-v01.api.letsencrypt.org/acme/key-change", "meta": { "caaIdentities": [ "letsencrypt.org" ], "terms-of-service": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf", "website": "https://letsencrypt.org" }, "new-authz": "https://acme-v01.api.letsencrypt.org/acme/new-authz", "new-cert": "https://acme-v01.api.
Oct 28 18:34:00 rc_service: service 4684:notify_rc restart_letsencrypt
Oct 28 18:34:08 kernel: acme-client: SSL_read return 5: Success
Oct 28 18:34:08 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-reg: bad comm
Oct 28 18:34:08 kernel: acme-client: transfer buffer: [{ "hpmh1Go5TKc": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417", "key-change": "https://acme-v01.api.letsencrypt.org/acme/key-change", "meta": { "caaIdentities": [ "letsencrypt.org" ], "terms-of-service": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf", "website": "https://letsencrypt.org" }, "new-authz": "https://acme-v01.api.letsencrypt.org/acme/new-authz", "new-cert": "https://acme-v01.api.
Oct 28 18:34:10 kernel: acme-client: SSL_read return 5: Success
Oct 28 18:34:10 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad comm
Oct 28 18:34:10 kernel: acme-client: transfer buffer: [{ "hpmh1Go5TKc": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417", "key-change": "https://acme-v01.api.letsencrypt.org/acme/key-change", "meta": { "caaIdentities": [ "letsencrypt.org" ], "terms-of-service": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf", "website": "https://letsencrypt.org" }, "new-authz": "https://acme-v01.api.letsencrypt.org/acme/new-authz", "new-cert": "https://acme-v01.api.

 

[Andy1932]

I can’t seem to pin a specific response on mobile, but Merlin addresses this on page 2.
ASUS is aware and working on it.
https://www.snbforums.com/threads/lets-encrypt-not-updating-or.59524/page-2