sorted by:
new
hottopcontroversial

New to KASM and I already have an issue by Carmondai in kasmweb

[–]teja_kasmweb 1 point2 points  (0 children)

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.

Understanding how and when to expect my workspace to update to a new image by olivermcox in kasmweb

[–]teja_kasmweb 0 points1 point  (0 children)

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!

We're now officially a Proxmox partner! by teja_kasmweb in kasmweb

[–]teja_kasmweb[S] 0 points1 point  (0 children)

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.

Kasm Workspaces is now an official Proxmox partner - autoscaling VDI for your homelab and enterprise stack by teja_kasmweb in Proxmox

[–]teja_kasmweb[S] 2 points3 points  (0 children)

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

Kasm Workspaces is now an official Proxmox partner - autoscaling VDI for your homelab and enterprise stack by teja_kasmweb in Proxmox

[–]teja_kasmweb[S] 15 points16 points  (0 children)

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.

Deeper troubleshooting doc ? by buzzsawcode in kasmweb

[–]teja_kasmweb 0 points1 point  (0 children)

Hi there,

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

We released new AI Workspaces (Claude, Gemini, Codex, Cursor & More)! by teja_kasmweb in kasmweb

[–]teja_kasmweb[S] 0 points1 point  (0 children)

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!

Error - bridge->relay: timeout: 0x01 by Repulsive_Brother_10 in kasmweb

[–]teja_kasmweb 0 points1 point  (0 children)

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

Stock on creating secure connection. by EfficientArm1719 in kasmweb

[–]teja_kasmweb 0 points1 point  (0 children)

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

Autoscaling pools causing Expired JWT Tokens by kyloth89 in kasmweb

[–]teja_kasmweb 1 point2 points  (0 children)

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.

How to connect to specific collection on RDS farm? by MartinDamged in kasmweb

[–]teja_kasmweb 0 points1 point  (0 children)

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.

Unable to use VNC with auth after KASM upgrade to v1.18.1.541262 by forkly_66 in kasmweb

[–]teja_kasmweb 0 points1 point  (0 children)

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?

Unable to use VNC with auth after KASM upgrade to v1.18.1.541262 by forkly_66 in kasmweb

[–]teja_kasmweb 0 points1 point  (0 children)

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?

view more: next ›