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

If you enable PROXY protocol on a load balancer but the services on the backend Droplets aren’t configured to accept PROXY protocol headers, those Droplets gives a 400 response to the load balancer’s health checks. This means the load balancer considers them unhealthy and stops routing traffic to them.

How you enable PROXY protocol support on your Droplets depends on the software you’re running. Here are some resources for common services:

• Configuring nginx to accept the PROXY protocol
• Apache’s remoteIPProxyProtocol directive

Related Topics

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 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.