This article provides information related to the error "NET::ERR_CERT_INVALID - Your connection is not private" which you see on Google Chrome while accessing J-web.

Additionally, there is no option to accept the risk and continue to the webpage.

The below error page will be displayed when J-web is accessed.



Please refer to KB94938 [juniper.net] (https://supportportal.juniper.net/s/article/JWEB-NET-ERR-CERT-INVALID-Your-connection-is-not-private) for the details on why this error will be seen and it's workaround.

As seen, this is more of a browser feature, which does not allow access to webpages with invalid certificates.

However, browsers do provide an option to "Accept the risk and continue" for other firewall vendors except for Juniper when a self-signed certificate is used.

On SRX, when we use "set system services web-management https system-generated-certificate", the certificate that SRX provides will have many parameters missing.

Hence, the recent versions of the browsers will not provide a link to accept the risk and continue.

This needs a self-signed certificate generated locally and then used the same for "set system services web-management https pki-local-certificate <certificate-id>".

When generating this certificate, we will provide basic parameters such as CN, domain name, IP and key pair. Hence, a complete proper certificate will be generated.

When this certificate is used, the browsers will give us a link to accept the link and continue to the webpage.

Reference:

https://supportportal.juniper.net/s/article/Junos-How-to-create-a-custom-self-signed-certificate-for-web-management-using-HTTPS?language=en_US