Adding already existing VMs to a load balancer for HTTPS

[adrianyong]

Hi I set up some Virtual Machines in the compute engine, but now I need to set up HTTPS for them. I followed this tutorial

https://cloud.google.com/load-balancing/docs/https/setup-global-ext-https-compute

This setups two new VMs in a VM group as my load balancer but they're complete separated from my previous VMs. Do you have to take those previous VMs and add them to a VM group?

In addition, my Google Managed Classic Certificate has been stuck at FAILED_NOT_VISIBLE despite adding the A record to my DNS zone that was provided from the LB, but even after 24 hours it is not provisioning

Thanks

[VannGuce · Accepted solution]

Hi,

Regarding your concern that adding your existing VM instance to your Manage Instance group is not possible, all we can do is add another VM instance by editing the Manage Instance group and add Minimum number of instances to create another one.

However, if you do not need the feature of Manage Instance group (stateless) there is another way to create HTTPs load balancer that will connect to your existing instance as backend service. You can follow the steps below.

1. Go to instance group and click “New Unmanaged instance group”
2. Create any name, make sure the location is also the same location with your existing instance.
3. Network should be the same network with your existing vm instance
4. On “select VMs” choose your existing VM instance. VM instance will not appear if location is different.
5. Click create.

From the steps above, what we are going to use is an Unmanaged instance group so you can use your existing instance. Next is by creating a https load balancer. You will just follow the instruction on creating an https load balancer and from the backend configuration there is an option “instance group” just choose the unmanaged instance group that you created.

With regards to the managed certificate, I suggest configuring the setup that I suggest and wait for the DNS propagation. One troubleshooting step that you can do to check if the website is reachable is by accessing it using the external ip address of your website. Once it is accessible, double check your DNS configuration, especially the A record.