I've created a compute VM, then went though the steps 2 days ago to attached my Google purchased Domain, added Load Balancer, Instance Group, and SSL. I followed these instructions. The Status of Domain is Failed not Visible. Anyone have any tips/tricks on what could have went wrong?
Related
I have a running Web server on Google Cloud. It's a Debian VM serving a few sites with low-ish traffic, but I don't like Cloudflare. So, Cloud CDN it is.
I created a load balancer with static IP.
I do all the items from the guides I've found. But when it comes time to Add origin to Cloud CDN, no load balancer is available because it's "unhealthy", as seen by rolling over the yellow triangle in the LB status page: "1 backend service is unhealthy".
At this point, the only option is to choose Create a Load Balancer.
I've created several load balancers with different attributes, thinking that might be it, but no luck. They all get the "1 backend service is unhealthy" tag, and thus are unavailable.
---Edit below---
During LB creation, I don't see anywhere that causes the LB to know about the VM, except in cert issue (see below). Nowhere does it ask for any field that would point to the VM.
I created another LB just now, and here are those settings. It finishes, then it's marked unhealthy.
Type
HTTP(S) Load Balancing
Internet facing or internal only?
From Internet to my VMs
(my VM is not listed in backend services, so I create one... is this the problem?)
Create backend service
Backend type: Instanced group
Port numbers: 80,443
Enable Cloud CDN: checked
Health check: create new: https, check /
Simple host and path rule: checked
New Frontend IP and port
Protocol: HTTPS
IP: v4, static reserved and issued
Port: 443
Certificate: Create New: Create Google-managed certificate, mydomain.com and www.mydomain.com
Load balancer's unhealthy state could mean that your LB's healthcheck probe is unable to reach your backend service(Your Debian VM in this case).
If your backend service looks good now, I think there is a problem with your firewall configuration.
Check your firewall rules whether it allows healthcheck probe's IP address range or not.
Refer to the docoment below to get more detailed information.
Required firewall rule
I have configured app load balancer on amazon. Set up DNS LB to route 53 with alias for A. Behind LB i have 2 instances with IIS. If i set up 2 sites on both instances, balancer automatically balance client by rotation
(as i know round robin). But, if i turn off site on IIS in one instance, load balancer continue go to that instance and if i go to exapmle.com i will have one time worked site and if refresh the page i will have error (because site turned off in IIS). Could you please tell me, how can i set up load balance to route traffic in working instance if one of them not working. Thank you
Load balancers continue to distribute the traffic on healthy servers. If it is not happening in your case, I would recheck the health check configuration under Target Groups.
You need to modify the port/path so that health checks start failing once the site is turned off. Only then, the load balancer will pass all traffic to healthy host, not the unhealthy host
What does the LB health checks say? If the back-end instances are not listening on the health check port then LB marks it as unhealthy and stops forwarding requests to it. If you are using Application loadbalancer then I think you can get the health check status within the target groups associated with the loadbalancer.
I have an AWS elastic load balancer connected to between 1 and 3 EC2 instances, which are connected to a single RDS database via phpMyAdmin.
When logging into phpMyAdmin, I can successfully log in and access the database when I have only ONE EC2 instance active. However when I have 2 or more, the phpMyAdmin login page simply stays when logging in. It does however return proper errors for incorrect info, but displays no extra info for accurate credentials.
This is bugging me to death! Please help!
This is happening because your load balancer is using a Round Robin algorithm to balance the traffic on the EC2 instances. Enable Session based Algorithm on your ELB and this issue will be resolved.
Check this Guide http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-sticky-sessions.html#enable-sticky-sessions-duration
Followed the entire tutorial at http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-create-as.html and the problem I am having is with the load balancer.
According to the Instances page and the Auto Scaling Groups page, the two instances I am running are InService and Healthy.
On the Load Balancers page under the Instances tab for the load balancer, it lists each instance as OutOfService and each Availability Zone's Health status as "No (Availability Zone contains no healthy instances)".
The part that is most confusing to me (and I believe to be the main issue) is that when I visit one of the instance's at its public dns ec2-server-name.us-west-2.compute.amazonaws.com, it displays the default "Amazon Linux AMI Test Page" but the headers of the page return 403.
So I imagine the issue is that the load balancer is running its health check and seeing that the instance's returned status code is 403. Why is it returning a 403 error code though? When I load the instance in browser I can see the page and everything seems to work, but when I visit the load balancer all I get is a blank white page.
Discovered the issue. Amazon's default "Amazon Linux AMI Test Page" returns a 403 error by default. Once new files are uploaded to /var/www/html and replace the default page, the problem goes away.
Hello I am i doing a proof of concept with AWS's EC2 and Loadbalancer. I have a wildfly quickstart running on 2 different EC2 instances. They work fine, in that i can go to them directly in my browser and get the sites to come up. One says hello server 1 and the other 2. Running on port 8080.
I have a load balancer set up and it sees my instances and the healthcheck i have in place says they're working.
The configuration is: 80 (HTTP) forwarding to 8080 (HTTP)
When i go to the dns entry + health check path (HTTP:80/wildfly-helloworld/HelloWorld) for the load balancer in my browser it times out.
The bizarre thing again is that it shows my instances as "In Service" and healthy.
Also security on the load balancer is allows ALL inbound and outbound traffic.
Any suggestions?
Thanks
Answer found here:
https://forums.aws.amazon.com/message.jspa?messageID=579018#579018
In short the security on the load balancers were off.