Digitalocean load balancer down happens when the load balancer may be down or not sending traffic to the target Droplet when attempting to access it via the load balancer. Bobcares answers all questions on Digital ocean Load balancer down, no matter the size, as part of our Digital ocean managed Services.  

Load Balancer Down

While attempting to reach the droplet via the load balancer, the load balancer may be down or not directing traffic to the target Droplet.

Follow the steps below in this steps given below to manage the troubleshooting.

1. Check the load balancer’s connection between the load balancer and the Droplet first.
2. Ensure that the load balancer can have access via the public internet.
3. If attempting to reach the Droplet via a hostname pointing at the load balancer, check the DNS configuration of the hostname.

Check Load Balancer Status

To view the status of the load balancer in the DigitalOcean Control Panel, go to Networking and then the Load Balancers tab. The page displays a list of the load balancers configured in the account. Select the load balancer for the target Droplet.

The Droplet tab of the load balancer in the Digitalocean will display the Droplets in connection to the load balancer. And the status column indicates the health of the connection between the Droplets and the load balancer. If the target Droplet is in the list of the Droplets that connect to the load balancer. Then add it to the load balancer and then try to connect to it again.

If the Droplet is in connection to the load balancer but its status is ‘down,’. The internal network configuration of the Droplet is incorrect or the Droplet is offline. Before proceeding, ensure that the Droplets are healthy and active.

Ping the Load Balancer and the Droplet

Using ping, determine whether the connection is failing at the Digitalocean load balancer or Droplet level. A ping is a diagnostic tool available in most operating systems. Ping tests the connection between network devices.

Add an inbound traffic rule that allows ICMP traffic to reach the Droplet under the protection of a cloud firewall. To verify connections, the ping diagnostic tool employs the ICMP protocol. If the cloud firewall does not have an inbound rule for ICMP, it will reject any ping attempts to the Droplet.

To ensure that the load balancer is accessible from the computer, open a terminal on the local machine and run the following command:

ping

Case 1:

If the load balancer is reachable via the public internet, ping returns the amount of data sent to it. And also the time it took for the data to reach the load balancer

PING 203.0.113.154 (203.0.113.154): 56 data bytes 64 bytes from 203.0.113.154: icmp_seq=0 ttl=46 time=239.488 ms 64 bytes from 203.0.113.154: icmp_seq=1 ttl=46 time=352.659 ms

Case 2:

Ping returns a timeout error if the load balancer is not available via the public internet:

PING 203.0.113.154 (203.0.113.154): 56 data bytes Request timeout for icmp_seq 0

Case 3:

Use the Droplet’s IP address to run the same command. If the Droplet answers but the Digitalocean load balancer does not, the load balancer is most likely to blame for the connection issue. If the load balancer is the issue, then there are two choices:

Destroy the load balancer and then rebuild it. The IP address of the load balancer is not retained with this option. And, create a support ticket and request that the load balancer is reset. This option keeps the IP address of the load balancer.

Check Load Balancer’s DNS

When attempting to reach the Digitalocean load balancer through a hostname, such as www.ex1234ample.com. An A record must be set up with the DNS provider to refer the hostname to the load balancer’s IP address.

After this, to confirm that the hostname has an A record pointing to the load balancer’s IP address, open a terminal and use the dig software to obtain the domain’s A records:

dig enter-the-hostname A

Case 1:

The command produces the following output:

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53050
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 5

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 1aad2b567441ddd264d7b5c062058926dea6b1dfd388758f (good)
;; QUESTION SECTION:
;bigassdraculasclub.com. IN A

;; ANSWER SECTION:
example.com. 30 IN A 104.16.243.78
example.com. 30 IN A 104.16.244.78

;; AUTHORITY SECTION:
example.com. 172800 IN NS ns3.digitalocean.com. example.com. 172800 IN NS ns2.digitalocean.com. example.com. 172800 IN NS ns1.digitalocean.com.

Case 2:

If the output’s ANSWER SECTION lacks an A record pointing to the Digitalocean load balancer’s IP address, add an A record to the hostname’s DNS settings.

Finally, add an A record via the management panel if your DNS provider is DigitalOcean. If DigitalOcean is not the DNS provider, see the documentation of the DNS provider to learn how to establish A records for the hostname. In the case of a recent A record update for the hostname, the update may take up to 24 hours to spread across the internet.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude, the DigitalOcean load balancer is down when the load balancer may be offline or not sending traffic there.