Tableau Server requires static IPv4 or IPv6 addresses. You may notice undesirable symptoms if your cluster has temporary IPv6 addresses (which are dynamic) enabled.
If you are running a Tableau Server cluster and one or more of the servers has temporary IPv6 addresses enabled, you may notice one or more of the following categories of symptoms.
If a primary Tableau Server has temporary IPv6 addresses enabled, worker servers running a data engine and/or repository may have a red, down status for those processes. This is because they are unable to communicate with the primary.
If one or more workers have temporary IPv6 addresses enabled (but the primary does not) you may not see the red, down status icons for any of the servers, but you will see connection errors in log files as the workers attempt and fail to communicate with services on the primary Tableau Server.
Here are examples of errors that may be written to the Tableau Server log files, if the primary Tableau Server or Tableau Worker servers have temporary IPv6 addresses enabled.
Data Engine Connection Errors
A message similar to the following may be in the log file for the server(s) running the data engine (ProgramData\Tableau\Tableau Server\data\tabsvc\logs\dataengine\tabspawnde0.log):
2013-10-23 16:02:41.234 -0700 ERROR root: connection to database failed
The process that spawns the data engine is unable to query Tableau's PostgreSQL database to determine which is the active data engine and which is the standby data engine. This information is in the following location: ProgramData\Tableau\Tableau Server\data\tabsvc\logs\dataengine\tdeserver0_<date_and_time>.log. For example, in the log file you may see a message similar to this:
2013-10-24 10:57:40.345 (6056): tdeserver: connection failed (IPC_Server_Socket: whitelist exclusion, peer=1234:113:f00b:2108:f51d:2101:c67c:ea97:12345)
Repository Access Errors
A message similar to the following may in in the log file for the server(s) running the repository (ProgramData\Tableau\Tableau Server\data\tabsvc\logs\pgsql\postgresql-<Day>.log):
2013-10-24 10:53:01.112 PDT 5444 FATAL: no pg_hba.conf entry for host "1234:113:f00b:2108:f51d:2101:c67c:ea97", user "tblwgadmin", database "workgroup", SSL off
Temporary IPv6 addresses are a feature of some Windows operating systems, including many that are supported by Tableau Server. When a computer has temporary IPv6 addresses enabled, its IPv6 address changes over time.
This Windows feature affects Tableau Server because, internally, Tableau Server relies on static IP addresses to communicate with worker servers in a cluster, or with trusted hosts in an environment configured for trusted authentication. In other words, even though you can use a computer's name instead of its static IPv4 address to do certain types of configuration in Tableau—such as identify the primary Tableau Server to a worker, or vice versa—the IP address for the computer must be static.
netsh interface ipv6 show privacyIf you see a status of enabled for Use Temporary Addresses, temporary IPv6 addresses are enabled for the computer.
Tableau Server 2018.2 and newer versions:
netsh interface ipv6 set global randomizeidentifiers=disablednetsh interface ipv6 set privacy state=disabledtsm stop tsm pending-changes applytsm startTableau Server 2018.1 and older versions:
netsh interface ipv6 set global randomizeidentifiers=disablednetsh interface ipv6 set privacy state=disabledtabadmin stop tabadmin configtabadmin start001473413

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.