When we use the HTTPS captive portal page in Hotspot Web Portal function, sometimes the hotspot client only gets "Your connection is not private" as the image showing below, "Untrusted Connection" or "Invalid Security Certificate." These are common warning messages when we try to open an HTTPS website which does not have a trusted certificate but using a self-signed certificate instead. It occurs in all web browsers no matter its Safari, Internet Explorer, Google Chrome or Mozilla Firefox, the error messages and symptoms varies between browsers, and sometimes the user may be prevented from the webpage for security concerns.
To solve the issue for Hotspot Web Portal, we first need a certificate that is issued by a certificate authority such as Let's Encrypt and Comodo. Next, we need to import the certificate into the router. Here are two solutions.
This is a convenient and free service if you can apply a DrayDDNS domain name for your Vigor router. In firmware version 3.9.0, administrator can apply a domain name for the router with DrayDDNS and obtain a trusted certificate from the Certificate Authority (CA), Let's encrypt. Please visit the following link for the configuration. Visit here to learn how to Use Let's Encrypt Certificate for your DDNS Domain
You may select this option if you have a trusted certificate for your own domain name.
If you are unable to obtain and import a trusted certificate, the hotspot client will need to ignore the browser's warning messages about insecure certificates, and proceed to load the router's landing page.
>Generally, devices will pop-up the built-in browser to open the portal page, and that browser will not show a certificate error. However, if the device didn't open the browser automatically, and the user needs to open the webpage manually, the browser may display a warning message like the image below. The hotspot user just needs to click Show detail, then click Visit the website to proceed to the login page.
Published On: 2019-04-02
Was this helpful?
Thank you for your feedback :)
Sorry about that. Contact Support if you need further assistance, or leave us some comments below to help us improve.