I am experiencing the exact same issue. I can access any droplet on the load balancer directly and it resolves fine, but the Load Balancer itself says that the droplet is down.

I know that the status is determined from health checks, but the health check settings are pointed directly at port 80 on those droplets - so I’m just not really sure what else to do.

same here

i just made support ticket it’s strange.

same here.
@uusa35fc8632c17142324fe9ff did you get any information?

Hello,

You might want to double check that there is nothing blocking the health checks and pings that are being done from your Load Balancer to your respective droplets.

In my case it was fail2ban which had picked up the Load Balancer’s local IP address.

tail -f /var/log/fail2ban.log 

To ensure this doesn’t continue happening you might want to add your VPC’s ip block to the fail2ban igonore list. Adding only the load balancers IP might not work as it might be subject to change.

To do so simply execute the following commands:

1) Copy fail2bans jail.conf and change it

cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local

2) Look for the ignoreip line, uncomment it, add your VPC block and save it.

You can find your VPC’s ip range in your Digital Ocean account under Networking > VPC

nano /etc/fail2ban/jail.local

Hoping this saves you some time!