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 to 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?
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.
i came across this in the NAT documentation yes, i’m not conviced yet it will not redirect to 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
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.