Ian-Kasmweb

Hi @mruizdia @zimmra, In our testing we have found that this issue occurs when client connections use HTTP/2. If you have a paid plan with Cloudflare [disabling HTTP/2 should resolve...

Hi @mruizdia and @zimmra , This issue should be resolved in the new Kasm 1.17.0 release. Instructions on upgrading your existing installation can be found in the [Kasm Documentation](https://kasmweb.com/docs/latest/upgrade/single_server_upgrade.html#automated-upgrade)

@mruizdia what happens when you attempt to connect via the web-native client? That can be selected by editing the workspace and going the "RDP Client options" section and seelcting "Web-Native...

Hello, What version of Kasm did you have installed when you attempted to run `upgrade.sh`?

Ah, that seems to be the issue. We don't recommend using the 1.17.0 installer's upgrade.sh on a system that has Kasm Workspaces 1.17.0 installed as it's not something currently supported....

Hi @straeb, Thank you for bringing this to our attention. We were able to reproduce this issue. It appears this also occurs without an external reverse proxy. We've added this...