Load Balancing creation failed on Google Cloud - stuck spinning

I’m trying to set up a Google Cloud Load Balancer with an SSL certificate for a WordPress VM. After an initial failed attempt and deleting resources (including the VPC network), I’am facing two main problems:

  1. Stuck Instance Group Deletion: An instance group from your first attempt is stuck in a spinning state with an error, preventing cleanup.

  2. Failed Load Balancer Creation: my second attempt to create a load balancer for a new WordPress VM has failed to complete after over an hour, and I cannot stop or delete it. However, an HTTP-to-HTTPS redirect load balancer did complete successfully.

I need to find a way to resolve these stuck resources before trying to set up the main load balancer again.

Thank you

Hi @G00GL3DEV,

You can check on the cloud console notification what type of error that prevents you from deleting the instance group. You cannot delete an instance group if it is being used by a load balancer’s backend service. Remove the backend service before deleting the instance group. Also, When you delete a managed instance group, all VMs in the group are deleted. If you want to keep any of the VMs, abandon the VMs first to remove those VMs from the group. Then, delete the managed instance group. You can also check this document for deleting Managed Instance Group.

There are several reasons or issues that prevent you from creating a new load balancer. Here are some common causes:

  1. Roles and Permission : make sure you have necessary permission to create and manage load balancers.
  2. Configuration errors: make sure that your backend service is properly configured and contains healthy instances. Also make sure your frontend has a correct and active SSL certificates.
  3. Quotas and Limits: Check if you have reached any quotas for the number of load balancers, backend services, or other related resources in your project or region.

Troubleshooting:

  • Review Error Messages: check any error messages displayed in the Google Cloud Console or when using gcloud commands, as they often provide specific clues.
  • Check Cloud Logging: for detailed logs related to load balancer creation attempts, which can offer more in-depth insights into the failure.
  • Use gcloud Commands: Try creating the load balancer using gcloud commands instead of the console. This method can sometimes help bypass browser-related issues and offer more precise error messages.

Refer to the official Google Cloud documentation for the specific type of load balancer you are trying to create for detailed setup instructions and troubleshooting guides.