Forum Discussion
Lee_Sutcliffe
Feb 05, 2018Nacreous
If you request https://202.2.2.2, the CN that you request in the HTTPS request (202.2.2.2) does not match that of the public SSL certificate. The browser will not do a reverse lookup, thus resulting in a certificate errot. As far as the browser is concerned, it has done it's job and got a response from the URL that you requested.
Is there any reason your clients are making the request based on IP address and not an FQDN?