Closed rursache closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Forgot to add, I'm not sure if this is a lsio issue or a Kasm issue, if it's not on you guys let me know and i'll move it to them. Thanks!
This is a Kasm thing you need to set your proxy port to 0 in the guide here, then it absorbs it from whatever the current url scheme is https://www.kasmweb.com/docs/latest/how_to/reverse_proxy.html#update-zones
I need to whip up a swag reverse proxy conf and add this in the readme as you are not the first person to stumble on this, please don't close this issue so I remember.
Thank you @thelamer, setting Proxy Port
to 0
in Kasm - Admin - Zones - default zone (edit)
fixed it for me!
This is now docced in the readme
Is there an existing issue for this?
Current Behavior
Currently I have Kasm installed on port 18260 instead of the default 443.
https://LOCALIP:18260
works perfectly however my cloudflare tunnelhttps://kasm.domain.tld
is not able to start any sessionThe Chrome console is full of errors because Kasm is trying to open
https://kasm.domain.tld:18260
instead ofhttps://kasm.domain.tld
Expected Behavior
The remote (cloudflare url) should work 1:1 as the local one
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs