Router keeps generating its own certificate despite having Let's Encrypt after 3006.102.5 update

[Ceejus]

Ever since updating my GT-BE98 Pro to 3006.102.5, I keep encountering an issue where my browsers randomly stop trusting my DDNS address due to suddenly reading a self-signed router-generated root certificate rather than the Let's Encrypt certificate that is actively shown in the DDNS section. Selecting "Auto" under the DDNS, resaving, then switching back to Let's Encrypt gets the browser to begin reading the Let's Encrypt certificate for a little while (anywhere between 20 minutes - a few days) before eventually presenting another self-signed root certificate again.

What is causing this? I wasn't seeing this issue with 3006.102.4. Is there a workaround that doesn't involve a factory reset?

 

[Ripshod]

Enable connections by only https. No reason discovered yet but my router seemed to serve up an self-signed tls instead of let's Encrypt when access was set to "Both".
**Edit**. Just tested and it still does the same on the alpha, but no surprise as only gui elements have been changed.

 

[scootertramp]

Seeing the same issue, but I have only noticed it after a reboot. Connections are set to https only.
Have to jump thru the same hoops to get Let's Encrypt working again.