Hello,
I’m trying to set up ThinLinc for access behind the Pangolin reverse proxy. I did the following:
Every time, i’m able to get to the Web Access login page. I log in, successfully, however, when it tries to get the agent at https:///agent/ , it times out. Any ideas on what to do?
I’m not familiar enough with Pangolin to be able to give a concrete answer here, I’m afraid. You might need to check the redirect URL, and check that your Pangolin instance is configured to forward that on to the agent. You can find more information on configuring ThinLinc behind a reverse proxy here:
Hello,
I’m not sure what you mean with redirect URL. I did change the agent’s URL, to that domain. If i should do anything else, please inform me as i’m clueless. I don’t think this is a Pangolin problem, i think this is caused by how the ThinLinc agent acts. From what I’ve seen, the web login flow redirects to https://domain.tld/agent/ and i can tell that’s responding since when i open it, it asks me to login and has a big blue button to redirect to the login form. It seems you’ve encountered a similar problem in the past, but that forum post didn’t help me.
Is your reverse proxy configured to set the Upgrade and Connection headers? From the documentation linked above:
ThinLinc Web Access relies on WebSocket connections to establish and maintain user sessions. Therefore, your proxy must set the Upgrade and Connection headers again. If this is not configured correctly, users will be able to load the login page but unable to start a session.
Ooh… No WebSocket support on Pangolin, sadly (Uptime Kuma complains about this too)… Welp guess i’m just going to forward the port.
Thank you for taking your time to answer my question especially during the one-in-40-years eclipse and Perseides meteor shower.
We didn’t get the solar eclipse down here in the southern hemisphere, so nothing missed 
glad we got to the bottom of the Pangolin issue, though!