HTTPS load balancer in Google Container Engine

Question

HTTPS load balancer in Google Container Engine

24.2k views Asked by lucas.coelho At 24 August 2015 at 17:36

I'm trying to set up an HTTPS load balancer for GKE using HTTPS L7 load balancer but for some reason is not working. Even the HTTP load balancer in the HTTP Load Balancing walkthrough. The forwarding rule's IP address is created and I'm able to ping and telnet to port 80. But when request via curl it give me a error.

<title>502 Server Error</title> </head> <body text=#000000 
bgcolor=#ffffff> <h1>Error: Server Error</h1> <h2>The server 
encountered a temporary error and could not complete your request. 
<p>Please try again in 30 seconds.</h2> <h2></h2> </body></html>

All the steps were fine and I created a firewall without any tags for the ${NODE_PORT} but it didn't work.

Has anyone encountered this problem?

Original Q&A

There are 8 answers

Chris Stryczynski On 27 September 2017 at 14:54

The issue resolved after a few minutes (like 5-10 minutes) in my case.

If using an ingress, there may be additional information in the events relating to the ingress. To view these:

kubectl describe ingress example

Bruce On 23 February 2017 at 09:39

I use GKE, and I just walked through the example and it works fine, but when I route to my own service, it does not work. (my service is a rest api service)

I found that the biggest difference between my service and the example, is that: the example got a root endpoint("/"), but I do not support it.

So, I solved this problem in this way: add a root endpoint("/") to my service, and just return success(an empty endpoint that returns nothing), and then re-create the ingress, and waited for several minutes, and then the ingress works!!

I think this problem should be caused by healthy checker UNHEALTHY instances do not receive new connections.

Here is a link for Healthy checks: https://cloud.google.com/compute/docs/load-balancing/health-checks

Robert Bailey On 24 August 2015 at 23:20

I just walked through the example and (prior to opening up a firewall for $NODE_PORT) saw the same 502 error.

If you look in the cloud console at

https://console.developers.google.com/project/<project>/loadbalancing/http/backendServices/details/web-map-backend-service

you should see that the backend shows 0 out of ${num_nodes_in_cluster} as healthy.

For your firewall definition, make sure that you set the source filter to 130.211.0.0/22 to allow traffic from the the load balancing service and set the allowed protocols and ports to tcp:$NODE_PORT.

user3637413 On 18 February 2020 at 16:27

Adding a Firewall Rule for Source: 130.211.0.0/22(the Load Balancer range on GCP) for the tcp:$NODEPORTIP fixed this for me.

Pulkit Pahwa On 24 July 2018 at 06:27

In my case, the load balancer was returning this error because there was no web server running on my instances and instance-groups to handle the network request.

I installed nginx on all the machines and then it started working.

From now on, I made a point to add nginx in my startup script while creating the vm/instance.

sandes On 16 January 2020 at 20:01

I created an endpoint to all request that contain 'GoogleHC' in the user-agent.

so,

server{
    server_name example.com www.example.com

    if ($http_user_agent ~* 'GoogleHC.*') {
        return 200 'isaac newton';
    }
}

Christoffer On 20 June 2019 at 13:22

If you are using nginx behind your loadbalancer then it's important that the default_server is returning 200 or some other 2**. That means that if you for example have a rewrite rule that returns 301 then it will fail.

The solution is to set default_server on your main server:

server {
    # Rewrite calls to www
    listen 443;
    server_name example.com;

    return 301 https://www.example.com$request_uri;
}


server {
    listen                  443 default_server;
    server_name             www.example.com;
    ...

**andresk** · Accepted Answer · 2016-09-09 18:59:21

I had the same problem with my application, the problem is that we did not have an endpoint returning "Success" and the health checks were always failing.

It seems that the HTTP/HTTPS load balancer will not send the request to the cluster nodes if the health checks are not passing, so my solution was to create an endpoint that always returns 200 OK, and as soon as the health checks were passing, the LB started working.

TechQA.

HTTPS load balancer in Google Container Engine

There are 8 answers

Related Questions in GOOGLE-COMPUTE-ENGINE

Related Questions in GOOGLE-KUBERNETES-ENGINE

Related Questions in GOOGLE-CLOUD-HTTP-LOAD-BALANCER

Popular Questions

Popular Tags

Trending Questions