Skip to content

Accessing our site after installing the load balancer

0

We have now this secure link (after installing the load balancer to support a certificate). We set all the ports properly to the best of our knowledge. Our URL is: https://ec2-load-balancer-1740072273.us-west-1.elb.amazonaws.com:443 We attempt to reach it via our site hacknot.net using the page: https://www.hacknot.net/secured-cloud-services/ The link showed when attempted does not include the 443 - ec2-load-balancer-1740072273.us-west-1.elb.amazonaws.com (and the HTTPS does not appear as part of the link. Why can't we access the secured link? Could you help in setting it up? Thanks for your help on this one!

2 Answers
0

https by default uses 443 and I can confirm https://www.hacknot.net/secured-cloud-services/ is using port 443

EXPERT

answered 2 years ago

  • I need to access the site, and this does not happen - first it is not secured and when I use the "advance" option to get to unsafe sites I get this: "503 Service Temporarily Unavailable". So, your confirmation of the 443 is GOOD but not solving the issue that the certificate is not recognized, and the access is not made - could you elaborate on this?

0

There are a few potential reasons why you might be having trouble accessing your secured link:

  1. Port specification: Generally, you don't need to specify port 443 in the URL for HTTPS connections, as this is the default port for HTTPS. Try accessing the URL without the port specification: https://ec2-load-balancer-1740072273.us-west-1.elb.amazonaws.com

  2. SSL/TLS configuration: Ensure that your load balancer is properly configured with the SSL/TLS certificate. Check that you have added an HTTPS listener to your load balancer and that it's using the correct certificate.

  3. Security groups and network ACLs: Verify that the security groups associated with your load balancer and EC2 instances allow incoming traffic on port 443 (HTTPS).

  4. Target group health: Check that your target group has healthy instances. If no instances are healthy, the load balancer won't be able to route traffic.

  5. DNS propagation: If you recently set up the load balancer or changed its configuration, it may take some time for DNS changes to propagate.

To properly set up the secured link:

  1. Open the Amazon EC2 console and navigate to the Load Balancers section.
  2. Select your load balancer and go to the "Listeners" tab.
  3. Ensure you have an HTTPS listener on port 443.
  4. Verify that the SSL certificate is correctly attached to this listener.
  5. Check that the security policy for the HTTPS listener is appropriate for your needs.
  6. Confirm that your target group has healthy instances.

If you're still unable to access the secured link after checking these items, you may need to review your application code to ensure it's correctly handling HTTPS requests and not inadvertently stripping the protocol from the URL.
Sources
Application Load Balancer | Elastic Load Balancing | Amazon Web Services
Update an HTTPS listener for your Application Load Balancer - Elastic Load Balancing
Configure an HTTPS listener for your Classic Load Balancer - Elastic Load Balancing

answered 2 years ago

EXPERT

reviewed 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.