---
schema_version: "1"
id: afcc9e8f5ee88fbc7594eebe12424d56af2fe65fc370b31650a48963a32f0e76
title: Add a Load Balancer
collection: tableau
version: next
locale: en-us
portal_url: https://docs.salesforce.com/tableau/next/en-us/server-linux/distrib_lb.md
canonical_url: https://help.tableau.com/v0.0/server-linux/en-us/distrib_lb.htm
source_site: help.tableau.com
content_type: documentation
content_hash: 0052bec427399f7f96b978f60dc495790d8652d7617a534db0c9f304b8bfa3f3
description: Add a load balancer to distribute requests across multiple Tableau Server gateways.
---
[Skip to main content](#main-content)

# Add a Load Balancer

You can enhance the reliability of Tableau Server by running gateways on multiple nodes, and configuring a load balancer to distribute requests across the gateways. Unlike the repository process, which can be active or passive, all gateway processes are active. If one gateway in a cluster becomes unavailable, the load balancer stops sending requests to it. The load balancer algorithm you choose determines how the gateways will route client requests.

- **Kerberos**: If you will be using Kerberos authentication, you need to configure Tableau Server for your load balancer before you configure Tableau Server for Kerberos. For more information, see [Configure Kerberos](https://help.tableau.com/v0.0/server-linux/en-us/config_kerberos.htm).
- **Tested load balancers**: Tableau Server clusters with multiple gateways have been tested with Apache and F5 load balancers.
    
    If you are using an Apache load balancer and creating custom administrative views, you need to connect directly to the Tableau Server repository. You cannot connect through the load balancer.
- **Tableau Server URL**: When a load balancer is in front of a Tableau Server cluster, the URL that's accessed by Tableau Server users belongs to the load balancer, not the initial Tableau Server node.
- **Single load balancer endpoint**: You must configure your load balancers for a single URL endpoint. You cannot configure different endpoint hosts to redirect to the same Tableau Server deployment. The single external URL is defined in `gateway.public.host` when you configure Tableau Server, as described in [Configuring Proxies and Load Balancers for Tableau Server](https://help.tableau.com/v0.0/server-linux/en-us/proxy.htm).
- **Trusted host settings**: The computer running the load balancer must be identified to Tableau Server as a trusted host, as described in [Configuring Proxies and Load Balancers for Tableau Server](https://help.tableau.com/v0.0/server-linux/en-us/proxy.htm).

## Configure Tableau Server to work with a load balancer

The settings used to identify a load balancer to Tableau Server are the same ones that are used to identify a reverse proxy server. If your Tableau Server cluster requires both a proxy server and a load balancer, both must use a single external URL defined in `gateway.public.host` and all proxy servers and load balancers must be specified in `gateway.trusted` and `gateway.trusted_hosts`. See [Configuring Proxies and Load Balancers for Tableau Server](https://help.tableau.com/v0.0/server-linux/en-us/proxy.htm).