Load Balancer Support

DigitalOcean fully manages Regional Load Balancers and Global Load Balancers, ensuring they are highly available load balancing services. Load balancers distribute traffic to groups of backend resources in specific regions or across different regions, which prevents the health of a service from depending on the health of a single server, cluster, or region.

How to Troubleshoot Load Balancer Health Check Issues

Health checks often fail due to firewalls or misconfigured backend server software.

How do I enable PROXY protocol when my load balancer sends requests to the NGINX Ingress Controller?

Edit the ConfigMap which nginx uses to enable PROXY protocol.

Why does my load balancer respond with a 504 Gateway Timeout error?

By default, load balancers time out after the connection has been idle for 60 seconds. You can customize the timeout duration.

Why does my load balancer respond with an HTTP 503 error?

Load balancers return 503 errors when there are either no Droplets assigned to them or all of the assigned Droplets are unhealthy.

I can't reach a Droplet through my DigitalOcean Load Balancer

Your load balancer may be down or not directing traffic to the target Droplet.

Why do my DOKS load balancer settings keep reverting?

You can configure load balancers that are provisioned by DOKS using Kubernetes service annotations.

Why do my load balancer's Kubernetes node(s) have the No Traffic status?

Kubernetes service ’externaltrafficpolicy’ field controls how nodes respond to health checks.

Why did all of my backend Droplets become unhealthy when I enabled PROXY protocol on my load balancer?

Enable PROXY protocol support on your Droplets.