Skip to main content
Connect the balancer
Last update:

Connect the balancer

  1. Merge servers with private network.
  2. Configure routing to the balancer subnet.
  3. Order a balancer.
  4. Check balancer operation.

1. Interconnect servers with a private network

To connect the load balancer, you must network the servers using a global router.

When creating a network, do not use addresses from the subnet on servers. This subnet hosts load balancers, its use can cause load balancers to fail.

2. Configure routing to the balancer subnet

  1. Select the subnet on which to host the load balancer. The default private subnet is, but you can use a different private subnet of dimension /16.
  2. Add the selected subnet to the global router that merge servers.
  3. Write routes to the selected balancer subnet on the servers.

3. Order a balancer

  1. If your servers use HTTPS, add your TLS (SSL) certificate to the secrets manager. You can also issue a Let's Encrypt certificate.

  2. In Control Panel, navigate to Network ServicesFirewall Load Balancer.

  3. Click Connect Balancer.

  4. Choose the tariff according to the desired channel width — 20, 50, 100 or 1 000 Mbps. If you need a different channel width, select Other and specify the required value in Mbps.

  5. Specify the global router that you used to merge the servers — its name, ID, or a list of subnets added to the router. You can view the router data in Control Panel: Network ServicesGlobal Router → Router page.

  6. Enter the private subnet that selected to host the balancer.

  7. Select a balancing algorithm:

    • Round Robin is a round robin algorithm in which requests are passed to each server in turn;
    • Weighted Round Robin is a weighted round robin algorithm in which each server is assigned a weighting factor corresponding to its performance and power. More requests are transferred to servers with higher ratios;
    • Source IP hash is an algorithm that, depending on the HTTP header or IP address, selects a preferred server to receive the request;
    • Least Connections — an algorithm that sends the request to the least loaded server.
  8. If you want to use Sticky Sessions, check the Sticky Sessions checkbox.

  9. Select the protocol of the target servers: TCP, HTTP, HTTPS.

  10. If you selected the TCP protocol, specify the parameters for using the protocol — all private IP addresses assigned within the global router's networks, with the ports specified.

  11. If you selected the HTTP protocol, specify all combinations of URLs received from the Internet and the IP addresses to which they should be redirected, specifying the port. For example, - http://X.X.X.X:X.

  12. If you selected the HTTPS protocol, specify:

    • all combinations of URLs received from the Internet and the IP addresses to which they should be redirected, specifying the port. For example, - http://X.X.X.X:X;
    • The ID of the certificate you added in step 2. The ID can be viewed in control panel: Cloud PlatformSecrets ManagerCertificates tab → in the certificate menu, select Copy UUID;
    • The ID of the cloud platform project where the certificate resides.
  13. Optional: if you need to provide any additional data, enter it in the Additional Comment field. For example, describe the use case in more detail, specify which pools host the infrastructure, leave an administrator contact for communication and details.

  14. Click Connect Balancer.

  15. We will create and submit a ticket to activate the service. Connection takes up to seven working days. When the balancer is ready, in a ticket we will give you a secure public IP address to which to direct incoming traffic for balancing.

4. Check balancer operation

  1. After the message that the load balancer is connected, verify that configured routes between the network segments that host the target servers and load balancers.
  2. Test the load balancer by sending test requests to the received IP address.