If I understand correctly, in the new version of the firmware WAN access is only through HTTPS, no more HTTP, and for that the router generates a certificate.
Problem is, at least in my case, it generates it not for the external name that is actually used. I'm using DNSOMATIC that further sends updates to afraid.org and opendns. Usually I access the router from outside using <mydomain>.mooo.com . But the certificate that the router has generated is not for that domain - in the following screenshots, all names pertain to the LAN.
Also note that that under "local access config" page instructs to access the router using external name (the correct one), while under "remote access config" is tells to access it using all.dnsomatic.com, which wouldn't work.
Problem is, at least in my case, it generates it not for the external name that is actually used. I'm using DNSOMATIC that further sends updates to afraid.org and opendns. Usually I access the router from outside using <mydomain>.mooo.com . But the certificate that the router has generated is not for that domain - in the following screenshots, all names pertain to the LAN.
Also note that that under "local access config" page instructs to access the router using external name (the correct one), while under "remote access config" is tells to access it using all.dnsomatic.com, which wouldn't work.
