OneZyUser  Freshman Member

@Zyxel_Stanley, the problem is if I disable admin access to port 443 (https, or 80 http) from WAN (so that only admins can access it from within the LAN), I should be able to free up that port for a virtual server behind NAT (when coming from WAN, and nat_loopback disabled). Another corner case is, as it happened to me, if…

I was able to add it via CLI. Still don't understand why I cannot add it via GUI/Web interface though. So, leaving this thread open in case someone can explain. The CLI command I used was: configure terminal ip virtual-server <rule_name> interface wan1 original-ip WAN4 map-to <server_host_ip_object> map-type port protocol…

Nevermind my last reply... The first time, I generated a pkcs12 file with both the cert and CAcert bundled together. After some thought, I imported the CA cert separately (the direct crt file I got from namecheap) and generated a pkcs12 with only the wild card crt file. This did the trick. Thanks again to @zyman2008 for…

Hi @Zyxel_Charlie, do you know if there has been any update on this?

Thanks @zyman2008 I did that, but right after I did it, the web interface became unavailable until I reverted back to the old (URL specific certificate). Is there any thing else that is needed when the certificate has is wildcard?