{"id":17344,"date":"2026-06-05T10:00:00","date_gmt":"2026-06-05T16:00:00","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=17344"},"modified":"2026-06-04T23:17:56","modified_gmt":"2026-06-05T05:17:56","slug":"common-google-cloud-load-balancer-health-check-failures-and-how-to-fix-them","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/common-google-cloud-load-balancer-health-check-failures-and-how-to-fix-them\/","title":{"rendered":"Common Google Cloud Load Balancer Health Check Failures and How to Fix Them"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">When an application suddenly becomes unreachable in Google Cloud, one of the most common causes is a failed load balancer health check. Even when servers appear to be running normally, a health check failure can cause Google Cloud Load Balancers to stop routing traffic to backend instances, resulting in downtime, error messages, and poor user experience.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Understanding why health checks fail and knowing how to troubleshoot them quickly can significantly reduce downtime and improve application availability.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we&#8217;ll explore the most common causes of Google Cloud Load Balancer health check failures, how to diagnose them, and the Linux commands that can help identify issues efficiently.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Are Google Cloud Health Checks?<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google Cloud health checks are monitoring probes used by load balancers to determine whether backend instances or services are healthy enough to receive traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Health checks verify several factors, including:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Server availability<\/li>\n\n\n\n<li>Application responsiveness<\/li>\n\n\n\n<li>Open and accessible ports<\/li>\n\n\n\n<li>HTTP\/HTTPS response status codes<\/li>\n\n\n\n<li>TCP connectivity<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If a backend repeatedly fails health checks, Google Cloud automatically removes it from traffic rotation until it becomes healthy again.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Common Symptoms of Health Check Failures<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You may be experiencing a health check issue if you notice any of the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Website or application becomes inaccessible<\/li>\n\n\n\n<li>Frequent 502 or 503 errors<\/li>\n\n\n\n<li>Backend instances marked as unhealthy<\/li>\n\n\n\n<li>Uneven traffic distribution<\/li>\n\n\n\n<li>Sudden drop in incoming requests<\/li>\n\n\n\n<li>Auto-scaling behaving unexpectedly<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Common Causes of Google Cloud Health Check Failures<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Firewall Rules Blocking Health Check Traffic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most common causes of health check failures is firewall rules blocking Google&#8217;s health check IP ranges.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google Cloud health checks typically originate from:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>35.191.0.0\/16<\/li>\n\n\n\n<li>130.211.0.0\/22<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If these IP ranges cannot access your backend service, health checks will fail even when the application is functioning properly.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Create a Firewall Rule<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>gcloud compute firewall-rules create allow-health-checks \\\n--network default \\\n--allow tcp:80,tcp:443 \\\n--source-ranges 35.191.0.0\/16,130.211.0.0\/22<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Always verify that required ports are accessible from Google Cloud health check sources.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Application Not Listening on the Correct Port<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Health checks must target the same port on which your application is actively listening.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Backend service configured on port 80<\/li>\n\n\n\n<li>Application running on port 8080<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This mismatch causes health checks to fail.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Check Listening Ports<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo netstat -tulnp<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">or<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ss -tulnp<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verify that the configured health check port matches the application&#8217;s listening port.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Web Server or Application Service Is Down<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the <a href=\"https:\/\/www.supportpro.com\/blog\/why-cloud-servers-still-go-down-common-operational-mistakes\/\" title=\"\">backend application or web server has stopped<\/a> or crashed, health checks will immediately fail.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Check Service Status<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">For NGINX:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status nginx<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For Apache:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status httpd<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For custom services:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status your-service-name<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Restart the Service<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl restart nginx<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Always review service logs to identify the root cause of service failures.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Incorrect Health Check Path<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">HTTP and HTTPS health checks typically expect a successful <strong>200 OK<\/strong> response.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the configured health check path returns:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>404 Not Found<\/li>\n\n\n\n<li>403 Forbidden<\/li>\n\n\n\n<li>500 Internal Server Error<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">the backend will be marked unhealthy.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Test the Health Check Endpoint<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -I http:\/\/localhost\/health<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">or<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -I http:\/\/localhost<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A healthy response should return:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>HTTP\/1.1 200 OK<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If errors occur, update either the application endpoint or the Google Cloud health check configuration.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. High CPU, Memory, or Disk Utilization<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Overloaded servers often respond slowly to health check requests, causing timeout failures.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Check CPU and Memory Usage<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>top<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">or<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>htop<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Check Disk Usage<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>df -h<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Check Memory Usage<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>free -m<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If resource utilization is consistently high, consider scaling resources or optimizing application performance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. Slow Backend Startup Time<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Applications that require significant initialization time may fail health checks immediately after startup.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This commonly occurs in:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Managed Instance Groups (MIGs)<\/li>\n\n\n\n<li>Auto-scaling environments<\/li>\n\n\n\n<li>Kubernetes workloads<\/li>\n\n\n\n<li>Large application deployments<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Check Startup Logs<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>journalctl -xe<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">or<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo journalctl -u nginx<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Consider increasing health check timeout values during startup if necessary.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7. Incorrect Health Check Configuration<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Even a healthy application can fail health checks due to configuration mistakes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Common issues include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incorrect protocol selection<\/li>\n\n\n\n<li>Wrong port number<\/li>\n\n\n\n<li>Invalid request path<\/li>\n\n\n\n<li>Timeout values that are too short<\/li>\n\n\n\n<li>Improper healthy or unhealthy thresholds<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">View Existing Health Checks<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>gcloud compute health-checks list<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Describe a Health Check<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>gcloud compute health-checks describe HEALTH_CHECK_NAME<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Port number<\/li>\n\n\n\n<li>Request path<\/li>\n\n\n\n<li>Check interval<\/li>\n\n\n\n<li>Timeout settings<\/li>\n\n\n\n<li>Healthy threshold<\/li>\n\n\n\n<li>Unhealthy threshold<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8. SSL or HTTPS Certificate Issues<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">HTTPS health checks may fail due to SSL-related problems such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Expired certificates<\/li>\n\n\n\n<li>TLS version mismatches<\/li>\n\n\n\n<li>Broken HTTPS redirects<\/li>\n\n\n\n<li>SSL handshake failures<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Verify SSL Certificate<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>openssl s_client -connect yourdomain.com:443<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Test HTTPS Endpoint<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -Iv https:\/\/yourdomain.com<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Look for certificate errors, expiration warnings, or handshake failures.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9. DNS Resolution Problems<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Applications that rely on DNS services may experience health check failures when domain resolution stops working correctly.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Verify DNS Resolution<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>nslookup yourdomain.com<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">or<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig yourdomain.com<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ensure all required domains resolve correctly and consistently.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10. Local Firewall or Security Software Blocking Traffic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Linux firewall tools such as iptables or firewalld may accidentally block health check traffic.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Check iptables Rules<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo iptables -L -n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Check firewalld Configuration<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo firewall-cmd --list-all<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verify that health check IP ranges and required ports are properly allowed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Useful Google Cloud Commands for Troubleshooting<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Check Backend Health<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>gcloud compute backend-services get-health BACKEND_SERVICE_NAME --global<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">List Backend Services<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>gcloud compute backend-services list<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">View Compute Instances<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>gcloud compute instances list<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Review Logs<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>gcloud logging read \"resource.type=gce_instance\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">These commands can quickly help determine whether the issue originates from networking, application configuration, or infrastructure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Best Practices to Prevent Health Check Failures<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Preventing health check failures is easier than troubleshooting them during an outage.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">-> Use Dedicated Health Check Endpoints<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Create lightweight endpoints specifically for health checks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">-> Avoid Complex Health Checks<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Minimize dependencies on databases or third-party services whenever possible.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">-> Monitor Infrastructure Proactively<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use monitoring tools such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Google Cloud Monitoring<\/li>\n\n\n\n<li>Prometheus<\/li>\n\n\n\n<li>Grafana<\/li>\n\n\n\n<li>Nagios<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">-> Enable Auto-Healing<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Configure health checks alongside auto-healing policies to automatically recover failed instances.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">-> Document Firewall and Network Rules<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Maintain clear documentation for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Allowed ports<\/li>\n\n\n\n<li>Firewall rules<\/li>\n\n\n\n<li>Health check IP ranges<\/li>\n\n\n\n<li>Backend configurations<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This significantly speeds up troubleshooting during incidents.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google Cloud Load Balancer health checks play a critical role in maintaining application availability and performance. When health checks fail, backend services can be removed from traffic rotation, leading to downtime and service disruptions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By understanding common failure causes such as firewall restrictions, incorrect ports, application crashes, SSL issues, resource bottlenecks, and configuration errors, administrators can quickly identify and resolve problems before they impact users.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Regular monitoring, proper health check configuration, and proactive infrastructure management are essential for maintaining a highly available and reliable Google Cloud environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Need Help Troubleshooting Google Cloud Infrastructure Issues?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.supportpro.com\/requestquote.php?opt=cloudsupport\" title=\"\">SupportPRO&#8217;s cloud engineers<\/a> provide expert Google Cloud support, load balancer troubleshooting, performance optimization, and 24\/7 infrastructure management. <a href=\"https:\/\/www.supportpro.com\/requestquote.php?opt=cloudsupport\" title=\"\">Contact us today<\/a> to keep your cloud applications running reliably and efficiently.<\/p>\n\n\n\n<div class=\"wp-block-media-text alignwide has-media-on-the-right is-stacked-on-mobile is-vertically-aligned-center has-white-background-color has-background\"><div class=\"wp-block-media-text__content\">\n<p class=\"has-large-font-size wp-block-paragraph\">Facing issues? <\/p>\n\n\n\n<p class=\"has-large-font-size wp-block-paragraph\">Our technical support<br>engineers can solve it. <\/p>\n\n\n\n<!--HubSpot Call-to-Action Code --><span class=\"hs-cta-wrapper\" id=\"hs-cta-wrapper-3350a795-db50-482f-9911-301930d1b1be\"><span class=\"hs-cta-node hs-cta-3350a795-db50-482f-9911-301930d1b1be\" id=\"hs-cta-3350a795-db50-482f-9911-301930d1b1be\"><!--[if lte IE 8]><div id=\"hs-cta-ie-element\"><\/div><![endif]--><a href=\"https:\/\/cta-redirect.hubspot.com\/cta\/redirect\/2725694\/3350a795-db50-482f-9911-301930d1b1be\" ><img decoding=\"async\" class=\"hs-cta-img\" id=\"hs-cta-img-3350a795-db50-482f-9911-301930d1b1be\" style=\"border-width:0px;\" src=\"https:\/\/no-cache.hubspot.com\/cta\/default\/2725694\/3350a795-db50-482f-9911-301930d1b1be.png\"  alt=\"Contact Us today!\"\/><\/a><\/span><script charset=\"utf-8\" src=\"https:\/\/js.hscta.net\/cta\/current.js\"><\/script><script type=\"text\/javascript\"> hbspt.cta.load(2725694, '3350a795-db50-482f-9911-301930d1b1be', {\"useNewLoader\":\"true\",\"region\":\"na1\"}); <\/script><\/span><!-- end HubSpot Call-to-Action Code -->\n<\/div><figure class=\"wp-block-media-text__media\"><img fetchpriority=\"high\" decoding=\"async\" width=\"904\" height=\"931\" src=\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup.png\" alt=\"guy server checkup\" class=\"wp-image-12943 size-full\" srcset=\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup.png 904w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-291x300.png 291w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-768x791.png 768w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-585x602.png 585w\" sizes=\"(max-width: 904px) 100vw, 904px\" \/><\/figure><\/div>\n","protected":false},"excerpt":{"rendered":"<p>When an application suddenly becomes unreachable in Google Cloud, one of the most common causes is a failed load balancer health check. Even when servers appear to be running normally,&hellip;<\/p>\n","protected":false},"author":37,"featured_media":17346,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[337],"tags":[],"class_list":["post-17344","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-gcp"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/17344","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/comments?post=17344"}],"version-history":[{"count":2,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/17344\/revisions"}],"predecessor-version":[{"id":17348,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/17344\/revisions\/17348"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/media\/17346"}],"wp:attachment":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/media?parent=17344"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/categories?post=17344"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/tags?post=17344"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}