Reverse proxy

Running ThinLinc Web Access behind a reverse proxy is a way to integrate ThinLinc into existing infrastructure or meet organizational requirements. This chapter explains the requirements ThinLinc Web Access places on a reverse proxy to function correctly.

In a ThinLinc cluster, users start at the ThinLinc master server, but their actual sessions run on individual agents to which ThinLinc Web Access automatically redirects traffic. If a reverse proxy is used, it must be configured to handle this routing and forward the connection to the correct internal agent.

To support a proxy environment, specific ThinLinc parameters should be updated. This involves enabling the X-Forwarded-For header to identify client IPs (see Forwarding client IP addresses) and updating /webaccess/login_page to match the public URL for the login page.

Please note that this is a conceptual guide intended to illustrate the routing logic. You must adapt the configuration to match your environment.