NET::ERR_CERT_INVALID {bypass that error}

[rugby]

I am attempting to log on to the web interface of a local device on my own private network. I am receiving the referenced error message. Others browsers allow the ability to bypass this error message, by allowing an exception. Does Vivaldi provide the ability to do this?

thanks,

[angelo.mascaro]

@gwen-dragon
Dear gwen-dragon, sometimes the button "continue anyway" is a good idea. We live in a relative world, not in an absolute one. Just an example: My NAS (a QNAP TS-451) has a certificate and I use it to access to my NAS with the address https:/.myqnapcloud.com when I'm out of office. When I'm in office the address is either https://.local or https://192.168.1.69 and the only way to get access to my NAS is http because I cannot say continue anyway!

NET::ERR_CERT_COMMON_NAME_INVALID

[becm]

@angelo-mascaro the full domain name should be usable in the office as well and just require a trip through the office router (with NAT step).
If this does not work, the firewall/network settings at your office are broken suboptimal.

Temporary workarround would be to assign a (fixed) DNS entry in your local (office) resolver for the specific <yourdevice>.myqnapcloud.com to the appropriate LAN address.
Then the FQDN is valid there as well (until DNSSEC is rolled out).

Otherwhise you will allways get a name mismatch, unless you include all local domains (and IP adresses) into the (public facing) certificate.
Or the QNAP appliance is sophisicated enough to allow different cert setups for LAN and WAN sources.

[Brean]

According to the page JS code, the new bypass-word is now thisisunsafe. I tried badidea as well as danger (suggested on Chrome related forums) but it didn't work.

(I hesitated to bring back a 2 year-old topic, however it's the only one that deals with that particular problem)