Let's Encrypt server certificate unknown or processing

[dmr24]

I factory reset my rt ax86u and using firmware 3004.388.9.2 and setting up ddns with let's Encrypt. However the server certificate is showing unknown or processing which it's never done before and affecting my usb drive remote access that uses ddns. How do I rectify this?

Note, I removed my Asus name for security reasons but even when added same issue.

 

[dacotmeister]

I've encountred the same behaviour on my RT-AX88UPro and have solved it by switching to import your own certificate. Generate a dyndns.org one from a linux based VM or stand alone distro and upload your .pem files into your router/browser

 

[FLA_NL]

Did you try to click on the apply button again? Most issues are solved for me that way. Sometimes for refreshing the certificate and sometimes when Ddns is not synchronizing.

 

[Eodyne]

This has been an issue (both with LetsEncrypt and using your own certificate) for months now through multiple updates of the firmware. At this point I just don't expect it to be fixed.

 

[scootertramp]

You might try a solution I found after a firmware change where I was in the same position.

Not seeing any server certificate information on the ddns page after changing ASUS official firmware to 3004.388.8_4-gnuton1.

The letsencrypt process scheduled in cron has run. This was populated prior to the firmware change. Is this just something that should populate when the cert actually gets renewed? I will have to wait awhile if that's the case. Thanks

www.snbforums.com

 

[Eodyne]

You might try a solution I found after a firmware change where I was in the same position.

Not seeing any server certificate information on the ddns page after changing ASUS official firmware to 3004.388.8_4-gnuton1.

The letsencrypt process scheduled in cron has run. This was populated prior to the firmware change. Is this just something that should populate when the cert actually gets renewed? I will have to wait awhile if that's the case. Thanks

www.snbforums.com

Yeah I saw that when I was trying to get it working. No luck for me, I'm assuming it has something to do with me trying to do ddns through cloudflare with a custom ddns-start script. Just hasn't been working well for me.