"Funny" you mention that--I was just working on the patches and notes and noticed that problem. The problem is this: https://github.com/RMerl/asuswrt-merlin/pull/42 "One of the changes Broadcom did is add support for the -setstartsecs option, which is used in httpd/gencert.sh. This will have to be re-added, or else certificate generation for the httpd will break." I want to apologize for any problems this caused. I have PM'ed Toastman with the fix, and I tested it on my router. I had no problems with https on mine, but I didn't try to regenerate the https certificate. I just tested that and it definitely is not working. DO NOT regenerate the HTTPS certificate in the admin menu, or the router admin pages will stop working. I've found a reboot fixes it if it's saved to NVRAM, but if not, I'm not sure what will happen. If you do that and you cannot access the admin pages, do the following steps to fix your router's http pages via ssh or telnet: The initial install was broken because it did not include the changes to support -setstartsecs. If you installed such a build, do the following: cd /etc cp /usr/sbin/gencert.sh . vi gencert.sh Change the line: openssl x509 -in /tmp/cert.csr -out cert.pem -req -signkey key.pem -setstartsecs $SECS -days 3653 -set_serial $1 to: openssl x509 -in /tmp/cert.csr -out cert.pem -req -signkey key.pem -days 3653 Then do :wq! to save, quit, and exit. sh gencert.sh cd /www httpd -d This should fix the problem, at least until you reboot. Keep in mind this is a temporary fix until the next release is out. When you upgrade to that release, you should regenerate your https certificates. If anyone needs the actual changes to x509.c before Toastman can commit them to git, send me a PM. I'll follow up.