Skip to main content

Troubleshoot Load Balancers

Use this page to resolve common Load Balancer problems in MyAccount. Find the symptom that matches what you see, then follow the checks. For configuration details, see Manage Load Balancers.

Backend Marked DOWN or Health Check Failing​

An Application Load Balancer marks a backend UP only when it returns a 2xx or 3xx response on the health-check path; otherwise the backend is DOWN and removed from rotation.

Check the following:

  • The health-check path (default /) exists on the backend and returns 2xx/3xx. Point it at a path your application serves.
  • The backend's IP and port in the Backend Mapping tab are correct — use the private IP if the node is on E2E Cloud.
  • The backend node is running and the application is listening on the configured port.
  • The backend's own security group and firewall allow traffic from the load balancer.

Status Stuck on Creating, Deploying, Upgrading, or Deleting​

These are transition states. Allow time before acting:

  • Creating takes about 5–6 minutes.
  • Deploying (applying a configuration change) takes about 2–3 minutes.

Most actions are disabled during these states. If a load balancer stays in a transition state far longer than expected, refresh the list; if it does not clear, contact support.

"Backend Connection Failure" or "Backend Status Unavailable"​

  • Backend Connection Failure — the load balancer is running but cannot reach one or more backends. Verify the backend nodes are running, reachable on the backend port, and (for internal traffic) attached to the same VPC.
  • Backend Status Unavailable — backend health cannot be determined. Confirm the health-check configuration and that the backends respond on the health-check path/port.

HTTPS or SSL Certificate Problems​

  • Certificate not in the SSL dropdown — the load balancer can only use certificates imported with the SSL certificate, the private key, and the certificate chain. Import all three from Services → Certificate Manager. See SSL Certificates.
  • HTTP Redirect option unavailable — the Redirect HTTP to HTTPS option only applies when the front-end protocol is HTTPS or Both. Change the protocol on the Info tab first.
  • Purchased certificate not working — certificates purchased from E2E do not include the private key. You must import the certificate manually with the locally generated private key.

Network, VPC, and IP Issues​

  • Internal load balancer has no VPC — an internal (private) load balancer must be attached to at least one VPC. Attach a VPC from the Network tab.
  • Cannot attach another VPC — a load balancer can have at most three VPCs attached.
  • Public IP not assigned — only an external load balancer has a public IP. To keep a stable address, reserve a public IP. See Reserved IP.
  • IPv6 not present — IPv6 is attached separately from the Network tab; use Attach to add it.

Cannot Upgrade the Plan​

  • Power off the load balancer before running Upgrade Plan.
  • Upgrade is not available for committed load balancers or private-cloud load balancers.

NLB Listening Port Rejected​

For a Network Load Balancer, the listening port must be 80, 443, or a value between 1024 and 65535. Ports 8080, 10050, and 9101 are reserved and cannot be used. An Application Load Balancer does not use a separate target port.

ACL Rules Not Available​

ACL rules are an Application Load Balancer feature only. A Network Load Balancer forwards TCP traffic and has no ACL tab. ACL rules cannot be combined with TCP backends.

Deleting a Committed Load Balancer​

A committed load balancer can be deleted at any time — the commitment does not block deletion. When you delete one before its committed period ends, the Delete dialog warns that the load balancer is committed and reserved until the end date, and recommends that you do not delete it.

Deleting early does not refund the commitment: the infra credits (or charge) for the committed period are applied in full when the load balancer is launched and are not returned if you delete before the term ends.

If your goal is only to stop paying beyond the committed term, you do not need to delete early. Instead, set the end-of-period behavior in Committed LB settings to Hourly Billing (then terminate once it switches to hourly) or Auto Termination. See Committed Load Balancer.

An Action Is Disabled​

Lifecycle actions (Start, Power Off, Upgrade Plan, Convert to Committed, Delete) are disabled while the load balancer is Creating, Deploying, Upgrading, or Deleting. Wait for the load balancer to reach a stable state, then retry.

Encryption Cannot Be Enabled​

Encryption is enabled only at creation time and cannot be added or removed afterward. To get an encrypted load balancer, create a new one with Enable Encryption selected. See Load Balancer Encryption.

Access Logs Are Empty​

Access logs must be activated before they record data. Activate access logs from the Info tab, then view them under Action Logs.

ResourceUse it for
Manage Load BalancersBackends, ACLs, network, monitoring, and actions.
Choose a Load BalancerConcepts, routing policies, and plans.
SSL CertificatesHTTPS and certificate setup.
Load Balancer EncryptionEncryption at rest.
VPC · Reserved IP · Security GroupsNetwork and security.
Last updated on June 5, 2026.