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.
Validated on 19 Mar 2024 • Last edited on 29 Mar 2024
When a load balancer’s connection remains idle for 60 seconds, it times out and responds with a 504 Gateway Timeout error. If your application requires longer than 60 seconds to respond, you can increase the load balancer’s timeout settings in its Settings tab.
Load balancers return 503 errors when there are either no Droplets assigned to them or all of the assigned Droplets are unhealthy.
Health checks often fail due to firewalls or misconfigured backend server software.
Edit the ConfigMap which nginx uses to enable PROXY protocol.
Try using different keywords or simplifying your search terms.