# Thinlinc behind a reverse proxy? **URL:** \ **Category:** Community Support\ **Tags:** webaccess, tlserver\ **Created:** [4 October 2024 18:01 UTC](https://community.thinlinc.com/t/thinlinc-behind-a-reverse-proxy/1116 "2024-10-04T18:01:42Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jhjacobs](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/jhjacobs/32/550_2.png) [@jhjacobs](https://community.thinlinc.com/u/jhjacobs)\ **Post date:** [4 October 2024 18:01 UTC](https://community.thinlinc.com/t/thinlinc-behind-a-reverse-proxy/1116/1 "2024-10-04T18:01:42Z")
I’ve been messing with Guacamole and Kasm, but i find both to be unstable and hard to maintain. Thinlinc on the other hand seems much easier, and so far it hasn’t crashed 🙂 I am trying to make it accessable for remote workers, running it behind Caddy. But after i login, it goes from [https://thinlinc.domain.tld](https://thinlinc.domain.tld) to [https://192.168.1.1:300/agent](https://192.168.1.1:300/agent) Which obviously doesnt work outside the building. Has anyone successfully made it work? Or am i overlooking something? ---
**Author:** ![McGyverFail](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/mcgyverfail/32/534_2.png) [@McGyverFail](https://community.thinlinc.com/u/McGyverFail)\ **Post date:** [4 October 2024 19:38 UTC](https://community.thinlinc.com/t/thinlinc-behind-a-reverse-proxy/1116/2 "2024-10-04T19:38:53Z")
Have you tried changing agent\_hostname in vsmagent.hconf to a hostname that is resolveable (and reachable) by your client machines? If its unset, it will default to the server’s primary ip. ---
**Author:** ![jhjacobs](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/jhjacobs/32/550_2.png) [@jhjacobs](https://community.thinlinc.com/u/jhjacobs)\ **Post date:** [4 October 2024 20:29 UTC](https://community.thinlinc.com/t/thinlinc-behind-a-reverse-proxy/1116/3 "2024-10-04T20:29:09Z")
i came across this in the NAT documentation yes, i’m not conviced yet it will not redirect to [https://thinlinc.domain.tld:300](https://thinlinc.domain.tld:300) yet (cant test it right now), but in the worst case i can forward that port too. I was hoping to stick everything behind a well configured Caddy server though 🙂 ---
**Author:** ![McGyverFail](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/mcgyverfail/32/534_2.png) [@McGyverFail](https://community.thinlinc.com/u/McGyverFail)\ **Post date:** [4 October 2024 20:42 UTC](https://community.thinlinc.com/t/thinlinc-behind-a-reverse-proxy/1116/4 "2024-10-04T20:42:01Z")
The port will remain, yes. Then you would have to configure the proxy software to rewrite that part before the response is sent back to the clients.