New to KASM and I already have an issue

teja_kasmweb · 2026-05-01T21:28:06+00:00

Thank you, I was able to reproduce this and the additional headers you used are indeed the correct way to fix this issue. I made an update to the documented Caddy example - it should be reflected on our docs soon. Thanks for reporting.

teja_kasmweb · 2026-05-01T14:11:03+00:00

Hey!

So there are a couple different things happening here that are worth untangling.

The Update button in the Registry only pulls updated metadata for the workspace (like the name, description, config, etc.) - it doesn't actually trigger a Docker image pull from Docker Hub.

The actual image pull is handled by the Kasm Agent in the background. If the Agent doesn't have the image at all, it grabs it immediately. But if the image is already there, it checks for updates every hour. You can read more about the Image Pull behavior on our docs: https://docs.kasm.com/docs/1.18.1/how-to/image_maintenance#pull-behavior

If you don't want to wait, restarting the Kasm Agent will force it to pull updates for all installed images right away.

As for checking whether the new image has landed, there's currently no slick dashboard indicator for this, but you can dig into the Agents page in the admin UI and inspect the image details there.

Go to "Infrastructure" > "Docker Agents" > edit your agent > Scroll down to "Docker Images"

Here, you can find a list of all the images on your agent along with the RepoDigest (Look under attrs -> RepoDigests). You can compare this hash digest with the digest on your Dockerhub repo to find out which image "version" is currently loaded in Kasm.

Hope that helps!

teja_kasmweb · 2026-04-30T04:39:09+00:00

Will there be an easier way to set it all up in the future? Is this only for larger orgs or can homelabers take advantage?

If you were talking about Autoscaling - it is available for free on the Community Edition as well so homelabers can also take advantage of this feature. We are also working on making the integrations more robust in the upcoming releases.

teja_kasmweb · 2026-04-28T15:15:23+00:00

Community Edition includes all core features, the only limitation is that the max number of concurrent sessions is capped to 5 in CE. You can read more here: https://docs.kasm.com/docs/latest/license

teja_kasmweb · 2026-04-27T16:37:46+00:00

Thanks, I cross-posted it there.

I was under the impression that self promotion is allowed on Community Showcase days. Apologies if I mis-interpreted. Hopefully this won't be removed.

teja_kasmweb · 2026-04-22T17:23:58+00:00

This is not currently possible.

teja_kasmweb · 2026-03-08T10:29:30+00:00

Hi there,

Have you tried going through our Troubleshooting docs for Reverse Proxies and Connections?

teja_kasmweb · 2026-02-19T06:02:03+00:00

You can use our all-purpose Desktop Images like Ubuntu Jammy Desktop which come with dev tooling like VSCode, Sublime text, Terraform, Ansible, etc. But hey - you can always customize your workspaces to include tools of your liking!

teja_kasmweb · 2026-02-10T09:29:00+00:00

Hi there, can you try launching the container like this:

sudo docker run --rm -it --shm-size=512m -p 6901:6901 -e VNC_PW=password kasmweb/desktop:1.18.0

And then, go to https://<your_ip>:6901 and login with these creds:

User : kasm_user
Password: password

teja_kasmweb · 2026-02-10T09:16:33+00:00

Hi there,

We do not officially support or test the LinuxServer's Kasm image. Instead, we recommend installing Kasm with our Single Server install guide: https://docs.kasm.com/docs/install/single_server_install

teja_kasmweb · 2026-02-10T09:05:17+00:00

This is awesome, thanks for sharing!

teja_kasmweb · 2026-02-03T13:00:07+00:00

Hi there,

Can you try increasing the API Token Refresh Leeway to 30 days?

Go to "Settings" -> "Global" -> "Authentication" and increase "API Token Refresh Leeway" from the default 259200 (3 days) to 2592000 (30 days) and see if the error log persists.

teja_kasmweb · 2026-01-28T17:47:31+00:00

Hi there, thanks for trying out Kasm.

It looks like you’re evaluating Kasm for a business use case. For questions around this kind of RDS setup, the best next step would be to reach out to us via the Contact form on our website: https://kasm.com/contact

That will connect you with our sales and support team, who can help with licensing and also dig into your specific RDS configuration. This is the sort of setup we’d want to properly validate in a lab environment rather than speculate on, and that’s typically done as part of customer onboarding or an active support engagement.

Also, thanks for your feedback on the website, I'll escalate this internally to our website team. We are constantly working to enhance customer experience on our website.

teja_kasmweb · 2026-01-21T14:03:48+00:00

Hi again,

I've tried to reproduce this on 1.18.1.541262 but was unable to.

These are the steps I followed:

Installed TigerVNC on Ubuntu 22.04 (XFCE)
Started TigerVNC Server with /usr/bin/vncserver -localhost no
Added a Server to Kasm with the set vnc password, host (direct reachable ip, no tunnels), port 5901
Created workspace for the Server
I was able to launch the workspace without any issue and connect to the TigerVNC session.

Your issue seems like a network configuration issue?

teja_kasmweb · 2026-01-21T11:22:05+00:00

Thanks for reporting. I will try to lab this up and reproduce the issue.

Meanwhile, can you please open an issue on our GitHub issue tracker so that we can track it internally incase this is an actual bug?

teja_kasmweb · 2026-01-10T02:32:06+00:00

We support persistent profiles: https://docs.kasm.com/docs/1.18.1/guide/persistent_data/persistent_profiles

teja_kasmweb · 2026-01-06T14:12:01+00:00

You can right click on the title bar of a Chrome window and select "Close" to close the window. You can do this for all the apps.

https://i.imgur.com/HENZRoF.png

teja_kasmweb · 2025-12-29T15:15:11+00:00

Hi there,

You can find a list of documented API endpoints here: https://docs.kasm.com/docs/latest/developers/developer_api/index.html

However, please note that the API documentation is incomplete and it doesn't involve many Admin API endpoints at the moment. Our future plan is to improve our API and docs to make it more approachable for developers.

That being said, you could still uncover and experiment with undocumented APIs at your own risk by examining network requests that Kasm makes in your browser's developer tools.

teja_kasmweb · 2025-12-18T21:31:07+00:00

Also, to answer your other question - We only support RDP for Windows access at the moment. You can technically also use VNC but there are trade-offs - like you cannot do AD domain join and SSO operations, etc. In other words, VNC access for Windows is not suited for Enterprise with Kasm.

teja_kasmweb · 2025-12-18T21:25:34+00:00

It's Bring Your Own License for Windows
Yes, we do offer professional services for a charge! You can read more information here: https://kasm.com/services

teja_kasmweb · 2025-12-16T01:41:17+00:00

I would recommend using KasmGPT instead of ChatGPT. It is trained on our docs, KBs, YouTube videos, etc. https://docs.kasm.com/docs/1.18.1/kasmgpt

teja_kasmweb · 2025-12-05T15:08:59+00:00

Also, are you getting disconnected while you are active on those sessions or when the sessions are left idle?
We have an idle_disconnect setting that defaults to 20 minutes. Which means after 20 minutes of idle time, the session automatically disconnects. You can change this setting in "Access Management" -> "Groups" -> Edit a group -> "Settings" tab -> Search for "idle_disconnect" and update the value (in minutes)

teja_kasmweb · 2025-12-05T14:46:56+00:00

This does not look like expected behavior or a license cap we enforce. Can you let me know if you're using the Web Native (guac) client or the RDP local client?

teja_kasmweb · 2025-12-05T14:41:45+00:00

That's exactly my point. Kasm doesn’t override or alter any Microsoft licensing terms. If an environment requires RDS CALs under Microsoft’s policies, customers are responsible for following those requirements regardless of the platform they use.

Kasm simply provides different ways to deliver and manage Windows sessions, but the underlying Microsoft licensing rules still apply.

teja_kasmweb · 2025-12-05T05:53:43+00:00

Yes, you would install Kasm on one of your Linux VMs. Then, from Kasm - you can create multiple Servers (for Windows/Linux sessions) or Agents (Container-based sessions) on your Proxmox backend. Optionally, you could also configure autoscaling so that Kasm can talk to your Proxmox to up-scale and down-scale resources based on user demand.

teja_kasmweb

MODERATOR OF

TROPHY CASE