1. Browser won't allow overriding, e.g. if the cipher is too weak, and it is possible that some beta browser version enforce new restrictions
2. Browser will allow override if you accept the cert. If this was the case, then you really wasted our time.
I was able to get past the certificate warning but this is just another security issue. This is just another security issue that needs to be fixed. Sorry to have wasted your time but it seems to me that if HTTPS is going to be a feature it should be made easy to replace the default certificate. I'm not criticizing the developers, I'm just giving feedback.
HTTPS (...) might be a problem on older units that do not have enough flash to include openssl, which is necessary nowadays, since browsers do not allow the use of old ciphers anymore.
(...)
HTTPS is not supported anymore on this router, it only has 4MB flash and therefore comes with an old ssl lib. There is not enough flash to upgrade the ssl lib on these models.
This is most interesting what Kong is saying, it should be sticked somewhere because many users (including me) wondered why simple "https" checkbox enabling crashed their devices making them unresponsive. It was due to security limitations of modern browsers denying access to too weak SSL. Now it makes perfect sense: 4MB flash memory devices cannot handle https connection meaning you need an 8MB+ OpenVPN capable router to establish a https connection with.
