When you try to access the Emulator over the Secure Socket Layer (SSL) protocol, it has to identify itself with a SSL certificate to the web browser.
In order for web browsers to trust the certificate that the server has presented, the SSL certificate must be issued by a valid certificate authority.
The default Eggplant Network SSL certificate is a self-signed one, essentially meaning that it has not been issued by a certificate authority, but instead Eggplant has signed the certificate as being valid.
This works perfectly fine for encrypting data, but it presents you with an error or warning in your web browser when trying to access the secure content. Below are examples of this from common browsers:
Click Advanced, then Proceed to 192.168.202.194 (unsafe) to bypass SSL warnings in Chrome.
Click I Understand the Risks, then click Add Exception.
Next, click Get Certificate, then click Confirm Security Exception to bypass SSL warnings in Firefox.
Click Continue to this webpage (not recommended) to bypass SSL warnings in Edge.
The above warnings let you know that the SSL certificate was self-signed. In the case of accessing Eggplant, this isn't a problem, and you can tell your browser to accept the self-signed SSL certificate and continue.
You would typically use caution on these types of errors if you were accessing your bank or an ecommerce website, as it could be an indication that your secure data isn't going to the right server.