I am new to AWS EC2, i had just setup an ec2 with whm cpanel, my public dns ip is not working without https, its showing 404 not found, but with https its working fine with a non secure red badge in the url. I would like to use ec2 public dns without HTTPS.
It would be a problem with the security groups associated with your EC2 instances.
While you may have setting to allow traffic on port 443 which is https, port 80 might be missing from your whitelisted ports
To allow traffic on port 80 and 443, you must configure the associated security group and network access control list (network ACL).
For more details check this link
Related
Getting Error 522 or 521, when accessing 80 or 443 port from ALB link its working (for 443 browser shows warning i.e because ALB and SSL domain is different)
AWS Config.
Created Custom VPC with 1 public subnet and 1 private subnet
Created AutoScaling Group
Created Load Balancer (two listener for http and https forwording to traget group ) and target group (two targets pointing to Ec2 Instance on port 80 and 443 for heathcheck) -> health check is passing.
Launched Ec2 instance in private subnet (no public ip), instance can only be access by application load balancer security group.
Ec2 and Apache2 Config.
Enabled SSL in apache2
Open port 443 in instance, Security Group of ALB and access port 80 (http) and 443 (https)
For SSL followed article https://www.digitalocean.com/community/tutorials/how-to-create-a-self-signed-ssl-certificate-for-apache-in-ubuntu-18-04
Generated SSL Certificate from CloudFlare
SSL/TLS -> Origin Server -> Generated RSA certificate
Imported SSL certificate to AWS ACM
Attached ACM SSL certificate to Loadbalancer HTTPS Listener
Also create AWS ACM SSL certificate and validated with DNS for testing tried both ssl certificate - didn't worked
Subdomain and ALB link
Created DNS CNAME entry in CloudFlare
Added subdomain which pointing to ALB link. (tried with proxy and DNS only)
Your SSL/TLS encryption mode is Full
Always Use HTTPS: ON
When hitting subdomain in normal window (browser) its getting 522 and in incognito mode for the first time it is working but after that not.
When making curl request to https://subdomain.domain.com always working
Created extact duplicate instance in Public subnet and linked with another subdomain (created in cloudflare) just for testing -> working properly.
Also tried by adding separate target group for port 443 (HTTPS) -> in this traget group health check is getting failed whereas same working in other target group which for port 80 (http)
I'm not getting how to resolve this issue, please help!
Thank you.
Please Help!
Issue was because of internet facing loadbalancer was available in public and private subnet, and because of private subnet cloudflare was not able to connect to ec2 instance which was in private subnet.
Loadbalancer subnet section was showing You are creating an internet-facing Load Balancer, but there is no Internet Gateway attached to these subnets you have selected warning.
Solution: https://aws.amazon.com/premiumsupport/knowledge-center/public-load-balancer-private-ec2/
I setup an ELB to accept http/https traffic with a security group to allow all http/https traffic. Instead of pointing the domain to the EC2 IP, it is instead pointed at the alias of the ELB.
The EC2 is setup to accept http/https from any location at the moment, amongst ssh from my computer.
The target group is setup to forward traffic via https to the instances, and health check is performed via http. The targets show as healthy. In addition, the DNS for the ELB, and the website, throws a 502 error, and is unsecure accessible via https.
When I configure the target group to forward traffic via http to the instances, and the health check is performed via http, the targets still show as healthy. The ELB DNS / website is accessible for the ELB, though https still throws an unsecure warning.
Port 443 shows as closed. I have apache setup to listen to both port 80 and port 443 in order to serve the website. Normally, I would have the certificates on the server and would route port 80 to port 443 to serve them, so that's why they're both enabled.
I have an application running on an AWS EC2 instance with the domain's nameservers on AWS as well. I have an A record with the public IP.
I've create a secure certificate with ACM and also created an ELB Load Balancer. My domain still doesn't show the HTTPS in front of it.
Can anyone provide some help? Many thanks
Have you tried this ?
First, you need to open HTTPS port (443). To do that, you go to https://console.aws.amazon.com/ec2/ and click on the Security Groups link on the left, then create a new security group with also HTTPS available. Then, just update the security group of a running instance or create a new instance using that group.
After these steps, your EC2 work is finished, and it's all an application problem.
Credit to : https://stackoverflow.com/a/6253484/8131036
The solution is pretty simple.
First of all, edit the listeners on your ELB and do the following:
443 (HTTPS) => 80 (HTTP) - and apply ACM certificate.
What this essentially is doing is tells the ELB to listen on port 443 (HTTPS) and terminate the certificate and then forward traffic internally over port 80 (HTTP) - the port the instance is listening on.
You can also add port 80 (HTTP) and forward to port 80 (HTTP) (recommended and then set up your application to redirect all users to HTTPS). You can read more about ELB and setting up listeners here Create a Classic Load Balancer with an HTTPS Listener
Second thing you need to do is update Route 53 to point to ELB.
ascisolutions.com. A ALIAS s3-website-us-west-2.amazonaws.com. You can read more about it here Routing Traffic to an ELB Load Balancer
Let me know if you have more questions in the comments section and I'll do my best to reply.
You cannot install an ACM certificate on an ec2 instance directly, but you can install it on your load balancer and have the load balancer terminate SSL.
Create a target group and register your ec2 instances using port 80.
In your ELB, setup listeners for both port 80 and 443. You'll need to add your ACM cert to your https listener (port 443). Note that the certificate needs to be issued in the same region as your ELB.
The ELB does not handle redirecting insecure traffic to HTTPS, if needed, you will need to update your application to redirect http to https.
I can browse to the web site with http but cannot with https, I get ERR_CONNECTION_REFUSED in Chrome.
My environment is an expressJS server on nodejs (64bit Amazon Linux 2015.09 v2.0) running on Elastic Beanstalk. I can telnet to the EC2 elastic public IP on port 80 but I cannot telnet on port 443, connection refused.
Steps taken to set up HTTPS
I created an SSL cert via the AWS Certificate Manager and added the cert to the Load Balancer Listeners.
Port Configuration:
80 (HTTP) forwarding to 80 (HTTP)
Stickiness: Disabled(Edit)
443 (HTTPS, ACM Certificate: 1E21...) forwarding to 80 (HTTP)
Stickiness: Disabled
In the Load Balancer Security Group, I added inbound and outbound https traffic on port 443 Source 0.0.0.0/0.
In my EC2 Elastic I.P, I selected my ExpressJS server instance and then added inbound and outbound https traffic on port 443 Source 0.0.0.0/0.
In addition, I also added the Load Balancer Security Group to my ExpressJS server security because I read in another post that you had to associate the load balancer group with the server instance (not sure that this is required).
Any suggestions?
btw, does HTTPS traffic terminate at the Load Balancer and then unencrypted and handled internally on port 80 to the server?
Solved it, turned out the mistake I made was that I added a record on my monster DNS for my AWS site and pointed it to the AWS Public Elastic IP as a A record, instead, I should have added the CNAME of my Load Balancer to the Monster DNS, once I did that, HTTPS was working.
I also ditched the Public Elastic IP as it was not required anymore, also, having the public I.P prevented me from taking advantage of the load balancer. Hope this helps other people.
My app was easy deployed on 3 instances using OpsWorks. I can Access it using instance IP's fine.
My question is: how can I access it using load balancer?
ELB says all 3 instances are InService, but typing public DNS on browser, it loads forever and shows nothing.
Testing ELB public DNS on http://whatsmydns.com it shows IP's that aren't from my instances.
Am I doing something wrong?
I have added Public DNS to my app as hostname.
There are a couple things to check:
Check that your load balancer listeners are configured to listen
and pass traffic to the same port that the instance is listening on
(for example http traffic 80 => http 80, https traffic 443 => https
443)
Check that the security group of the webservers allows
traffic from the loadbalancer. Though if you can access your instances directly via browser, I'm guessing they are open to 0.0.0.0/0 so shouldn't be an issue here?
Check that security group of the load balancer allows access to public on all needed ports (typically 80 and 443)
Check that elb healthcheck is not failing (under elb
instances you can see if the instances are in service or not) If it
says "Out of service" that's the problem. You need to make sure that
healthcheck URL is accessible and returns 200.
The DNS of your load balancer is different from your instances - it returns the IP addresses of the instances that the load balancer is running on, AWS usually has at least 3 servers behind the scenes for that.