How to fix the 'connection not private' error when accessing a website through an A

I configured an https://www.janbasktraining.com/blog/aws-elastic-load-balancer/ with a pre-configured SSL certificate. It listens for HTTPS traffic on port 443 but terminates it and forwards regular HTTP traffic on port 80 (apparently there’s no option to enable HTTPS on the load balancer itself).

When I access my actual website, everything works fine and shows a secure connection (HTTPS with the green lock). However, when I directly access the load balancer address (like https://load-balancer-xxxxxx.us-east-7.elb.amazonaws.com/index.html), my browser warns me about an “unsecured connection.”

I’m wondering if this warning means my actual website traffic (HTTPS) is still secure? Could the error be because the load balancer’s certificate doesn’t match my domain name?

Should I consider using a wildcard certificate that covers both my domain (e.g., domain.com) and the AWS load balancer address (*.amazonaws.com) to resolve this warning?

This version clarifies the technical details while maintaining readability. It removes unnecessary conversational phrases and focuses on the problem and potential solution.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.