Server configuration

ThinLinc Web Access is served by the service tlwebaccess. The default TCP port number for this HTTP service is 300. It can be changed to some other port such as 443, assuming this port is free. The configured port must be allowed in any firewalls.

For details about configuring ThinLinc Web Access behind a reverse proxy, please see Reverse proxy.

In a cluster setup, the tlwebaccess service must run on all machines. The same service port should be used, and all machines must be accessible from the clients.

The setting /webaccess/login_page will also need to be configured in a cluster setup. The client first authenticates with the master. Once the master server has chosen an agent server for the session, the client will authenticate with that agent server. The browser will thus present pages from two different servers. First a page from the master, and then from the agent, unless the agent is on the same server of course. This parameter is a means for the agent to know the public hostname of the master server. Thus when it’s properly set, the user can, when the session has ended, click a button to return from the agent to the master to log in again. The default value, which is /, will not redirect to another server and is only usable if you are running a standalone ThinLinc server, i.e. not a cluster. If you have more than one server or are using Network Address Translation (NAT), you must set this parameter to an address that all clients can connect to. Example:

login_page = https://thinlinc-master.example.com:300/

Please see Parameters in /webaccess/ for details on all possible settings for ThinLinc Web Access.