DigitalOcean Load Balancer Health Check Configuration
When you change the port that backend Droplets (instances) listen on, you must also update the Load Balancer's health check port to match — otherwise the load balancer marks all backends as unhealthy and stops forwarding traffic.
When this occurs
If you move Apache or Nginx from port 80 to a custom port (e.g., 8080) behind the load balancer, and forget to update the health check, traffic stops flowing even though the application is running fine.
How to fix
- In the DigitalOcean Control Panel, go to Networking → Load Balancers.
- Select the load balancer.
- Click Settings → scroll to Health Checks.
- Update the Port to match the new backend port (e.g., 8080).
- Save. The load balancer will re-check backends within a few seconds.
Recommended health check settings
- Protocol: HTTP
- Port: same as your backend application port
- Path:
/or a dedicated health endpoint (e.g.,/health) - Check interval: 10s, Unhealthy threshold: 3