Custom path configuration

You may also want to serve the entire ThinLinc Web Access interface from a specific sub-path, such as /subpath/, instead of from the server root /. This requires prefixing all of your ThinLinc path handlers. The master’s path becomes /subpath/ and the agent paths will also be nested under it, such as /subpath/connect/agent1.internal.example.com/.

location /subpath/ {
    proxy_pass https://tl.internal.example.com:300/;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
}

location /subpath/connect/tl.internal.example.com/ {
    proxy_pass https://tl.internal.example.com:300/;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
}

location /subpath/connect/agent1.internal.example.com/ {
    proxy_pass https://agent1.internal.example.com:300/;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
}