---
title: "Manage Load Balancers | Hostman Docs"
description: "Learn how to configure load balancer health checks, SSL and other advanced settings for secure, stable networking."
---

> For the complete documentation index for AI agents, see [llms.txt](https://hostman.com/llms.txt).

Manage your load balancers in the Hostman dashboard.

## Advanced Settings

To launch a load balancer, you only need to add servers and set at least one forwarding rule, leaving the rest of the settings as default. However, you can also configure the load balancing in more detail.

To configure a new load balancer, click **Advanced settings** in the **Settings** step when creating a load balancer.

To configure an existing load balancer:

1.  Go to the **Load balancers** section and click on the load balancer.
    
2.  Click **Configure** next to **Advanced settings**.
    

### Balancing Algorithm

Select your preferred balancing algorithm.

-   **Round Robin** sends requests to servers in turns: the first request to the first server, the next request to the second server, and so on until the last server, after which the cycle starts over.
    
-   **Least Connections** sends each new request to the server that currently has the least number of active connections. This method allows you to distribute the load on the servers fairly evenly.
    

### Sticky Sessions

When enabled, the load balancer uses cookies to redirect requests from the same client to the same server.

However, if the server becomes unavailable, the load balancer will redirect the client's request to another server.

### Health Checks

Health checks run in the background. The load balancer sends test requests to the servers. If a server fails the test, it is removed from the load balancing until it passes the test again. 

You can use default health checks parameters or configure them yourself.

First, set the basic parameters for sending test requests to the server: protocol and port. We recommend using the TCP protocol.

You can also set your own values for these parameters:

-   **Check interval**: how often to send test requests.
    
-   **Response timeout**: how long to wait for a response to a test request.
    
-   **Unhealthy threshold**: the number of failed tests in a row before the server is removed from balancing.
    
-   **Healthy threshold**: the number of successful tests in a row before the server is added back to balancing.
    

### SSL Certificate

When enabled, all HTTP traffic to the load balancer will be redirected to a secure connection. To make this work, you must create at least one rule to redirect from HTTP to HTTPS.

### Proxy Protocol

When enabled, the load balancer will pass client connection data (IP address and port) to the end server, rather than discarding it. This can be useful for collecting traffic statistics, showing a site or app in the user's language, or providing specific features based on the user's country.

The proxy protocol will work for all redirection rules with HTTP or HTTPS  as the target protocol.

Make sure the end servers support the Proxy protocol; otherwise, they will give a 400 error when health checked, and the load balancer will stop redirecting requests to them. 

Configuring your server to use the proxy protocol depends on the software you use:

-   [Nginx](https://docs.nginx.com/nginx/admin-guide/load-balancer/using-proxy-protocol/#configuring-nginx-to-accept-the-proxy-protocol)
    
-   [Apache](https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html#remoteipproxyprotocol)
    

### Backend Keep-alive

When enabled, the load balancer will maintain persistent connections with the servers for all rules with HTTP or HTTPS as target protocol. This means that instead of opening and closing a new TCP connection for each request, the load balancer keeps the connection open for multiple requests.

In most cases, enabling this option will help improve performance and reduce response time for the client.

## Requirements and Limitations

When setting up redirects to HTTP and HTTPS, keep in mind the following details.

### Setting Up HTTP

If your redirect settings use the HTTP protocol, you may receive a 503 Service Unavailable error when accessing the domain.

To fix the problem, use the TCP protocol instead of HTTP in the health check settings:

![Image7](https://content.hostman.com/assets/26ffe594-7fc9-4976-847a-29f5f373c06e?width=606&height=164)

### Setting Up HTTPS

For HTTPS redirection to work correctly, you should use the following settings:

1.  In the forwarding rules, add a rule with TCP instead of HTTPS and use port 443, as shown below:
    

![Image8](https://content.hostman.com/assets/42b2076a-090f-4651-842b-82491108dde2?width=620&height=736)

2.  In the **Health checks** parameter, use the TCP protocol and port 80:
    

![Image7](https://content.hostman.com/assets/26ffe594-7fc9-4976-847a-29f5f373c06e?width=606&height=164)

3.  Set the load balancer IP address as the domain A record.
    
4.  Add an SSL certificate to each server’s domain in the balancing.
    

### Cloudflare Usage

If your domain uses Cloudflare name servers, you must choose TCP as the source and destination protocols when pointing the domain to the load balancer's IP address. Other protocols are not supported.

![Image8](https://content.hostman.com/assets/42b2076a-090f-4651-842b-82491108dde2?width=620&height=736)

### Port Restrictions

You cannot set up port 22 as the source port. If you try to connect to the load balancer on port 22, you will receive a _Connection refused_ error.

## Maintenance Window

A maintenance window is a period during which we may apply updates and optimize service performance.

Two options are available:

-   Anytime
-   At a specified time

The time is set according to your time zone.

You can set a maintenance window when creating a load balancer, and you can also manage it in the settings.

To change the maintenance window:

1.  In the **Load Balancers** section, click the load balancer you need.
    
2.  On the **Configuration** tab, click **Edit** in the **Load balancer m****aintenance window** block.
    
3.  Choose the desired option and save the changes.
    

## Domain Setup

Each load balancer is issued a public IP address. You can find the IP address in the **Load balancers** section.

![Image5](https://content.hostman.com/assets/bd4ef49f-eb7d-4594-94e1-b69973ad2e2d?width=1514&height=765)

Set this IP address as the A record of your domain.

## Action History

You can view the actions performed on load balancers. To check the action history, go to **Load balancers** → click on the load balancer → **History**.

We log the following events:

-   Creating a balancer
    
-   Adding a server to balancing
    
-   Removing a server from balancing
    
-   Creating forwarding rules
    
-   Changing forwarding rules
    
-   Changing load balancer settings