[Bug] - only RDP local client mode does not connect, and only web native connection is possible.

[redkreuz]

Existing Resources

• [ ] Please search the existing issues for related problems
• [ ] Consult the product documentation : Docs
• [ ] Consult the FAQ : FAQ
• [ ] Consult the Troubleshooting Guide : Guide
• [ ] Reviewed existing training videos: Youtube

Describe the bug During a typical day, when 7-10 users use only RDP local client mode for more than 10 hours, the session connection is terminated. When trying to reconnect a few hours later in the evening, only RDP local client mode fails, while web native connects normally. This issue occurs even when no one else is using the service. Restarting the kasm_rdp_https_gateway container allows normal RDP local client access.

To Reproduce Steps to reproduce the behavior:

1. Go to 'Infra > Server > Create RDP Server and Kasm Workspaces > Create and Select Server'
2. Go to the access management menu, create each user and group, and assign each workspace.
3. When 7 to 10 people use the RDP local client for more than 10 hours, the web session timeout is 10 minutes and the RDP session timeout is 5 hours (18000 seconds).
4. Due to persistent errors, the kasm_rdp_https_gateway container is restarted every day at 4 AM, and after most of the usage ends around 7 PM, I try to connect again with the RDP local client around 9~10 PM, but I get the message "Unable to connect" and cannot connect.

Expected behavior At this point, the web session can be accessed normally, but the RDP local client mode is not accessible. Restarting the kasm_rdp_https_gateway container will allow access in RDP local client mode.

Screenshots

• unable to connect rdp local client mode
• kasm_rdp_https_gateway container log when rdp connection fails

Workspaces Version

• Version 1.17.0

Workspaces Installation Method

• Single Server

Client Browser (please complete the following information):

• OS: Windows 10, Windows 11
• Browser: Edge, Chrome
• Version: lastest

Workspace Server Information (please provide the output of the following commands): $ uname -a Linux kasm 4.18.0-553.45.1.el8_10.x86_64 https://github.com/kasmtech/workspaces-issues/issues/1 SMP Wed Mar 19 18:28:53 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/os-release NAME="Rocky Linux" VERSION="8.10 (Green Obsidian)" ID="rocky" ID_LIKE="rhel centos fedora" VERSION_ID="8.10" PLATFORM_ID="platform:el8" PRETTY_NAME="Rocky Linux 8.10 (Green Obsidian)" ANSI_COLOR="0;32" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:rocky:rocky:8:GA" HOME_URL="https://rockylinux.org/" BUG_REPORT_URL="https://bugs.rockylinux.org/" SUPPORT_END="2029-05-31" ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8" ROCKY_SUPPORT_PRODUCT_VERSION="8.10" REDHAT_SUPPORT_PRODUCT="Rocky Linux" REDHAT_SUPPORT_PRODUCT_VERSION="8.10"

$ docker info Client: Docker Engine - Community Version: 26.1.3 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.14.0 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.5.0 Path: /usr/local/lib/docker/cli-plugins/docker-compose

Server: Containers: 10 Running: 10 Paused: 0 Stopped: 0 Images: 21 Server Version: 26.1.3 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan kasmweb/sidecar:1.2 macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 8b3b7ca2e5ce38e8f31a34f35b2b68ceb8470d89 runc version: v1.1.12-0-g51d5e94 init version: de40ad0 Security Options: seccomp Profile: builtin Kernel Version: 4.18.0-553.45.1.el8_10.x86_64 Operating System: Rocky Linux 8.10 (Green Obsidian) OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 15.39GiB Name: kasm ID: de1d58d2-44d9-479e-bf43-cce3d0cbd3e4 Docker Root Dir: /var/lib/docker Debug Mode: false Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1f3d5e7147e9 kasmweb/proxy:1.17.0 "/docker-entrypoint.…" 4 weeks ago Up 5 days 80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp kasm_proxy d6893de9f923 kasmweb/rdp-https-gateway:1.17.0 "/opt/rdpgw/rdpgw" 4 weeks ago Up 18 hours (healthy) kasm_rdp_https_gateway 58d852c4aa90 kasmweb/rdp-gateway:1.17.0 "/start.sh" 4 weeks ago Up 5 days (healthy) 0.0.0.0:3389->3389/tcp, :::3389->3389/tcp kasm_rdp_gateway 2a464ad1288e kasmweb/agent:1.17.0 "python3 /src/Provis…" 4 weeks ago Up 5 days (healthy) 4444/tcp kasm_agent fb9d8fb84333 kasmweb/share:1.17.0 "python3 /src/api_se…" 4 weeks ago Up 5 days (healthy) 8182/tcp kasm_share aad26760043d kasmweb/manager:1.17.0 "python3 /src/api_se…" 4 weeks ago Up 5 days (healthy) 8181/tcp kasm_manager 666bcdf12063 kasmweb/api:1.17.0 "/bin/sh -c /usr/bin…" 4 weeks ago Up 5 days (healthy) 8080/tcp kasm_api f6778c853845 kasmweb/kasm-guac:1.17.0 "/dockerentrypoint.sh" 4 weeks ago Up 5 days (healthy) kasm_guac 8f8109bb2dfb redis:5-alpine "docker-entrypoint.s…" 4 weeks ago Up 5 days 6379/tcp kasm_redis a0b31960028c kasmweb/postgres:1.17.0 "docker-entrypoint.s…" 4 weeks ago Up 5 days (healthy) 5432/tcp kasm_db

Additional context Add any other context about the problem here.

kasm_rdp_20250826.txt