Troubleshoot common issues

Available in Classic and VPC

You may encounter the following issues while using the Load Balancer service. Check the causes and solutions for each issue and take appropriate action.

Load Balancer status shows "Stopped"

After creating a Load Balancer, the status continues to display "Stopped."

Cause

It occurs when the application port setting is missing or there's no rule allowing the Load Balancer in the ACG.

Solution

Set the application port on the server bound to the Load Balancer and create a rule in the server's ACG to allow the Load Balancer.

Setting the application port
After creating the Load Balancer, you must set the application port on the server bound to it.

To set the application port, follow these steps:

1. See Create Application Load Balancer to create a Load Balancer.
2. Set the application port in the Load Balancer settings screen.
   • Once the application port is set on the server bound to the Load Balancer, the Load Balancer status changes to "Running."
   • The status of the server bound to the Load Balancer also changes to "In Use."
   • The Health check for the server changes from "Failure" to "Success."

Set ACG
When both the application port and ACG rules are set, the Load Balancer operates normally and displays related information. You can also view monitoring information such as Concurrent Connection, Connection per Second (CPS), and Traffic. Note that monitoring information is available about 10 minutes after the Load Balancer status changes to "Running."

To set ACG, follow these steps:

1. From the NAVER Cloud Platform console, click Server > ACG, in order.
2. Select the relevant ACG and click the [Set ACG] button.
3. Add an ACG rule to allow the Load Balancer.
   • Protocol: enter the Load Balancer's protocol
   • Access source: enter the Load Balancer's access source (e.g., ncloud-load-balancer). You can find the access source in the AccessControlGroup source of the Load Balancer information
   • Allowed port (service): enter the Load Balancer's server port

Changing zone after creating a Private Load Balancer

Unable to change the zone after creating a Private Load Balancer.

Cause

Because KR1 and KR2 have different IP ranges, moving to a different zone with the same IP is impossible.

Solution

To change the zone of a Private Load Balancer, create a new Load Balancer in the desired zone.