KNOWLEDGE BASE

Cannot Connect to Tableau Server through SSL Proxy


Published: 06 Mar 2013
Last Modified Date: 28 Dec 2016

Issue

When Tableau Server is behind a proxy configured for SSL, Tableau Desktop may not be able to connect to Tableau Server (an HTTP 500 or HTTP 404 response code might be returned). This issue can present itself in one or more of the following ways:

  • You cannot access Tableau Data Server data sources from Tableau Desktop.
  • You cannot connect to any data source published on Tableau Server.

Environment

  • Tableau Server (not configured for SSL)
  • Reverse proxy configured for SSL

Resolution

Configure the proxy server to forward the X-Forwarded-Proto HTTP header.

Generally, you must enable SSL affinity as well. In some proxies, this setting refers to SSL Session Persistence or SSL Persistence.

The following steps are for enabling X-Forward-Proto on an F5 proxy device. For other devices, you might need to modify these steps and settings.

  1. In a custom HTTP profile applied to the virtual server, use Insert header:
    • For HTTPS virtuals, insert X-Forwarded-Proto with a value of https.
    • For HTTP virtuals, insert X-Forwarded-Proto with a value of http.
  2. Apply an iRule to the Virtual Server. A typical example of this would be:

    HTTP::header insert X-Forwarded-Proto https}
    when HTTP_REQUEST { HTTP::header insert X_FORWARDED_PROTO https }
    OR:
    when HTTP_REQUEST { HTTP::redirect https://\[HTTP::host\]\[HTTP::uri\] }

Additional Information

HTTP header naming convention is to capitalize words and separate them using hyphens. Generally, unless required by the proxy, do not use underscores. Some examples of headers that follow standard naming convention include:

  • X-Forwarded-Proto
  • User-Agent
  • If-Match
Did this article resolve the issue?