Sign in
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Your connection is not private

  • By Venkat
  • on 07/20/2020

I setup an instance with this AMI. Installation is pretty straight-forward. But I am not able to access the admin page. Browsers are blocking it with this error "Your connection is not private". I can't bypass this. Going to shutdown the instance.


  • By francisco
  • on 06/10/2021

You need to configure an SSL certificate

  • By john
  • on 05/25/2021

I am also getting this error message on Chrome and cannot get past it. However it works with Firefox and Safari (I get warning messages but I can proceed past them) - so I presume the issue is Chrome-specific ?

  • By AdminDogg
  • on 12/14/2020

If you do a quick search for OpenVPN and LetsEncrypt, you'll see a few guides on how to install the Certbot agent and to issue certs to your OpenVPN box, plug those into the OpenVPN config, and set up autorenew.

  • By Patrick
  • on 10/01/2020

Use Google Chrome. Or check your browser settings to enable this.

  • By Gleb
  • on 08/24/2020

Hello, I'm also getting this issue. There is no option to go to 'Advanced Setting' then 'Proceed'. Full error message: Your connection is not private Attackers might be trying to steal your information from xxx.xxx.xxx.xxx (for example, passwords, messages, or credit cards). Learn more NET::ERR_CERT_INVALID Help improve Chrome security by sending URLs of some pages you visit, limited system information, and some page content to Google. Privacy policy xxx.xxx.xxx.xxx normally uses encryption to protect your information. When Google Chrome tried to connect to xxx.xxx.xxx.xxx this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be xxx.xxx.xxx.xxx, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged. You cannot visit xxx.xxx.xxx.xxx right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.

  • By Patrick
  • on 07/31/2020

Click on Advanced Setting and then click on Proceed.