Google Load Balancer creating frontend IP that differs from Compute Engine IP

Question

I have a single compute engine that I am trying to make accessible by HTTPS. I assigned it to a instance Group and added a port name that mapped to 443. Then I created an HTTP(S) load balancer who's backend service connected to the instance and the port that I had set in the instance group. However, the IP address that the load balancer creates for the front end service is different to the external IP address of the instance.

So my question is, when I contact the frontend service IP address, will that route to the port 443 of the instance's IP address or is it expecting the external IP address of the instance to be the same as the fronend IP address of the load balancer.

Currently, my backend service is unhealthy, and I am suspecting this to be the probable reason. If not, are there any other steps I have to take to make my instance's IP address accessible via HTTPS other than setting a mapped port creating a load balancer with a backend service connected to that isntance and port?

Answer 1

The load balancer should route to your compute engine instance(s) if you configured it properly, so first thing to check is your routing configuration. As a matter of fact, I would actually remove the static external IP address of the CE instance.

Also check your load balancing logs(explained here) to see any errors.